Glia Android Widgets 2.3.2

Changed

Reintroduced lost legacy company name configurability.

Glia Android Widgets 2.3.1

Fixed

Java ambiguous reference error for GliaWidgetsConfig.

Glia Android Widgets 2.3.0

Added

• Live Observation support for native mobile applications.
• Ability to set up an engagement confirmation dialog, with or without outbound links to your privacy policy and terms and conditions.

Changed

• Error labels can now be modified using Unified Customization.
• The default screen sharing mode has been changed from UNBOUNDED to APP_BOUNDED.
• Images attached directly from the device camera are now deleted after use, preventing access by other apps with media library permissions.
• The default text in the screen sharing dialog has been updated to match iOS wording.

Fixed

• Sending a message during connection issues resulted in the engagement being terminated.
• Sending an image or file in secure conversations did not work properly.
• When starting a chat engagement after a video call, the audio bubble would appear on the chat screen.
• Resuming audio and video from a hold state did not work correctly.
• The queue animation was shown on the chat screen of restored engagements.
• The SDK would stop receiving screen sharing requests if the visitor rejected the system request.
• In rare cases, the app could crash if it was in the background for a minute or more.

Glia Android Widgets 2.2.2

Added

The capability to manually override the site’s default locale.

Fixed

• The local fallback for the company name was ignored if its value in the SDK configuration was null.
• An unread message indicator was shown over the screen sharing bubble in Call Visualizer engagements.
• The visitor’s floating video view (as black box) remained on the screen when video was turned off.
• Screen sharing and video did not resume after switching network type or briefly turning on airplane mode.

Glia Android Widgets 2.2.0

Added

Support for custom locales in native mobile applications.

Changed

The company name set through Glia Hub is now prioritized over the value set via code.

Fixed

• Global colors were not applied to some views.
• The operator image was not always shown when the “Always Use the Default Operator Picture” setting was enabled.
• The app crashed when the network status could not be specified.

Glia Android Widgets 2.1.3

Added

Default tint color for the GVA card background.

Glia Android Widgets 2.1.2

Fixed

• The chat bubble was not displayed after restoring an engagement.
• The visitor code was not shown unless notifications were already allowed for the app.
• Chat engagements did not restore properly.

Glia Android Widgets 2.1.1

We identified an issue in this release, please use 2.1.2 or newer instead.

Fixed

Visitor renewal request fails with HTTP error 422 when app is upgraded to Glia Android Widgets 2.0.4 or 2.1.0.

Glia Android Widgets 2.1.0

We identified an issue in this release, please use 2.1.2 or newer instead.

Added

• Native GVA support for mobile applications.
• For more information about the feature, see: GVA Support: Android

Changed

• A new NO_ENGAGEMENT state has been added for cases without an ongoing engagement, whereas ENGAGEMENT_ENDED is now used only if engagement has ended.
• Chat now automatically scrolls down when a visitor sends a message.

Fixed

• Some engagements were prematurely cleared before the [Events.END] event.
• The Attachment button was hidden in secure conversations.
• The default operator image was not shown in the chat transcript.
• The app crashed when sending a message from an empty secure conversations chat screen.
• Errors occurred when calling showVisitorCodeDialog if the material design was set globally but then overridden.

Full Changelog

Glia Android Widgets 2.0.4

We identified an issue in this release, please use 2.1.2 or newer instead.

Changed

Security improvements for visitor authentication.

Fixed

• Some engagements were prematurely cleared before the Events.END event.
• Visitor code view was not closing correctly in some cases.
• Survey was shown on new engagement start if the previous engagement was ended by calling endEngagement().
• Operator image was not shown after engagement transfer.
• Two-way video and screen-sharing requests were not coming in some cases.