-
Notifications
You must be signed in to change notification settings - Fork 371
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
[Bug]: EventProducer.fire #1858
Comments
Getting the same error here, seems like it's trying to modify a collection using an iterator, which generates a crash. I can't really help since com.onesignal:core is closed source, but it seems to be a straightforward fix. |
Thanks for the reports! We're looking into this. |
Hi all, I apologize for any delay, We have identified the cause and are working on the fix for all the methods this crash is reported. |
Hi, |
I've found a way to reproduce this error consistently, with a temporary fix: #1857 (comment) |
Hello everyone! Thank you for your patience here. We have introduced a fix for this crash in our latest release, 5.0.4. Please update your SDK and let us know if you are still having any issues. |
Closing this issue; please let us know if you see any further occurrences of this exception. Thanks! |
Ok and for those who use OneSignalSDK.DotNet 5.0.2 version in Xamarin.Form how do we fix this bug?? |
@tobus2012 you will need to update to OneSignalSDK.DotNet 5.1.0 or newer to get this fix. Please follow up on the OneSignal-DotNet-SDK repo if you have issues, since this repo is only for Android native issues. Edit: an issue was already created as a follow up here: |
What happened?
java.util.ConcurrentModificationException
Steps to reproduce?
What did you expect to happen?
Not crash the app
OneSignal Android SDK version
5.0.2
Android version
13
Specific Android models
No response
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: