-
Notifications
You must be signed in to change notification settings - Fork 218
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]: iOS app gets crashed (Release 3.4.2) #613
Comments
Possibly a duplicate of #608. I am running into this as well |
running into the same weird log during the crash on iOS with |
@chrisvidal for now, you can use the previous stable version |
@devmuaz same error with the
|
@chrisvidal I believe that the version is still the same in the
If still not working, clear the pub cache by running:
|
starting a blank project with |
Make sure you are using Cocoapods 1.11.3 with ruby 2.7.5 and try the below code. We have seen this issue when using versions lower than 1.11.3 and Ruby 2.6.0, but it gets resolved after upgrading
|
this work for me Clean build folder and build. |
I couldn't get anything to work, downgrading, upgrading until I added the groups to info plist(runner and service extension) following the directions of the latest guide. I didn't have that setup. I added those and I was able to build. Granted I did a ton of pod updates and installs, but it's working now. I also followed the steps before to update ruby and cocoapods. |
That's what worked. |
I am still using |
having this issue on my Intel Mac, but on on M1 chip. |
upgrading ruby and cocoapods as well as using |
what versions of ruby and cocoapods have you upgraded? |
The latest - Cocoapods 1.11.3 Ruby 3.2.1 |
This is a critical issue blocking library upgrades. Is it possible to prioritize it? |
Did you try the steps mentioned to resolve? We were able to reproduce the issue when we used a lower ruby version, and the error resolved after we updated. Make sure you are using Cocoapods 1.11.3 with ruby 2.7.5 and try the below code. We have seen this issue when using versions lower than 1.11.3 and Ruby 2.6.0, but it gets resolved after upgrading
|
Hi @nan-li, thanks for the response! Do you think the steps you shared help with the latest version of OneSignal SDK? |
I think these steps are good for 3.4.2+. Then the problem went away after I update my ruby version to 2.7.5+ and cocoapods to 1.11.3. |
@nan-li thanks for the explanation. Unfortunately, I can't control the ruby version since I am building my application with Codemagic which doesn't provide a way to manage the ruby version (only Pod). |
@AndreiMisiukevich Cocoapods released 1.12.1 maybe that updated version will resolve the issue since it has an explicit ruby version requirement >2.7.5 |
What happened?
The latest version
v3.4.2
causes a memory crash on iOS and was unable to run the application properly until I downgraded the version back tov3.4.1
and worked just fine.Steps to reproduce?
What did you expect to happen?
It should run correctly as it supposed to be
OneSignal Flutter SDK version
Release 3.4.2
Which platform(s) are affected?
Relevant log output
I got these memory logs
And also I got these output logs
The text was updated successfully, but these errors were encountered: