Open cyanglaz opened 9 months ago
Workaround: In XCode, moving the "Embed Foundation Extensions" build phase to above "Run Script" solved the issue.
At the moment, I'm not sure if there is anything Flutter can do to prevent this.
This order works for me with an embedded watch app:
I'm not actively working on this since there is an easy workaround.
The change of "Embed Foundation Extensions" worked for me, but is there any reason why it happens? can it affect the performance of my app?
since I applied the above mentioned solution, the flutter project started to create a build folder inside the ios folder, does anyone know why this is happening? how can I fix it?
without realizing it I made a commit but today while detailing I realized the existence of this folder that was not there before.
I solved in this order. #135739
I re-downloaded xcode 14.3 and run it with the following command line. /Applications/Xcode14.3.app/Contents/MacOS/Xcode --help
This orders works for me.
This order works for me with an embedded watch app:
WOOWW, THANK YOU! Other solution were long and useless
What could be wrong if I have everything molested like this. Why does it not work?
@dam-ease
I created a test project and added a notification service extension to xCode. I changed the build phases there in the order of the queue and attach a screenshot.
But I still get an error when building on a physical device. I have no idea at all how to solve it, because on my second computer on m2 pro, the same project runs without problems
I updated the App Clip website to reflect the order needed for the build phases.
Drag Embedded App Clips to above Thin Binary.
https://github.com/flutter/website/pull/10145/files#r1489922511 https://docs.flutter.dev/platform-integration/ios/ios-app-clip#step-2---add-an-app-clip-target
This should also be done for https://docs.flutter.dev/platform-integration/ios/app-extensions
Finally, I managed to install the application on a real device in --release mode and all the others and finally i can do archive for my app!
The problem of Command ValidateEmbeddedBinary failed with a nonzero exit code was solved for me, which was related to the NotificationService. Although it is strange that on my working mac mini m2 pro there were no problems with assembly, but on my home m2 macbook it was not possible in any way.
Apparently, xCode was updated and I was able to go to the error log and see the problem, although the error was not clickable before.
And so, I found such an offer there: "The CFBundleShortVersionString string of the application extensions (3.0.0) must match the string containing the parent application (3.0.5)."
I started searching the project for version 3.0.0 and found a match with MARKETING_VERSION. I found the MARKETING_VERSION code in my Notification Service, changed it to the desired product version 3.0.0 -> 3.0.5 and everything worked!
I do not know how this can happen at all, some kind of magic, I'm shocked :)
Is there a workaround that doesn't require opening the project with XCode?
I also have the same issue.
I also have the same issue.
part of https://github.com/flutter/flutter/issues/124287
When building iOS app extension with XCode 15, an error has shown:
This error prevents Flutter from supporting app extension for iOS 17 and above.