-
Notifications
You must be signed in to change notification settings - Fork 44
Replace events.removeFirst with events.removeAt(0) #50
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
Conversation
Due to issues outline (here)[https://youtrack.jetbrains.com/issue/KT-71375/Prevent-Kotlins-removeFirst-and-removeLast-from-causing-crashes-on-Android-14-and-below-after-upgrading-to-Android-API-Level-35] ```list.removeFirst()``` produces a runtime error for apps targeting Android 35. Until this issue is resolved, ```list.removeAt(0)``` must be used
|
Are there any workarounds to fix this issue. As this PR is not picked up yet, I suppose it won't get fixed quite soon. |
|
Fixes #35 |
|
I really need this, without this fix most of my users' apps will crash. |
|
@focafull I fixed the issue with patch-package. This is such a simple fix, I'm not sure why it hasn't been merged in |
|
This is quite urgent as it i making the plugin unusable with Capacitor 7. |
|
Why isn't this being merged? |
|
Hey @ColeKainzRSG, thanks for opening the PR with the fix, indeed this was an issue that affects Capacitor 7 builds that use this plugin. We expect to release this fix soon. We apologize for the time it took to address this PR; I'll post a new comment (here and in the opened issues) once the new plugin version is released. |
|
Thank you for the contribution! |
Due to issues outline here,
list.removeFirst()produces a runtime error for apps targeting Android 35. Until this issue is resolved,list.removeAt(0)must be used