Releases: OneSignal/OneSignal-Android-SDK
Releases · OneSignal/OneSignal-Android-SDK
3.4.0 Release
Google Project number pulled from OneSignal account
- Google project number is now used from OneSignal instead of
onesignal_google_project_number
.- If none was entered on OneSignal then the manifest key will still be used.
- Fixed issue where disabling badges was not being respected in some cases. Issue #129
- Was creating crashes on some Sony devices if you also removed the permission.
- If send priority was set to high(10), then the notification will be displayed with
PRIORITY_MAX
. - Added
priority
andcollapseId
toOSNotificationPayload
collapseId
(AKAcollapse_key
) will be used to replace notifications in a future update.
3.3.1 Release
- Background images on notifications will now be top left aligned.
- Set string key
onesignal_bgimage_notif_image_align
toright
to change alignment. - Alignment was
centerCrop
in previous releases. - Background images are now only supported on Android 4.1+.
- Set string key
- Added
syncHashedEmail
validation.
3.3.0 Release
manifestApplicationId and Hardware id remove and postNotification fix
manifestApplicationId
no longer needs to be set, defaultapplicationId
is now used.- Removed used of fallback hardware ids.
PostNotificationResponseHandler.onFailure
now always returns aJSONObject
with an error.
3.2.0 Release
Stability, no sound payload option, and Location sharing setting
Features
- Setting Android sound name to
"null"
or"nil"
disables the notification's sound. - Location sharing can be disabled with
setLocationShared
.
Fixes
3.1.1 Release
Added removeNotificationReceivedHandler
for use with other SDKs.
3.1.0 Release
- Fixed field names with notification classes
- Fixed very rare concurrency issue with user update network call.
3.0.4-rc1 Release
- Fixes for closed database errors due to race conditions.
- SyncService keeping process in memory fix.
3.0.3 Release
3.0.2 Release
Fixed Google Play services app out of date issue
3.0.1 Release
- Fixed rare crash if your app was stopped while generating a notification. Issue #84
- Fix extra network calls if using sendTags and their was a delay registering for push.