1.9.0

Version 1.9.0

This version contains bug fixes and a feature.

AppCenter

• [Fix] Fix a potential deadlock that can freeze the application launch causing the iOS watchdog to kill the application.

AppCenterCrashes

• [Fix] The above deadlock was mostly impacting the Crashes module.

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.8.0

Version 1.8.0

This version contains bug fixes and a feature.

AppCenterDistribute

• [Fix] Fix in-app update occasional initialization failure caused by deletion of update token/group id on HTTP status code '0'.
• [Fix] Fix Chinese translation of "side-loading".

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.1

Version 1.7.1

This version contains a bug fix and a new feature.

AppCenter

• [Fix] Fix duplicate symbol errors discovered when using Xamarin wrapper SDK.

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.6.1

Version 1.6.1

This version contains bug fixes.

AppCenterCrashes

• [Fix] Fix an issue in breadcrumbs feature when events are being tracked on the main thread just before a crash.
• [Fix] Fix an issue with cached logs for breadcrumbs feature which are sometimes not sent during app start.

1.6.0

Version 1.6.0

This version contains an improvement and fixes. Any macOS app with unsent logs prior to the update will discard these logs.

AppCenter

• [Fix] Fix non app store macOS apps were sharing the same DB.

AppCenterAnalytics

• [Improvement] Analytics now allows a maximum of 20 properties by event, each property key and value length can be up to 125 characters long.

AppCenterCrashes

• [Fix] Fix enabling uncaught exception handler when a wrapper SDK is in use.

1.5.0

Version 1.5.0

This version contains a new feature.

AppCenterDistribute

• [Feature] Add Session statistics for distribution group.

1.4.0

Version 1.4.0

This version contains a new feature.

AppCenterDistribute

• [Feature] Add reporting of downloads for in-app update.
• [Improvement] Add distribution group to all logs that are sent.

1.3.0

Version 1.3.0

This version has a breaking change as the SDK now requires iOS 9 or later. It also contains a bug fix and an improvement.

AppCenter

• [Improvement] Successful configuration of the SDK creates a success message in the console with log level INFO instead of ASSERT. Errors during configuration will still show up in the console with the log level ASSERT.

AppCenterCrashes

• [Fix] Fix an issue where crashes were not reported reliably in some cases when used in Xamarin apps or when apps would take a long time to launch.

1.2.0

Version 1.2.0

This version has a breaking change with bug fixes and improvements.

AppCenter

• [Fix] Fix an issue that enables internal services even if App Center was disabled in previous sessions.
• [Fix] Fix an issue not to delete pending logs after maximum retries.

AppCenterCrashes

• [Improvement] Improve session tracking to get appropriate session information for crashes if an application also uses Analytics.

AppCenterPush

• [Fix] Fix "Missing Push Notification Entitlement" warning message after uploading an application to TestFlight and publishing to App Store.
• [Improvement] (Breaking Change) In previous versions, it was required to add code to application:didReceiveRemoteNotification:fetchCompletionHandler callback in your application delegate if you or 3rd party libraries already implemented this callback. This is no longer necessary.
  This is a breaking change for some use cases because it required modifications in your code. Not changing your implementation might cause push notifications to be received twice.

  • If you don't see any implementation of application:didReceiveRemoteNotification:fetchCompletionHandler callback in your application delegate, you don't need to do anything, there is no breaking change for you.

  • If you want to keep automatic forwarding disabled, you also don't need to do anything.

  • If your application delegate contains implementation of application:didReceiveRemoteNotification:fetchCompletionHandler, you need to remove the following code from your implementation of the callback. This is typically the case when you or your 3rd party libraries implement the callback.

    Objective-C

    BOOL result = [MSPush didReceiveRemoteNotification:userInfo];
    if (result) {
        completionHandler(UIBackgroundFetchResultNewData);
    } else {
        completionHandler(UIBackgroundFetchResultNoData);
    }

    Swift

    let result: Bool = MSPush.didReceiveRemoteNotification(userInfo)
    if result {
        completionHandler(.newData)
    }
    else {
        completionHandler(.noData)
    }

1.1.0

Version 1.1.0

This version contains a bug fix and improvements.

AppCenter

• [Fix] Fix a locale issue that doesn't properly report system locale if an application doesn't support current language.
• [Improvement] Change log level to make HTTP failures more visible, and add more logs.

AppCenterDistribute

• [Improvement] Add Portuguese to supported languages, see this folder for a list of supported languages.
• [Improvement] Users with app versions that still use Mobile Center can directly upgrade to versions that use this version of App Center, without the need to reinstall.