Same issue when trying to run a test for my Flutter app, I am able to run the app otherwise in the simulator. Obviously this is a pretty major issue after upgrading to Sonoma 14.0 as you can't downgrade xCode to 14.x once you've upgraded to Sonoma. I am desperate for a fix, I've tried the following code added to my Podfile but it has NOT alleviate the issue: `post_install do |installer| installer.pods_project.targets.each do |target| target.build_configurations.each do |config| #config.build_settings['DEVELOPMENT_TEAM'] = '<TEAM_ID>' end end end

FIX for failing Patrol test builds (for Flutter integration testing), may work for other scenarios! I was skeptical of that the DVTAssertions warnings were the cause of the build failure, after all they are only warnings of an existing file being overwrote... Therefore I turned on verbose logging and studied each line of errors. I discovered within the verbose logs that directories and files were not permitted to be created for my test build due to sandboxing being enabled. I then studied sandboxing and found another thread that solved the build failure: [https://developer.apple.com/forums/thread/731041) For your project in Xcode, select the Target you're working with (for Patrol testing on iOS this was RunnerUITests) and choose Build Settings > [expand] Build Options > User Script Sandboxing select 'No'. Removing sandboxing allows for all build (test build in this case) files to be generated. I previously mentioned my app builds worked in another comment, and this is the reason why: sandboxing was disabled on my app's Target Runner already!