Releases: OneSignal/OneSignal-iOS-SDK
Releases · OneSignal/OneSignal-iOS-SDK
2.13.0 Release
In-App Messaging Improvements, Added External User Id Update Callback, API URL Changed, Minor Bug Fixes
- In-App Messaging Improvements: Redisplaying with a limit and delay, Adding and removing tags, sending outcomes, and permission prompts
- Redisplay params now expected (has defaults) in parser
- Adding and removing tags w/ element click
- Sending outcomes w/ element click
- Showing permission prompts for location and push w/ element click
- Set and remove external user id now have completion callback
- Callback for completion added to verify the status of the set or remove of an external user id (push & email)
- Changed internal API call from onesignal.com to api.onesignal.com
2.12.6 Release
Minor Bug Fixes
- Moved some
init
code beforeinitDone
check so it runs these things every timeinit
is called- Wrapper SDKs call init twice, so when
initDone
was added it harmed some wrapper SDKs
- Wrapper SDKs call init twice, so when
2.12.5 Release
Minor Bug Fixes
-
Cold Start Subscription Fix #596
- Needed better differentiation between
TO
andFROM
states ofOneSignalCommonDefines
keys when saving and getting
- Needed better differentiation between
-
Wrapper(s) Second Init Not Pulling iOS Params Fix #593
- iOS remote params couldn't be pulled and caused SDK to use the default values assigned
-
SetLocationShared Changes #533
- Now
setLocationShared:false
clears last location in the SDK - Extra
VERBOSE
logging added to track the state location checks for better insight
- Now
-
Notification Action Buttons Not Displaying Fix #430
- Forced a refresh on the internal list of list categories so that the action buttons will be added to the notification as well
-
IAM Pause Check Change
- IAMs accumulate in the queue, but prevent the SDK from showing any IAMs from the queue until in app messaging is enabled again
2.12.4 Release
Crash From Null Param & Minor Bug Fixes
- Crash From Null Param #590
NSMutableArray addObject
method called with a nullNSString
param caused a crash- These notifications appearing with null/empty ids are most likely not OneSignal notifications, but handling was implemented to ignore these now and also clean any existing cached ones
2.12.3 Release
Confirmed Deliveries upgrade, i386 simulator, Carthage fixes
- Fixed Carthage build issue
- Fixed missing i386 for 32 bit iOS simulators
- Fixed Confirmed Deliveries not sending for those updating from an older SDK.
2.12.2 Release
Minor fixes
jsonRepresentation
inOSOutcomeEvent
needed a minor check to prevent crashing
2.12.1 Release
Received Receipts
- New Confirmed Deliveries
- Added
jsonRepresentation
toOSOutcomeEvent
2.12.0 Release
Outcome Events, Catalyst Support, & Fixed In-App Message Crash
- New Outcomes feature
- Incorporates outcomes to the focus request for Session Duration tracking on the dashboard
- Includes 3 new public methods
sendOutcome
,sendUniqueOutcome
, andsendOutcomeWithValue
- The concept of a session type now exists in the SDK, DIRECT, INDIRECT, UNATTRIBUTED
- Catalyst support now lets you build iPad apps with our SDK on Mac #534
- Must add
x86_64h
architecture to your targets- Under "Valid Architectures" AND "Architectures"
- Must add
- Fixes In-App Message crash on dismissing #542 & #555
2.11.2 Release
In-App Message iOS Preview crash fix
- Fixes In-App Message preview crash fix note in issue #542
- Bitcode Version - Xcode 10.1
2.11.1 Release
Fixed In-App Message Crash, setLocationShared(), and mikechoch Warnings
- Fixed the mikechoch warnings showing up in apps #525
- Warnings caused by
GENERATE_MASTER_OBJECT_FILE
being set toYES
in release2.10.2
- Changed the
DEPLOYMENT_POSTPROCESSING
flag toYES
to fix the warnings
- Warnings caused by
- In-App Message causing iOS app to crash because of constraint conflicts #536
- Constraint conflict was occurring when sending previews with specific scenarios
- Fixed by removing all constraints on
OSInAppMessageView
before setup of an incoming In-App Message
setLocationShared
was being setfalse
but location still being sent to player record #533- Fixed by adding a check into the
locationManager
callback to return early when location shared isfalse
- Fixed by adding a check into the