After investigating, i think the root cause was the xcode_backend.sh will mark the files under Flutter.framework tobe readonly.

For someone run into this issue, try modify the $FLUTTER_ROOT/packages/flutter_tools/bin/xcode_backend.sh for workaround:

--- a/packages/flutter_tools/bin/xcode_backend.sh
+++ b/packages/flutter_tools/bin/xcode_backend.sh
@@ -141,7 +141,7 @@ BuildApp() {
     mkdir "${derived_dir}/engine"
     RunCommand cp -r -- "${flutter_podspec}" "${derived_dir}/engine"
     RunCommand cp -r -- "${flutter_framework}" "${derived_dir}/engine"
-    RunCommand find "${derived_dir}/engine/Flutter.framework" -type f -exec chmod a-w "{}" \;
+    RunCommand find "${derived_dir}/engine/Flutter.framework" -type f -iname '.h' -exec chmod a-w "{}" \;
   else
     RunCommand rm -rf -- "${derived_dir}/Flutter.framework"
     RunCommand cp -r -- "${flutter_framework}" "${derived_dir}"

I'm using a flutter module inside of existing app. The upgrade instructions at https://github.com/flutter/flutter/wiki/Upgrading-Flutter-added-to-existing-iOS-Xcode-project have the xcode_backend.sh build phase removed.

I did a similar command in the Pods/Target Support Files/Pods-TARGET/Pods-TARGET-frameworks.sh just above the /usr/bin/codesign command.

/cc @jmagman

Duplicate of #39507.

If someone can flutter update (you must be on the master channel to use add-to-app modules!) and let me know if the issue is fixed, that would be awesome!

Reopening, @OHeroJ says this is still happening.

@OHeroJ Can you run flutter clean before you build to make sure the old read-only files are removed?

Reopening, @OHeroJ says this is still happening.

@OHeroJ Can you run flutter clean before you build to make sure the old read-only files are removed?

I see execution flutter after the clean, .ios folder disappeared; run flutter build ios the .ios folder appeared(regenerate), in flutter stable channel;

I mean you would need to merge the branch to the stable branch。

I will try a test in master channel, then tell you result.

$ flutter channel master
$ flutter upgrade
$ flutter clean
$ flutter build ios

Building com.mtd.iosFlutterModule for device (ios-release)...
Automatically signing iOS for device deployment using specified development team in Xcode project: BB535CKPXQ
Running pod install...                                              2.6s
Running Xcode build...

 ├─Building Dart code...
  439.3s (!)
 ├─Generating dSYM file...                                   0.4s
 ├─Stripping debug symbols...                                0.4s
 ├─Assembling Flutter resources...                           4.3s
 └─Compiling, linking and signing...                        40.5s
Xcode build done.                                           498.2s
Built /Users/oheroj/Desktop/TN/flutter_module/build/ios/iphoneos/Runner.app.

in master channel run well! @jmagman ，will combine the branch to the stable branch?

same problem

@jmagman

I can confirm that it now works in master channel for me as well.

@jmagman Do you still need me to file a new issue now that chmod is going to be removed ?

@jmagman Do you still need me to file a new issue now that chmod is going to be removed ?

@vitor-gyant If the Podfile you generated on the stable channel works but the one generated on master doesn't, a new issue would be very helpful.

The same error for our app on stable channel.

Flutter 1.9.1+hotfix.6 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 68587a0916 (3 months ago) • 2019-09-13 19:46:58 -0700
Engine • revision b863200c37
Tools • Dart 2.5.0

On master channel we have no this error and can build the app.

Posted a workaround here: #39507

The same error for our app on stable channel.

Flutter 1.9.1+hotfix.6 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 68587a0916 (3 months ago) • 2019-09-13 19:46:58 -0700
Engine • revision b863200c37
Tools • Dart 2.5.0

On master channel we have no this error and can build the app.

@ivanesi The fix is on stable 1.12.13 https://flutter.dev/docs/development/tools/sdk/releases?tab=macos. Try running flutter upgrade.

Upgrading to master is NOT a valid solution, as master does not deploy to Huawei devices properly. The only way is to use 1.9.1 until THAT is fixed.

Upgrading to master is NOT a valid solution, as master does not deploy to Huawei devices properly. The only way is to use 1.9.1 until THAT is fixed.

#45189 is on all channels, not just master. If you have to stay on 1.9.1, you can manually patch your Flutter SDK's packages/flutter_tools/bin/xcode_backend.sh to https://github.com/flutter/flutter/blob/v1.12.13-hotfixes/packages/flutter_tools/bin/xcode_backend.sh. The Flutter SDK is a git repo, and Flutter channels are branches. To reset, make sure you run git checkout . from your SDK folder before you flutter channel or flutter upgrade again (you've voided your easy-upgrade warranty at that point)

Moved from v1.9.1+hotfix.6 to v1.11.0 .

To change flutter version to 1.11.0 just run

flutter version v1.11.0

This fixed this issue for me , tried all other other highly voted solutions but none worked.

To complete solve this! go here:- https://stackoverflow.com/a/65473410/10563627

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.