Error when build ios app with Flutter 2.0.6 and null safety #389
Comments
|
I am also having the same error. |
|
Same here... Can't understand the #374 solution. |
|
Seems similar to this Flutter issue from last year. Can you see if |
|
@emawby No, I don't have this file |
|
@emawby I also don't have this file |
|
@rovkinmax @nickscamara I am not able to reproduce this issue. Are you able to share the contents of your custom configurations? A sample project with this issue would also be very helpful. |
|
@emawby Yep, check this one https://github.com/rovkinmax/OneSignalSDKProblem |
|
@rovkinmax So from my testing some of the configs worked and some didn't. You had the Runner Scheme set to use the release-prod config when running (this is usually a debug config). |
|
without OneSignal this project builds fine and I have no idea how fix it for onesignal |
|
This is an issue with the custom configuration setup since the project runs fine with the Debug and Release configs. How were these configs generated and how are you using them? |
|
This Flutter issue also seems similar flutter/flutter#78436 |
|
@emawby I made custom config according this article https://github.com/surfstudio/SurfGear/blob/dev/docs/en/best_practice/flavors/flavors_for_devs.md |
|
Something about those configs is making Flutter try to add onesignal_flutter to the NotificationServiceExtension when it shouldn't. The NSE only needs the OneSignal (iOS Native) SDK not the flutter SDK. If you can use the default configs instead you should. To change the run target for the scheme go to edit scheme -> run -> Build Configuration and select Debug. |
|
This error appears when I want to run the app on the simulator. I removed the extension and the app worked, and after adding it back by following the official steps, it stopped working. |
|
@GyuriMajercsik This appears to be an architecture issue. What is the value of the following build settings for both your app and NSE targets? |
|
Are you referring to this ?
|
|
Yes I am not seeing the simulator architectures there only the device ones |
|
This one ? I'm not sure where to look at. |
|
This thread has lots of good suggestions for you to try, but in addition to the build error You are using Standard Architectures (arm64, armv7). If you are not running on an Apple Silicon mac then you probably have intel based simulators (x86_64) so you need to include those architectures as well. |
|
I see this issue too, but adding x86 doesn't make a difference.
|
|
I found solution for this problem:
|
|
This unfortunately doesn't fix the issue I'm facing. ... The release build still works but running in the simulator doesn't. Want to also mention that it did work before. Probably after updating xCode something is not compatible anymore ... |
|
It did not work for me either... |
|
@GyuriMajercsik if you updated from Xcode 11 to Xcode 12 you are likely experiencing one of the architecture issues that were very common upon release of Xcode 12. I don't think this issue is related to OneSignal |
|
Might be the case, but after I removed everything OneSignal related it started to work... |
|
@GyuriMajercsik I had very similar looking error as rovkinmax when working on Share extension (after update to flutter 2.0.6, Xcode 12.5). Removing the values in Build Settings / Other Linker Flags for the mentioned extension seemed to fix it for me. |
Just a heads up, when using this solution, the second step was not necessary and it actually broke my service extension for confirmed deliveries. |
Description:
After migrating to null-safety and flutter 2 I get problem with ios build:
I run
flutter clean; rm ios/Podfile.lock pubspec.lock; rm -rf ios/Pods ios/Runner.xcworkspace; flutter run --flavor dev -t lib/main_dev.dartEnvironment
Steps to Reproduce Issue:
Anything else:
Also I found this issue but I don't understand solution from it
#374
Logcat output
The text was updated successfully, but these errors were encountered: