Releases: microsoft/appcenter-sdk-dotnet
1.1.0
AppCenter
iOS
- [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.
UWP
- [Fix #390] The SDK is now compatible with sqlite-net-pcl 1.5.* (currently in beta). It is still compatible with 1.3.*. Note that it is still not compatible with versions in the 1.4.* range due to a known issue.
- [Fix] Fix a locale issue that doesn't properly report system locale if an application doesn't support current language.
- [Improvement] HTTP warning and error logs now include more details: status code and full response body are now printed.
AppCenterCrashes
Android
- [Fix] Fix a crash when sending an attachment larger than 1.4MB. The SDK is still unable to send large attachments (for Android) in this release but now it does not crash anymore. An error log is printed instead.
- [Improvement] Java exceptions caught from .NET runtime are now reported with .NET stack trace frames on the server. However the client side exception object returned by the SDK APIs will still be null and you have to look at
AndroidDetailsproperty to get the Java Throwable that caused this type of crash. (Java.Lang.Throwable is not serializable to a System.Exception object).
UWP
- [Fix #544] Remove message that crashes are not supported on UWP. Please note that none of the client side APIs besides
AppCenter.Startare supported in UWP as crash reporting is provided by a system level component in Windows. Errors when registering the system level crash reporting are now also logged.
AppCenterDistribute
Android and iOS
- [Improvement] Updated translations.
- [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.
AppCenterPush
Android
- [Improvement] The Firebase SDK dependency is now optional. If Firebase SDK is not available at runtime, the push registers and generate notifications using only App Center SDK. The Firebase application and servers are still used whether the Firebase SDK is installed into the application or not.
- The SDK is still compatible with Firebase packages. But if you don't use Firebase besides App Center, you can now remove these packages and refer to the updated getting started instructions to migrate the set up. Migrating the push set up in the application remains optional.
UWP
- [Fix #518] Fix a crash that could occur when starting Push.
1.0.1
1.0.0
General Availability (GA) Announcement.
This version contains breaking changes due to the renaming from Mobile Center to App Center. In the unlikely event there was data on the device not sent prior to the update, that data will be discarded.
Please follow the migration guide to update from an earlier version of Mobile Center SDK.
AppCenter
iOS
- [Fix] Don't send startService log while SDK is disabled.
AppCenterDistribute
iOS
- [Fix] Fix a bug where unrecoverable HTTP error wouldn't popup the reinstall app dialog after an app restart.
- [Improvement] Adding missing translations.
- [Known bug] Checking for last updates will fail if the app was updating from a Mobile Center app. A pop up will show next time the app is restarted to ask for reinstallation.
Android
- [Fix] The view release notes button was not correctly hidden when no release notes were available.
- [Fix] Added missing translations for failed to enable in-app update dialog title and buttons. The main message, however, is not localized yet as it's extracted from a REST API text response.
- [Known issue] When updating an application that uses Mobile Center SDK using the in-app update dialog to an application version that uses AppCenter SDK version, the browser will be re-opened and will fail. User will need to re-install the application from the App Center portal.
0.17.1
This release include 2 bug fixes.
MobileCenterAnalytics
- [Fix] Prevents a possible crash on UWP startup #484
MobileCenterPush
- [Improvement] Updates dependencies on Xamarin Firebase Push to avoid most package conflicts when updating Mobile Center Push on Android.
- [Fix] Fixes a crash when receiving a silent push in background with no message on iOS.
Native SDK Updates
- Fixes from iOS SDK version 0.14.1.
0.17.0
This version contains bug fixes, a new API, and improvements.
MobileCenter
- [Improvement] The NuGet packages now support .NET standard without adding extra project configuration, and the nugets remain compatible with PCL projects.
- [Feature] Added a
MobileCenter.SdkVersionproperty to get the current version of Mobile Center SDK programmatically.
MobileCenterPush
- [Breaking change] To support Android 8.0 applications that use
targetSdkVersion="26"we updated the Firebase SDK dependency which forces applications to use Android 8.0 Mono frameworks.- You need to have Xamarin tools up to date, select Android 8.0 as a target framework and then make sure that in
package.configthe attribute for every package looks like this:targetFramework="monoandroid80"and update as necessary. It's highly recommended to close Studio and clean every obj/bin folder manually in case of any build error after the update. - If you get a conflict with
Xamarin.GooglePlayServices.Basementpackage, you need to update this one to prerelease version60.1142.0-beta1(ore more recent) and retry updating the Mobile Center Push package.
- You need to have Xamarin tools up to date, select Android 8.0 as a target framework and then make sure that in
- [Fix] Fixed: prior to this release, calling
Push.SetEnabledAsync(true)during startup could prevent UWP push registration. Please note that any call toSetEnabledAsync(true)for any module is useless if you have not called it withfalsebefore, modules are enabled by default once included in theStartcall.
Native SDK updates
Embed changes from the underlying native SDK releases:
0.16.0
This release includes bug fixes for iOS from the native SDK: https://github.com/Microsoft/mobile-center-sdk-ios/releases/tag/0.13.0.
Please note that this release does not yet provide the .NET equivalent of the sdkVersion method introduced by the iOS change.
0.15.2
0.15.1
This release includes bug fixes for iOS from the native SDK: https://github.com/Microsoft/mobile-center-sdk-ios/releases/tag/0.12.2
Known issue This release causes build error in Mobile Center or in environments where XCode version is lower than 9. As a consequence, this release was unlisted from nuget.org.
0.15.0
When you update to this release, there will be potential data loss if an application installed with previous versions of MobileCenter SDK on devices that has pending logs which are not sent to server yet at the time of the application is being updated.
- New feature: in app updates can now be received from public distribution groups.
- Fix a bug in UWP SDK where an
InvalidOperationExceptioncould sometimes be thrown at launch time. - This release also includes changes from underlying Android and iOS SDKs of the following versions:
0.14.2
-
Fix a bug in UWP where some crashes, especially those caused by
AggregateException, would not be sent properly. -
Fix a bug in UWP where Analytics would always emit a warning on startup.
-
Reword some logs that used to look like errors when starting Mobile Center in multiple places to appear less harmful. (Issue #396).
-
Improve the reliability of device screen size retrieval in UWP (used in device properties sent with logs).
-
Fix a bug where getting the screen size in UWP could, in some cases, cause a crash. (Issue #398).
-
Change the behavior of Analytics events so that now, when event fields exceed their capacity, they are truncated instead of dropped altogether. Limits:
- Event name maximum length: 256 characters.
- Maximum number of event properties: 5.
- Event property key maximum length: 64 characters.
- Event property value maximum length: 64 characters.
-
This release also includes changes from underlying Android and iOS SDKs of the following versions: