[Critical Bugs] : Build successfully but crash when the app launch in IOS #608
Comments
|
@foongef are you using the latest package? onesignal_flutter: ^3.4.2 I also had the crash wih onesignal_flutter: ^3.4.1, now I am testing it with the latest. |
|
@imajercsik yes i have tried 3.4.2 and 3.4.1. Both version also crashed after built successfully. |
|
Same thing for me |
|
Works fine for 3.4.0 |
|
For me it is crashing with 3.4.0, 3.4.1 and 3.4.2. [✓] Flutter (Channel stable, 3.3.6, on macOS 13.0 22A380 darwin-x64) |
|
Same here, but It works fine for me on 3.4.1 [✓] Flutter (Channel stable, 3.3.6, on macOS 13.0 22A380 darwin-arm, locale en-BR) |
|
It might be an SDK problem |
|
3.4.0, 3.4.1, 3.4.2 also crashed. Anyone has the solution? |
|
any one found a solution? Am facing the same issue |
|
same problem here |
foongef
changed the title
|
same here |
|
I have the exact same issue! Tested 3.4.1 and 3.4.2 |
|
Same issue. Version 3.4.2. Works fine on simulator but not working on a physical device |
|
Same issue - This is critical and stopping the release of new versions of any apps using the library. Please can someone from the OneSignal team chime in here ASAP? Thanks. |
|
i'm using onesignal_flutter 3.3.1 and it works... |
Mine cannot even work on simulator. |
Contacted them and was told to just refer to the migration guide. |
|
What? That's kinda ridiculous, I don't see anything specific in the migration guide, unless I'm missing something? I downgraded to 3.4.1 and it worked fine btw, so it's something to do with 3.4.2 for sure. |
Oh.. Both 3.4.1 and 3.4.2 don't worker 2.6 and did everything necessary as indicated in the migration guide. |
|
Can you please post a link to the migration guide you're referring here?
…On Fri, 4 Nov 2022, 02:38 hosaysg, ***@***.***> wrote:
What? That's kinda ridiculous, I don't see anything specific in the
migration guide, unless I'm missing something? Link please?
I downgraded to 3.4.1 and it worked fine btw, so it's something to do with
3.4.2 for sure.
Oh.. Both 3.4.1 and 3.4.2 don't worker 2.6 and did everything necessary as
indicated in the migration guide.
—
Reply to this email directly, view it on GitHub
<#608 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADM6KXVD4E7P4JABIGLBCQ3WGSVNFANCNFSM6AAAAAARS4EXMQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hi everyone, thank you for reporting this.
Update: We are not able to reproduce, may be related to new Xcode/Flutter/Cocoapods versions or podfile setup. |
|
Hello, @daveshirman I don't believe there will be any further information that will help in the migration guide. Can you share your podfile please? Also is the Notification Service Extension crashing, or the app itself? |
I still don't know what migration guide you're referring to, please kindly share the link at least. At my end with 3.4.2: App loads, immediately crashes with the error: Library not loaded. The app compiles and runs fine with 3.4.1 as I mentioned. My Podfile |
|
The same issue with failed loading OneSignalExtension framework. As a dirty workaround, you may link the framework directly to your project by adding it to the linked binaries list of your project (not pods project). |
|
Hello there |
|
Same here, did not found any solution yet :(. @nan-li do you have an update? Thanks! |
|
same here |
|
@nan-li Please check crash log file here: Flutter doctor Doctor summary (to see all details, run flutter doctor -v): Already try onesignal_flutter: ^3.3.0 to latest flutter version. |
|
This solution work for me. |
It worked for me too, thanks! Still waiting the official fix! |
|
@nan-li, below the confs set of a project that's currently failing with
Dependencies on dependencies:
flutter:
sdk: flutter
flutter_localizations:
sdk: flutter
adeptarch_base: ^5.0.3+24
adeptviews: ^6.0.0+60
adeptannotations: ^2.1.1+8
cloudinary_sdk: ^4.0.2+10
cloudflare: ^1.3.1+12
oauth_webauth: ^3.1.2+13
onesignal_flutter: ^3.4.2
page_view_indicators: ^2.0.0
connectivity_plus: ^3.0.2
sentry: ^6.15.0
cached_network_image: ^3.2.2
badges: ^2.0.3
image_picker: ^0.8.6
chewie: ^1.3.5
apivideo_live_stream: ^1.0.7
firebase_analytics: ^10.0.4
google_maps_flutter: ^2.2.1
google_maps_webservice: #^0.0.20-nullsafety.5
git:
url: https://github.com/luis901101/google_maps_webservice
ref: 256fab72e921942cecc88d3f79b6b71a623d189d
permission_handler: ^10.2.0
geolocator: ^9.0.2
geocoding: ^2.0.5
flutter_appauth: ^4.2.1
duration: ^3.0.12
uni_links: ^0.5.1
share_plus: ^4.5.2
flutter_typeahead: ^4.1.1
uuid: ^3.0.6
qr_flutter: ^4.0.0
path_provider: ^2.0.11
get: ^4.6.5
keyboard_actions: ^4.1.0
intl_phone_number_input: ^0.7.1
flutter_html: ^2.2.1
mobile_scanner: ^3.0.0-beta.1
qr_code_scanner: ^1.0.1
animations: ^2.0.7
carousel_slider: ^4.1.1
json_annotation: ^4.7.0
html_unescape: ^2.0.0
chaleno: ^0.0.6
flutter_scrolling_fab_animated: ^0.1.4
google_fonts: ^3.0.1
responsive_sizer: ^3.1.1
flutter_rating_bar: #^4.0.1
git:
url: https://github.com/sarbagyastha/flutter_rating_bar.git
ref: ba0dda2338b27c8a568c9c753cb53fb5a336a676
equatable: ^2.0.5
numeral: ^2.0.1
flutter_cache_manager: ^3.3.0
sleek_circular_slider: ^2.0.1
copy_with_extension: ^4.0.4
hive: ^2.2.3
hive_flutter: ^1.1.0
html_editor_enhanced: ^2.5.0
visibility_detector: ^0.3.3
|
|
I found my mistake, my onesigal target name was not exactly "OneSignalNotificationServiceExtension". I adjusted and it worked. |
|
Same here - Flutter 3.3.8 new project, do the onesignal integration using onesignal_flutter: ^3.4.2, startup crash:
Fixing at 3.4.1 solves the issue. Interestingly I only see this when building on our Codemagic instance, locally I can use ^3.4.2 |
Hmmm, interesting, maybe something related to Apple M1 procesors? Codemagic is using m1 for CI/CD, and in my case my macbook pro is also a m1 procesor... 🤔 |
Actually I don't think so, I had my colleague build with his M1 machine and it was also ok. However we did not try much else. Once it built and ran OK I moved on. We should probably have tried more like clearing xcode derived data and cleaning the Flutter project |
|
|
|
@Zfinix this works for me, but only if I |
|
Mine worked without signing
On Mon, 21 Nov 2022 at 5:10 AM, Seth Westphal ***@***.***> wrote:
@Zfinix <https://github.com/Zfinix> this works for me, but only if I Embed
and Sign the framework.
—
Reply to this email directly, view it on GitHub
<#608 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGE3JSICWPR2RC6F6BLTE4LWJLY3RANCNFSM6AAAAAARS4EXMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Chiziaruhoma O.
|
|
Hello ..!
Is this what you're saying?
Thanks! |
|
Facing same issue here, with 3.4.0, 3.4.1, and 3.4.2 version on a new Flutter 3.0 project built on a Mac M1 chip as well. |
|
same here |
This worked for me |
|
Just tested with latest version 3.5.0 and the same error occurred. It failed complaining about OneSignalCore and OneSignalOutcomes, I finally ended up adding it manually like:
If these steps are necessary to be manual I think it should be explained in documentation. |
|
Make sure you are using Cocoapods 1.11.3 and try the below code. We have seen this issue when using versions lower than 1.11.3 |
Done:
|
|
@luis901101 Try updating to ruby 2.7.5+. I believe Cocoapods 1.11.3 has an FFI dependency that requires a higher ruby version than you are using so I am not sure how Cocoapods 1.11.3 installed succsesfully. Regardless try updating Ruby version and see if that helps. Out of curiosity did you install Cocoapods directly from the gem or using Homebrew? |
I can't remember right now, but I think it was homebrew |
After updating ruby to latest |
|
The following worked for me -
if it says CocoaPods is broken then run the following command - sudo gem install cocoapods This should solve the problem. |
this fixed for me |
I was able to Identify that this issue doesn't happen on M1 after following this steps |
|
This answer solved it for me |
|
having this issue on my Intel Mac, but on on M1 chip. |
|
Hello there, I’m facing the same crash. On xCode 14.2 / Mac Book Pro 13.0.1
Termination Reason: DYLD 1 Library missing Kindly help. urgent |
|
@rackNeha There are some workarounds mentioned above, but perhaps the latest Cocoapods release (1.12.+) fixes this issue? Cocoapods had not released a new version for almost a year and did not well support Xcode 14 so I am hoping their new release fixes issues like these. |
and others
Crash message bellow
The text was updated successfully, but these errors were encountered: