In the new Xcode 12 there was a great change to tabs, so that they don't act like individual windows. However when using this new tab mode there is a very annoying situation when using cmd+shift+o to open a file in a new tab. It opens the tab, with its name in italics. If I don't do anything with the new "temporary" tab, and try to open another file, it will replace the temporary tab instead of opening another one. I frequently look at unit test coverage reports, or test failure reports, open multiple files in separate tabs and then work on them one at a time, rather than having to keep going back and forth. The new tabs don't remember scroll positions in these files and have to process them every-time they open, so its quite slow, especially with UI Test reports. Now I have to open a tab, make some meaningless edit, go back wait for it to process, open another tab, make a meaningless edit, go back, wait for it to process etc. Is there anyway to change this behaviour, so cmd+shift+o opens a full fledged document tab without this "temporary" state. Can't seem to find anything in preferences, or else I just know know the names of these things.

Just upgrades to Xcode 12. I'm working on writing a UITest and I can't get the record button to work or any test to run. Record button: Seems to activate, and launches simulator. Highlights one of the lines of code with the semi-transparent white bar as it always has. Doesn't capture any taps or report any errors, just does nothing. Running tests: iOS 14 simulator: Underlying error: Failed call to AXDisabledAccessibilityOnTermination: kAXErrorCannotComplete iOS 13.3 simulator: Underlying Error: Timed out waiting for AX loaded notification I've tried restarting xcode, restarting simulators etc. Can't get anything to work. I still haven't gotten an answer to my last question about Xcode 11 Server timing out with "AX loaded notification": https://developer.apple.com/forums/thread/656364, seems to be related. Really need someone from apple to look into these issues.

My XCUITests fail randomly with the message: Initialization failure for UI testing: Timed out waiting for AX loaded notification This happens randomly, but frequently. I currently have tests running on two simulators: iPhone 11, iOS 13.6 iPhone SE (1st generation), iOS 12.2 I've tried switching simulators to other iOS versions, other phone types to see if that makes a difference. But it doesn't. Sometimes both run fine, sometimes one fails, sometimes they both do. I'm using Xcode server setup as a second user on my mac. Using: Xcode: 11.6 Mac OS: 10.5.4

I'm using Xcode 11 and Xcode server to try build and upload my app to TestFlight. Now i've hit a point where I can't get even a basic build/export to work. I was trying to use a custom ExportOptions.plist:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>method</key> <string>app-store</string> <key>teamID</key> <string>YOUR_TEN_CHARACTER_TEAM_ID</string> <key>destination</key> <string>upload</string> </dict> </plist>But then I get an error saying "Upload" is not supported by Xcode server. Suggestions online are to leave it as "Export" and use this to upload in a post-integration script: altool --upload-app -f $XCS_PRODUCT -u <username> -p <app-specific password> So I did that and I've tried setting the bot to use either:Archive export: Installable ProductArchive export: Installable Product & Thinned Variantsinstead of the custom plist. But now my Archive step is failing with the below error before even getting to the trigger:Build Service Error: exportArchive: exportOptionsPlist error for key 'destination': expected one of {upload}, but found exportI've tried removing the trigger to see if that was causing an issue, but its not. Now my bot is simply trying to archive and export the project and i'm getting this error about destination should be upload ... which isn't supported.Archiving the app and uploading from the "Distribute app" button manually works fine. So there are no cert issuesAny help would be appreciated. I was hoping to do this without adding more tools as it should be possible on its own.