-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when reattempting the request #391
Comments
@ogres Even in release builds, |
Nightsd01
added a commit
that referenced
this issue
Aug 1, 2018
• In the OneSignalClient class that handles network request logic, there were rare cases where the SDK was attempting to execute blocks that could potentially be nil • Adds checks to ensure these blocks aren't executed if they're nil (fixes #391)
Merged
Nightsd01
added a commit
that referenced
this issue
Aug 6, 2018
• In the OneSignalClient class that handles network request logic, there were rare cases where the SDK was attempting to execute blocks that could potentially be nil • Adds checks to ensure these blocks aren't executed if they're nil (fixes #391)
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using OneSignal v 2.8.5 and having crashes.
Here is a crash log:
It crashes on this line: https://github.com/OneSignal/OneSignal-iOS-SDK/blob/master/iOS_SDK/OneSignalSDK/Source/OneSignalClient.m#L111
This might be connected to NSStringFromClass usage, maybe in Release mode optimisations are removing some info for this method to function properly.
Or failureBlock can be nil ....
Unfortunately I could not reproduce it myself.
But, looks like it happens when there are some requests saved to re-attempt, then user removes consent and then reattempt tries to fail with error message.
The text was updated successfully, but these errors were encountered: