Closed devmuaz closed 5 months ago
Possibly a duplicate of #608. I am running into this as well
running into the same weird log during the crash on iOS with 3.4.2
@chrisvidal for now, you can use the previous stable version 3.4.1
which works just fine.
@devmuaz same error with the 3.4.1
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD 1 Library missing
Library not loaded: @rpath/OneSignalExtension.framework/OneSignalExtension
@chrisvidal I believe that the version is still the same in the pubspec.lock
file, you need to delete it and run:
flutter pub get
If still not working, clear the pub cache by running:
flutter pub cache clean && flutter pub get
starting a blank project with 3.4.1
and see...
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
rm Podfile.lock
pod cache clean --all
pod install --repo-update
this work for me Go to Project --> Targets --> [Application Name] --> Frameworks, Libraries, and Embedded Content section. Click + icon --> Type OneSignal in the search box --> Select OneSignalCore.xcframework and click Add button. Do the same for OneSignalOutcomes.xcframework. Check Embed and Sign on both.
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.
this work for me Go to Project --> Targets --> [Application Name] --> Frameworks, Libraries, and Embedded Content section. Click + icon --> Type OneSignal in the search box --> Select OneSignalCore.xcframework and click Add button. Do the same for OneSignalOutcomes.xcframework. Check Embed and Sign on both.
Clean build folder and build.
That's what worked.
I am still using onesignal_flutter: 3.4.1
are there any updates on this issue? Thanks!
having this issue on my Intel Mac, but on on M1 chip.
upgrading ruby and cocoapods as well as using onesignal_flutter: 3.4.1
fixed the issue for my Intel Mac
upgrading ruby and cocoapods as well as using
onesignal_flutter: 3.4.1
fixed the issue for my Intel Mac
what versions of ruby and cocoapods have you upgraded?
upgrading ruby and cocoapods as well as using
onesignal_flutter: 3.4.1
fixed the issue for my Intel Macwhat 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?
Hi @AndreiMisiukevich,
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
rm Podfile.lock
pod cache clean --all
pod install --repo-update
Hi @nan-li, thanks for the response! I haven't tried it yet.
Do you think the steps you shared help with the latest version of OneSignal SDK? I saw this comment https://github.com/OneSignal/OneSignal-Flutter-SDK/issues/613#issuecomment-1433908773 and thought it would help only for version 3.4.1, which works like a charm for me even without any addition steps.
Hi @AndreiMisiukevich,
I think these steps are good for 3.4.2+.
I was able to personally reproduce this issue after I updated my Xcode from 14 to 14.1 and using OneSignal Flutter SDK 3.4.2.
My ruby version was also 2.6.8
.
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