-
Notifications
You must be signed in to change notification settings - Fork 27.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MacOS 14.0 & Xcode15] "failed to write to a file" error during build #135199
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@wanyangye @ImagineBoom I haven't had macOS 14.0 yet but I found this answer that you can try ti see if it works. If it doesn't work, please confirm:
Thanks! |
This comment was marked as off-topic.
This comment was marked as off-topic.
this file is flutter run -v info |
This comment was marked as off-topic.
This comment was marked as off-topic.
error: Sandbox: rsync.samba(44082) deny(1) file-write-create /Users/steven/Steven/Work/Code/PrintHub/Client/flutter/client/build/macos/Build/Products/Debug/FlutterMacOS.framework (in target 'Flutter Assemble' from project 'Runner') warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner') |
This comment was marked as off-topic.
This comment was marked as off-topic.
@wanyangye I notice this is indeed permission error on your output log (at
You can try the following suggestion to see if it works. @ImagineBoom I can see the same Warning on your output log (at Regarding the initial warning, I will label this for other's input. Initial warning (from output log files)[ +37 ms] 2023-09-21 18:35:45.108 xcodebuild[18082:138468] [MT] DVTAssertions: Warning in
/System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22267/IDEFoundation/Provisionin
g/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103
[ ] Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists.
[ ] Function: createItemModels(for:itemModelSource:)
[ ] Thread: <_NSMainThread: 0x600002620240>{number = 1, name = main}
[ ] Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. |
I've retitled this to be about the error, since it was reported as a build error, and hidden the screenshot of the unrelated and harmless warning. @ImagineBoom Please file a new issue about the warning you are seeing, since that's not related to the error. |
I ran across this in a couple Xcode/Sonoma betas. It disappeared for one developer beta (maybe the 6th beta), then reappeared in a later one. I can repro on last week's release candidates. The warning reads as though part of the issue is a bug with Xcode incremental builds but I suspect it's likely that our build wiring is out-of-the-ordinary enough that we might be hitting some unusual edge-case. In testing with a non-Flutter (AppKit/Swift) app, the same warning is emitted during commandline builds via |
After testing with Xcode Version 15.0 (15A240d), I'm still seeing this error both in Flutter and non-Flutter app builds that are built from the command-line. |
its not work。I've followed the advice, and it's not working. I have just upgraded to MacOS14 Xcode15 to run the flutter project when this prompt appears, before the latest version of MacOS13 and the latest version of Xcode14, there is no problem. |
OK, I have filed this issue #135277 Thanks! |
@wanyangye the error you're experiencing is unrelated to the warning here
It's due to this error:
which was filed in: #132755 This is caused by an issue in CocoaPods, which was fixed in: CocoaPods/CocoaPods#12009 However, as far as I'm aware, they haven't yet published a new release that includes their fix, so you'll need to rely on our workaround. Please make sure you've got the latest Flutter version installed. You may need to switch Closing as a duplicate of #132755. |
This is off-topic for this bug; however, you can see our Supported deployment platforms page for details. Short answer: 10.14 (Mojave) is the minimum required version today. This is because Flutter requires Metal support. If you need support for older versions of macOS, you'll need to use an older version of Flutter (and possibly older version of Xcode). |
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 |
Steps to reproduce
I experienced a compilation error after upgrading to MacOS 14.0 Xcode15。
[Edited to hide, as this picture is of an unrelated warning]
![WX20230921-123454@2x](https://github.com/flutter/flutter/assets/44550529/ab7c06d8-8929-4d3a-88c2-98135ff114e8)Expected results
buildinfo.log
Actual results
buildinfo.log
Code sample
Code sample
Screenshots or Video
Screenshots / Video demonstration
Flutter Doctor output
flutter doctor -v
The text was updated successfully, but these errors were encountered: