2.1.0

Version 2.1.0

App Center

• [Fix] Handle incorrect usage of AppCenter.setLogUrl API to provide readable error message.
• [Fix] Fix decrypting values that have been stored for more than a year (such as the in-app update token).

App Center Analytics

• [Feature] Support setting latency of sending events via Analytics.setTransmissionInterval.

App Center Auth

• [Feature] Expose the ID Token and Access Token (as raw JWT format) in the UserInformation object returned from the sign-in method.
• [Fix] Fix missing proguard rules so that the app does not have to specify them.
• [Fix] Fix crash on silently refreshing token if initialization of MSAL fails.
• [Fix] Fix sign-in before start auth service never ends and blocks every next try.
• [Breaking change] The UserInformation class has been moved from the appcenter module to the appcenter-auth module and must now be imported as import com.microsoft.appcenter.auth.UserInformation.

App Center Data

• [Fix] Fix an issue where invalid characters in the document ID are accepted at creation time but causing errors while trying to read or delete the document. The characters are #, \, /, ?, and all whitespaces.

App Center Crashes

• [Fix] Fix a crash that could sometimes occur while processing native crash reports.

App Center Distribute

• [Feature] Add Distribute.setEnabledForDebuggableBuild(boolean) method to allow in-app updates in debuggable builds.
• [Fix] Fix duplicate in-app update dialog when restarting (or switching) activity quickly after clicking download. Also fixes a crash when choosing "Ask me in a day" in the duplicate dialog.
• [Fix] Fix a crash that could occur when downloading the update with a customized dialog and then calling Distribute.notifyUserConfirmation(UpdateAction.POSTPONE) right after calling Distribute.notifyUserConfirmation(UpdateAction.UPDATE).
• [Fix] Fix a crash that could occur while trying to open the browser on some devices.

App Center Push

• [Fix] Update Firebase dependency and AppCenter push logic to avoid a runtime issue with the latest Firebase messaging version 18.0.0.

2.0.0

Version 2.0.0

Version 2 of the App Center SDK includes two new modules: Auth and Data.

AppCenterAuth

App Center Auth is a cloud-based identity management service that enables developers to authenticate application users and manage user identities. The service integrates with other parts of App Center, enabling developers to leverage the user identity to view user data in other services and even send push notifications to users instead of individual devices.

AppCenterData

The App Center Data service provides functionality enabling developers to persist app data in the cloud in both online and offline scenarios. This enables you to store and manage both user-specific data as well as data shared between users and across platforms.

AppCenterCrashes

• [Feature] After calling Auth.signIn, the next crashes are associated with an accountId corresponding to the signed in user. This is a different field than the userId set by AppCenter.setUserId. Calling Auth.signOut stops the accountId association for the next crashes.

AppCenterDistribute

• [Fix] Fix in-app updates not working on new Samsung devices.

AppCenterPush

• [Feature] After calling Auth.signIn, the push installation is associated to the signed in user with an accountId and can be pushed by using the accountId audience. This is a different field than the userId set by AppCenter.setUserId. The push installation is also updated on calling Auth.signOut to stop the association.
• [Fix] Fix updating push installation when setting or unsetting the user identifier by calling AppCenter.setUserId.

1.11.4

Version 1.11.4

AppCenter

• [Fix] Fix network connection state tracking issue, which prevented sending data in some restricted networks.
• [Fix] Fix possible deadlock on changing network connection state.

AppCenterDistribute

• [Fix] Fix in-app updates not working on devices using Xiaomi MIUI from versions 10 and above.

1.11.3

Version 1.11.3

AppCenter

• [Fix] The SDK normally disables storing and sending logs when SQLite is failing instead of crashing the application. New SQLite APIs were introduced in version 1.9.0 and the new API exceptions were not caught, this is now fixed.

AppCenterDistribute

• [Fix] Fix exception if we receive deep link intent with setup failure before onStart.
• [Fix] Fix checking updates for applications installed on corporate-owned single-use devices.

1.11.2

Version 1.11.2

AppCenter

• [Fix] Fix TLS 1.2 configuration for some specific devices running API level <21. The bug did not affect all devices running older API levels, only some models/brands, and prevented any data from being sent.

AppCenterAnalytics

• [Fix] Extend the current session instead of starting a new session when sending events from the background. Sessions are also no longer started in background by sending an event or a log from another service such as push, as a consequence the push registration information will be missing from crash events information.

AppCenterDistribute

• [Fix] Fix issue with forcing Chrome to open links when other browsers are the default.

1.11.0

Version 1.11.0

AppCenter

• [Feature] Allow users to set userId that applies to crashes, error and push logs. This feature adds an API, but is not yet supported on the App Center backend.
• [Fix] Do not delete old logs when trying to add a log larger than the maximum storage capacity.
• [Fix] Fix error detection of setMaxStorageSize API if database uses custom page size.
• [Fix] Fix minimum storage size verification to match minimum possible value.
• [Fix] Fix disabling logging of network state changes according to AppCenter.getLogLevel.
• [Fix] Fix logs duplication on unstable network.

AppCenterCrashes

• [Fix] Fix a bug where crash data file could leak when the database is full.

AppCenterPush

• [Fix] Fix push foreground listener after re-enabling push service.

1.10.0

Version 1.10.0

AppCenterAnalytics

• [Feature] Add API to specify event persistence priority.

AppCenterCrashes

• [Fix] Preventing stack overflow crash while reading a huge throwable file.

1.9.0

AppCenter

• [Feature] Add a setMaxStorageSize API which allows setting a maximum size limit on the local SQLite storage. Previously, up to 300 logs were stored of any size. The default value is 10MB.
• [Security] To enforce TLS 1.2 on all HTTPS connections the SDK makes, we are dropping support for API level 15 (which supports only TLS 1.0), the minimum SDK version thus becomes 16. Previous versions of the SDK were already using TLS 1.2 on API level 16+.
• [Bug fix] Fix validating and discarding NaN and infinite double values when calling setCustomProperties.

AppCenterAnalytics

• [Feature] Add pause/resume APIs which pause/resume sending Analytics logs to App Center.
• [Feature] Add support for typed properties. Note that these APIs still convert properties back to strings on the App Center backend. More work is needed to store and display typed properties in the App Center portal. Using the new APIs now will enable future scenarios, but for now the behavior will be the same as it is for current event properties.
• [Feature] Preparation work for a future change in transmission protocol and endpoint for Analytics data. There is no impact on your current workflow when using App Center.

1.8.0

AppCenterCrashes

• [Fix] Fix a bug where some initialize operations were executed twice.
• [Fix] Fix a bug where device information could be null when reading the error report client side.

AppCenterDistribute

• [Fix] Fix a crash that could happen when starting the application.

AppCenterAnalytics

• [Feature] Preparation work for a future change in transmission protocol and endpoint for Analytics data. There is no impact on your current workflow when using App Center.

1.7.0

AppCenterAnalytics

• [Feature] Preparation work for a future change in transmission protocol and endpoint for Analytics data. There is no impact on your current workflow when using App Center.

AppCenterPush

The Firebase messaging SDK is now a dependency of the App Center Push SDK to be able to support Android P and also prevent features to break after April 2019 based on this announcement.

You need to follow some migration steps after updating the SDK to actually use Firebase instead of the manual registration mechanism that we are providing. The non Firebase mechanism still works after updating the SDK but you will see a deprecation message, but this will not work on Android P devices until you migrate.

After updating the app to use Firebase, you will also no longer see duplicate notifications when uninstalling and reinstalling the app on the same device and user.