Skip to content

3.2.0 Release
Compare
Choose a tag to compare
@Nightsd01 Nightsd01 released this 01 Jun 23:02
3.2.0
2130293
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Xamarin SDK Updates

• Adds GDPR compliance methods to the SDK.
• You can now use OneSignal.SetRequiresUserPrivacyConsent(true) to completely disable initialization of the OneSignal SDK until the user provides privacy consent (when your app calls OneSignal.UserDidProvidePrivacyConsent(true)).
• Until consent is provided, the SDK will delay initialization and will not send any personal data. If your app attempts to call any methods (such as GetTags), the SDK will not crash but will print out an error message to console.
• Fixes an issue that caused new methods (ie. the new Email methods) to not appear in some circumstances.
• Fixes the way the SDK handles callbacks, making it safe to call GetTags() multiple times for example instead of using global references.
• Fixed an Android issue which would have caused users to see Could not install ... CustomTabs, by adding MonoAndroid7.1, 8.0, and 8.1 to the nupkg

Android Native SDK 3.9.1

  • Now supports FCM (Firebase Cloud Messaging) library
    • After April 11, 2019 Google will drop the GCM from new versions their Play Services library
    • GCM (Google Cloud Messaging) is still supported in the OneSignal SDK until then
    • Issue #507
  • Fixed NPE on UserState.dependValues. Issue #503
  • Added try-catch to work around Oppo device bugs. Issue #491and #487
  • Rare NullPointerException on WakefulBroadcastReceiver. Issue #488
  • Fixed Excessive Wi-Fi scans (background). issue #433
  • Fixed additional ConcurrentModificationException occurrence. issue #465
  • Fixed issue with latest Proguard causing FCM and Android Support library report as not found.
  • FCM init error when the Firebase Auth library was added to the project. PR #530
  • Fixed GoogleAPIClient not connected yet errors. Issue #509
  • Android 7.0 Bad Notification: Couldn't expand RemoteViews for: StatusBarNotification
    • Restore on app update disabled to fix issue #263
  • NPE on flushBufferToDisk. Issue #513

iOS Native SDK 2.8.5

• Fixes a rare concurrency issue with the SDK's HTTP client.
• This issue would have caused exceptions when GDPR consent was revoked, or in some wrapper SDK's, early in the app lifecycle before the app ID was provided.
• Fixes a private API issues preventing developers from uploading binaries to the App Store
• Any methods named valueForQueryParameter() are apparently flagged by Apple as private API usage......
• Changed the name of the method so it no longer triggers this issue.
• The OneSignal iOS SDK now includes GDPR privacy consent methods which allow developers to postpone initialization of the SDK until the user provides privacy consent.
• This new GDPR privacy setting can be controlled by adding OneSignal_require_privacy_consent to your application's Info.plist and setting it to YES.
• Once the user accepts the GDPR privacy permissions, your application can call OneSignal.consentGranted(true)
• Your users can revoke privacy consent at any time by calling OneSignal.consentGranted(false)
• The SDK will now work with media attachment URL's that don't end in file extension (ie. .jpg). If a URL is missing a file extension, it will instead use the MIME type of the asset.
• Resolves an incompatibility issue with the HelpShift iOS SDK
• Fixes an issue that caused incorrect "notification opened" events to be sent to OneSignal's backend server

Assets 2
Loading