Flutter部署至App Store Connect因Asset validation failed(90035)失败求助

错误信息 #

Asset validation failed (90035)
Invalid Signature. Code object is not signed at all. The file at path [Runner.app/Frameworks/App.framework/flutter_assets/android/gradlew] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target.

问题背景 #

已启用自动签名，本地构建无控制台报错，仅通过Transporter上传时触发该错误；已尝试flutter clean、删除Podfile重建iOS/Android目录、重新启用自动签名，均未解决。

解决方案 #

1. 排查并修正Flutter资源打包配置 #

• 打开项目根目录的pubspec.yaml，检查assets配置项，确认是否错误包含了android/目录（比如- android/），若有则删除该条目，执行flutter pub get更新配置。
• 若pubspec.yaml无问题，打开Xcode的Runner Target → Build Phases → Copy Bundle Resources，检查是否存在android/gradlew相关条目，若有则移除。

2. 手动清理冗余文件并重新签名 #

• 构建Release包后，右键点击生成的Runner.app，选择「显示包内容」。
• 进入Frameworks/App.framework/flutter_assets/android/，删除gradlew文件。
• 打开终端，执行签名命令（替换证书名称为你的分发证书）：

  codesign -f -s "Apple Distribution: 你的开发者账号名称" --entitlements Runner.app/Entitlements.plist Runner.app/Frameworks/App.framework
  

• 重新使用Transporter上传修改后的包。

3. 确保Framework签名配置正确 #

• 在Xcode中进入Runner Target → Build Settings，搜索Code Signing：
  • 确认CODE_SIGN_STYLE设置为Automatic，且Signing Certificate选择分发证书。
  • 进入Build Phases → Embed Frameworks，确保App.framework的Code Sign On Copy选项被勾选。

4. 重新生成完整iOS构建配置 #

• 依次执行以下命令：

  flutter clean
  flutter pub get
  flutter build ios --release --no-codesign
  

• 打开ios/Runner.xcworkspace，手动配置签名后重新打包上传。

内容的提问来源于stack exchange，提问作者Valkyrie