-
Notifications
You must be signed in to change notification settings - Fork 396
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
build porblem on macos sonoma xcode 15 #600
Comments
problem is not about flutter_secure_storage |
I replaced all DT_TOOLCHAIN_DIRs with TOOLCHAIN_DIR. it still gives some errors but at least it builds now. |
same issue |
I think it's not related specifically to flutter, I have it on a flutter project and react-native one |
I open an empty project and it gives me the same error. i think its macos sonoma or xcode 15 problem. |
I have same error, just after upgrading to Sonoma :| |
Same here, Xcode 15 MacOS ventura 13.6 |
same here :( |
This one works on mine, Step 1. Add this line into post_install do |installer| inside podfile file installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
xcconfig_path = config.base_configuration_reference.real_path
xcconfig = File.read(xcconfig_path)
xcconfig_mod = xcconfig.gsub(/DT_TOOLCHAIN_DIR/, "TOOLCHAIN_DIR")
File.open(xcconfig_path, "w") { |file| file << xcconfig_mod }
end
end Step 2: Update Build Phases (Extension)
Step 3. Clean your flutter project
|
For me, a simple flutter clean did the job. |
I did follow your step but nothing worked |
its works fine post_install do |installer| |
Seeing this running iOS simulator tests on a bitrise machine, xcode 15 |
Have someone find a fix or workaround for this? Having the same issue here, xcode 15 and Ventura 13.6. |
Why is this closed? Have the same problem. XCode 15.0, Sonoma 14.0 |
i still have the same issue xcode 15, sonoma 14 :/ |
I fixed this issue by uninstalling cocoapods and rebuilding with the latest ruby 3.2.2 |
It's an XCode MacOS Problem not a |
Same problem here!!! :( |
I'm having this exact issue after upgrading to Sonoma, Xcode 15.1, I can run the app fine in the simulator but I can't not make a test build, it fails with the same error as in the logs above (many times over). |
same issue here |
I have fixed this issue in regards to my test builds failing, for me I had to go into Xcode, find my Target for tests which was RunnerUITests (for Patrol testing) and update Build Settings > Build Options > User Script Sandboxing to 'No'. It appears the warnings above are not the root cause for the build failures, turn on verbose logging and study the other errors present, they are the cause for the build failures (at least in my case). Hope this helps! |
Having similar issue with React Native |
Before line in podfile |
Adding |
I do not have firebase in this project. xcode 15 have a problem with old projects but we have a lot of solution in this issue. And your solution will probably work in most cases. |
worked for me as well, in my case I installed the latest version of cocoapods (from homebrew) |
I'm using macOs Sonoma v14.1.0 and Xcode 15.0. I got the same error |
try this
|
Same problem here. This problem is old, I just updated, you guys must have found a way to fix it by now. Please help. |
Might be a slightly different error, but I fixed this by first copying the contents of LaunchScreen.storyboard, deleting LaunchScreen.storyboard, and re-creating it. Something strange I noticed (that may be a bug on Apple's end) is that when you delete a .storyboard file and recreate it within xcode, it creates the file in the wrong directory. The file must be in the ios/[YOUR-PROJECT] directory. |
I had no idea about this setting, but it makes sense for my case. Here's a blog post on the setting from Daniel Jalkut, for others to understand it better. https://indiestack.com/2023/06/xcode-build-script-sandboxing/ |
i have updated my computer to macos sonoma. as xcode does not work in this version, i downloaded xcode 15 beta. there was no problem in my project until i added secure storage. The cause of the problem is uncertain, and could be related to macOS, the pod, or Xcode.
The text was updated successfully, but these errors were encountered: