Releases: microsoft/appcenter-sdk-react-native
1.4.0
Bugfixes
- Returns
NO
fromrequiresMainQueueSetup()
in iOS native modules to avoid react native warnings. #238 - Adds LICENSE.md to Products folder to make cocoapod integration easier during SDK release process. #250
- Fixes react-native 0.53 prompt glitches when linking. #252
- Avoid android link duplicates for appcenter in react-native 0.53. #254
- Improves error handling in react-native android linker script. #256
- Adds GitHub Issue Template. #258
Misc
1.3.0
1.2.0
This release contains bugfixes and a breaking change. The SDK now requires iOS 9 or later.
Bugfixes
- Fix warnings when sending crashes without a listener. #192
- The test app doesn't show an error when a binary attachment is not present. #193
- Fix a bug where
Analytics.trackEvent
doesn't allow message with no properties. #202 - Perform a case-insensitive search for AppDelegate based on package.json. #202
- Don't check for the platform when checking for the
pod
command. #217
Misc
1.1.0
Features
-
[Android] 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.
-
[iOS] Support brownfield iOS app with
Podfile
to install usingreact-native link
(with react-native v0.50 or later) #177. See examplePodfile
here. -
appcenter-crashes
getErrorAttachments
callback now works with ES2107 async/await functions #179. Please see Add attachments to a crash report of App Center documentation for more information.
Bugfixes
- Fix a bug where the license is not included in
AppCenterReactNativeShared
CocoaPod #174 - Fix a bug in appcenter-crashes module to make sure crashes won't get processed when crashes is disabled #181
Misc
- This release also includes changes from underlying AppCenter Apple SDK:
- This release also includes changes from underlying AppCenter Android SDK:
1.0.1
Bugfixes
- Fixes an issue in React Native iOS where
Crashes.setListener()
sometimes doesn't get the callback when iOS application launches too quickly.
Misc
- This release also includes changes from underlying AppCenter Apple SDK:
1.0.0
Visual Studio App Center General Availability (GA).
Breaking Change
This version contains breaking changes due to the renaming from Mobile Center to App Center. If you have existing apps using Mobile Center SDK, please follow the react-native sdk migration guide to upgrade to App Center SDK.
Misc
- This release also includes changes from underlying AppCenter Apple SDK:
- This release also includes changes from underlying AppCenter Android SDK:
0.11.2
0.11.1
Breaking Change
Crashes.process()
API that process crashes in JavaScript is deprecated and removed from this version.Crashes.setListener()
API is introduced to provide more functionality and flexibility of processing crashes in JavaScript. For more information, please see Customize your usage of Mobile Center Crashes.Crashes.setEventListener()
API that get sending status for a crash log is deprecated and removed from this version. UseCrashes.setListener()
API instead. The three callbacks inCrashes.setEventListener()
are renamed inCrashes.setListener()
as follow:willSendCrash()
->onBeforeSending()
didSendCrash()
->onSendingSucceeded()
failedSendingCrash()
->onSendingFailed()
Push.setEventListener()
API is renamed asPush.setListener()
, and the callback is renamed as follow:pushNotificationReceived()
->onPushNotificationReceived()
New Feature
Crashes.setListener()
provides the following callbacks:shouldProcess()
callback allows you decide if a particular crash needs to be processed or not.shouldAwaitUserConfirmation()
andCrashes.notifyUserConfirmation()
callback allows you wait for user confirmation before sending crashes.getErrorAttachments()
callback allows you to add attachments to a crashe report
For more information, please see Customize your usage of Mobile Center Crashes.
Bugfixes
- Fix a bug in Android that JS send events before native Java loads would crash application #135
Misc
- This release also includes changes from underlying iOS SDK:
- This release also includes changes from underlying Android SDK:
0.10.0
- New Feature -
getSdkVersion()
API for getting mobile center react native SDK version at runtime #126 - Support Android only project in
react-native link
#107 - Support iOS only project in
react-native link
#107 - Fix a bug in
setCustomProperties()
API where boolean property is always set to true #114 - Fix a bug where mobile center analytics is always enabled even analytics is supposed to "Enable in JavaScript" #117
- Fix a typo in crashes logging in onSendingFailed #120
- Fix a bug in iOS
react-native link
script issue #123 - This release also includes changes from underlying iOS SDK:
0.9.0
- Breaking change Updated CustomProperties API parameters to align with other Mobile Center SDKs. Please refer to the updated documentation.
- Fix updating code when changing iOS prompt answers when running
react-native link
a second time. - This release also includes changes from underlying Android SDK of the following versions:
- This release also includes changes from underlying iOS SDK: