Skip to content

[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

Closed

Description

@alihassan143

Steps to reproduce

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 Image

Logs

Logs
[Paste your logs here]

Flutter Doctor output

Doctor output
 flutter doctor
Doctor 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!

Activity

  1. m96Ahmed commented on Aug 19, 2025

    @m96Ahmed
  2. alihassan143 commented on Aug 19, 2025

    @alihassan143
    Author

    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.

  3. darshankawar commented on Aug 19, 2025

    @darshankawar
    Member

    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 ?

  4. added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Aug 19, 2025
  5. alihassan143 commented on Aug 19, 2025

    @alihassan143
    Author

    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

  6. removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Aug 19, 2025
  7. alihassan143 commented on Aug 19, 2025

    @alihassan143
    Author

    @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.

  8. m96Ahmed commented on Aug 19, 2025

    @m96Ahmed
  9. large commented on Aug 19, 2025

    @large

    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:

    Image

    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
    Image
    Ref: #167737

  10. naseerx commented on Aug 20, 2025

    @naseerx
  11. darshankawar commented on Aug 21, 2025

    @darshankawar
  12. added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Aug 21, 2025
  13. alihassan143 commented on Aug 21, 2025

    @alihassan143
    Author
  14. removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on Aug 21, 2025
  15. 36 remaining items

  16. MirceaX2Mobile commented on Aug 30, 2025

    @MirceaX2Mobile

    @darshankawar Do you know when this fix will be on stable? #174715

  17. added
    r: fixedIssue is closed as already fixed in a newer version
    on Sep 2, 2025
  18. vashworth commented on Sep 4, 2025

    @vashworth
    Contributor

    @darshankawar Do you know when this fix will be on stable? #174715

    Fix should be on stable 3.35.3.

  19. enesakbal commented on Sep 18, 2025

    @enesakbal

    @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.

    Its worked for me, thank you

  20. github-actions commented on Oct 2, 2025

    @github-actions

    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.

  21. locked as resolved and limited conversation to collaborators on Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listc: regressionIt was better in the past than it is nowfound in release: 3.35Found to occur in 3.35found in release: 3.36Found to occur in 3.36has reproducible stepsThe issue has been confirmed reproducible and is ready to work onplatform-iosiOS applications specificallyr: fixedIssue is closed as already fixed in a newer versiont: xcode"xcodebuild" on iOS and general Xcode project managementteam-iosOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-iosTriaged by iOS platform teamworkaround availableThere is a workaround available to overcome the issue

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions