You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[3.35.1][ios]: Trying to archive the app after flutter run --debug throws Your Flutter project is currently configured for debug mode. Please run flutter build ios --config-only --release in your Flutter project to update your settings. #174015
1 debug the ios app
2 try to create archive
its show build error and show to run flutter build ios --config-only --release command every time
Expected results
it should automatically change its mode from debug to release
Actual results
its showing build error every time
Code sample
Code sample
[Paste your code here]
Screenshots or Video
Screenshots / Video demonstration
Logs
Logs
[Paste your logs here]
Flutter Doctor output
Doctor output
flutter doctorDoctor summary (to see all details, run flutter doctor -v):[✓] Flutter (Channel stable, 3.35.1, on macOS 15.6 24G84 darwin-arm64, locale en-US)[✓] Android toolchain - develop for Android devices (Android SDK version 36.0.0)[✓] Xcode - develop for iOS and macOS (Xcode 16.4)[✓] Chrome - develop for the web[✓] Android Studio (version 2025.1)[✓] VS Code (version 1.102.3)[✓] Connected device (3 available) ! Error: Browsing on the local area network for Mac’s iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac. The device must be opted into Developer Mode to connect wirelessly. (code -27)[✓] Network resources• No issues found!
The issue is not that I can’t create a release build — the problem is that every time I do some debugging in the app and then try to create a new release build, it always shows an error. It should automatically detect and create the release build, like it used to before the 3.35.0 release.
It should automatically detect and create the release build, like it used to before the 3.35.0 release.
@alihassan143 Does it happen with a counter app in latest stable version but not in previous version ? Can you give us an example wherein it didn't throw the reported error ?
Also, is your project configured for release build as well or only in debug mode ?
It should automatically detect and create the release build, like it used to before the 3.35.0 release.
@alihassan143 Does it happen with a counter app in latest stable version but not in previous version ? Can you give us an example wherein it didn't throw the reported error ? Also, is your project configured for release build as well or only in debug mode ?
it happening with every app
when trying to create archive from xcode using flutter version 3.35.0 or 3.35.1 it did not happended with 3.32.8 or earlier version
Reacted by Lars Werner, Javier del Canto Montenegro, Alessandro Defendenti and Carlos Umaña Acevedo
@darshankawar This happens when I debug the app and make changes. In previous versions, after debugging, I could directly create an archive from Xcode and it would generate a release IPA to upload to the App Store. But after version 3.35.0, I now need to run flutter build ios --config-only --release first before archiving, otherwise the build fails.
Reacted by Javier del Canto Montenegro, Zack Lemley, Prashant Ghimire, Alessandro Defendenti, valh577 and rastogiyash29
I have the same experience after 3.35.0 was released the build of my app on Xcode cloud does no longer work.
Details on error from build, exiting with code 65:
Your Flutter project is currently configured for debug mode. Please run flutter build ios --config-only --release in your Flutter project to update your settings.
I tested some simple parameters changes in my app and after 3.35.0 it fails.
Released that fails downloads this version (from logfiles):
Downloading Darwin x64 Dart SDK from Flutter engine 1e9a811...
Release that was OK had this version downloaded (from logfiles):
Downloading Darwin x64 Dart SDK from Flutter engine ef0cd00...
Edit: @darshankawar - unknown status on the counter part here
Something changed in the Flutter end here.
My ci_post_clone.sh scripts shows this for working version:
Building flutter tool...
Resolving dependencies...
Downloading packages...
Got dependencies.
Failed to find the latest git commit date: VersionCheckError: Command exited with code 128: git -c log.showSignature=false log ef0cd00 -n 1 --pretty=format:%ad --date=iso
Standard out:
Standard error: fatal: bad object ef0cd00
Returning 1969-12-31 16:00:00.000 instead.
Downloading Material fonts... 406ms
(...)
Changed 239 dependencies!
24 packages have newer versions incompatible with dependency constraints.
Try flutter pub outdated for more information.
In the non working version of 3.35.0 this error has been gone, but there are less incompatible constrains:
Building flutter tool...
Resolving dependencies...
Downloading packages...
Got dependencies.
Downloading Material fonts... 510ms
(...)
Changed 239 dependencies!
18 packages have newer versions incompatible with dependency constraints.
Try flutter pub outdated for more information.
The is project dependent, but it seems like the 3.35.x upgrade also lifted 6 packages (that I did not version control) that might could be an bad actor.
Edit2:
I included the "flutter build ios --config-only --release" in the ci_post_clone.sh and it works.
Logs shows this:
Changing current working directory to: /Volumes/workspace/repository
Building com.myapp for device (ios-release)...
Updating project for Xcode compatibility.
Upgrading project.pbxproj
Upgrading Runner.xcscheme
Automatically signing iOS for device deployment using specified development team in Xcode project: (removed)
Running pod install...
Now people must also change the Runner/Flutter/AppFrameworkInfo.plist -> MinimumOSVersion=13.0
Ref: #167737
@darshankawar This happens when I debug the app and make changes. In previous versions, after debugging, I could directly create an archive from Xcode and it would generate a release IPA to upload to the App Store. But after version 3.35.0, I now need to run flutter build ios --config-only --release first before archiving, otherwise the build fails.
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.
Activity
m96Ahmed commentedon Aug 19, 2025
alihassan143 commentedon Aug 19, 2025
The issue is not that I can’t create a release build — the problem is that every time I do some debugging in the app and then try to create a new release build, it always shows an error. It should automatically detect and create the release build, like it used to before the 3.35.0 release.
darshankawar commentedon Aug 19, 2025
@alihassan143 Does it happen with a counter app in latest stable version but not in previous version ? Can you give us an example wherein it didn't throw the reported error ?
Also, is your project configured for release build as well or only in debug mode ?
alihassan143 commentedon Aug 19, 2025
it happening with every app
when trying to create archive from xcode using flutter version 3.35.0 or 3.35.1 it did not happended with 3.32.8 or earlier version
alihassan143 commentedon Aug 19, 2025
@darshankawar This happens when I debug the app and make changes. In previous versions, after debugging, I could directly create an archive from Xcode and it would generate a release IPA to upload to the App Store. But after version 3.35.0, I now need to run
flutter build ios --config-only --releasefirst before archiving, otherwise the build fails.m96Ahmed commentedon Aug 19, 2025
large commentedon Aug 19, 2025
I have the same experience after 3.35.0 was released the build of my app on Xcode cloud does no longer work.
Details on error from build, exiting with code 65:
I tested some simple parameters changes in my app and after 3.35.0 it fails.
Released that fails downloads this version (from logfiles):
Downloading Darwin x64 Dart SDK from Flutter engine 1e9a811...
Release that was OK had this version downloaded (from logfiles):
Downloading Darwin x64 Dart SDK from Flutter engine ef0cd00...
Edit:
@darshankawar - unknown status on the counter part here
Something changed in the Flutter end here.
My ci_post_clone.sh scripts shows this for working version:
In the non working version of 3.35.0 this error has been gone, but there are less incompatible constrains:
The is project dependent, but it seems like the 3.35.x upgrade also lifted 6 packages (that I did not version control) that might could be an bad actor.
Edit2:
I included the "flutter build ios --config-only --release" in the ci_post_clone.sh and it works.
Logs shows this:
Now people must also change the Runner/Flutter/AppFrameworkInfo.plist -> MinimumOSVersion=13.0

Ref: #167737
naseerx commentedon Aug 20, 2025
darshankawar commentedon Aug 21, 2025
alihassan143 commentedon Aug 21, 2025
36 remaining items
Remove build configuration mismatch warning (flutter#174715)
Remove build configuration mismatch warning (flutter#174715)
MirceaX2Mobile commentedon Aug 30, 2025
@darshankawar Do you know when this fix will be on stable? #174715
[CP-stable]Remove build configuration mismatch warning (#174725)
vashworth commentedon Sep 4, 2025
Fix should be on stable 3.35.3.
enesakbal commentedon Sep 18, 2025
Its worked for me, thank you
Remove build configuration mismatch warning (flutter#174715)
Remove build configuration mismatch warning (flutter#174715)
Remove build configuration mismatch warning (flutter#174715)
github-actions commentedon Oct 2, 2025
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 -vand a minimal reproduction of the issue.Remove build configuration mismatch warning (flutter#174715)
Remove build configuration mismatch warning (#174715)