“file uri scheme”

Also, as the original poster points out, the scheme now shows the device (iPad Air) and the simulator identifier (i.e.: 085BD3A4-CC9E-4717-AF2F-E08106BB7A88) There is no reference to the iOS of the scheme, so it's just hit-and-miss as to what iOS each scheme tests. That makes it difficult - to say the least - to test an app against all devices/iOSs.

I fixed this by going to Product-Scheme-Edit scheme select RUN, I had arguments passed on launch check box ticked, but were empty, so unticked the box. hey presto, my app would run on simulator. Solved for me.

Hello Benjamin, the workaround I found is to disable GPU Frame Capture. Menu Product | Scheme | Edit Scheme. under the Options tab, set GPU Frame Capture to disabled Regards David

Well, it happened for me after renaming the project. It is just a wrong setting in the Appstoreconnect Xcode Cloud tab. For me it was in the Actions Archive - IOS section, Scheme dropdown. I have selected the correct scheme and build succeeded.

iOS is case sensitive..CR2 is not the same as .cr2, .Cr2, .cR2, etc.Be sure to match the file name case with the image name used in your code. Might want to get into the habit of only/always using lower case, as an example, just to avoid such issues in the future. Whichever scheme you adopt, be consistent.

Yes, I tried doing that. Both through Build Phases and under Schemes by creating Post-Run/Post-Build Scripts. Neither of the tries worked for me.Anyways, I think this will not work as I will have to change the CMake for the project to access the shared object file to run even through the terminal. Thank you so much for taking time out and replying to my issue.RegardsJayam Patel

I even do not get an error by the Thread Performance Checker but keeping the option enabled in Xcode 15.3 results in horrible performance of the app during the full utilization of the app (I'm making intensive use of background threads). The only option currently possible is deactivate this feature in Debug Scheme. (Filed bug report: FB13681777)

I have seen this issue on other versions on macOS as well; I don't think this is specific to this version. You will need to trust the certificate when on the site click the padlock. Show the certificate in the details you should see the CA Issuers, click on the URI. (This will ensure the correct cert required is downloaded) it could be the ones in your keychain may vary. You can then add this certificate into keychain.

Quinn's should be the accepted answer (sorry, this should've been a comment on that—I clicked the wrong button and don't see how to fix it). @eskimo Quinn, Any chance you could push to get the x-apple.systempreferences URL scheme properly documented? It seems like something that user-friendly apps need to be able to do, and people are doing it anyway, so it would be great to have it documented explicitly as stable API somewhere outside of a header file (which only gives two specific examples for Full Disk Access, which is not the location desired here). I understand that things tend to move around in System Settings, but it seems like some needs to commit to supporting a scheme or other API that will allow apps to direct people to where they need to go.

Adding more information on this problem. The UI tests are in a separate project in the same workspace. We split this way to reduce the amount of conflicts in the project file since the xcuitests are written by a separate team and the app project gets so many updates per day. I noticed that if I add the UI test target in the app scheme without using test plans I can run the ui tests in parallel many times in a row, but if I convert to test plans or if I keep the UI tests in a separate scheme using test plans I can run the ui tests in parallel only once and then I get this error on the subsequent tries. The only way around it is to delete the simulator and recreate it.

I had a similar problem. The fix for me was making sure that the local branch was up to date with remote. It seemed that if I had unstaged changes to my schemes, xcode would skip the tests, or complain that the scheme could not be found. Best of luck!

UPD Everything works fine when we use -target option for xcododebuild command line arguments instead of -scheme, but could not use option due to project -target. The problem is in the scheme configuration or devices visibility for scheme, or both Also, it is working when I use generic destination: xcodebuild -project MyApp.xcodeproj -scheme 'MyApp WatchKit App' -destination generic/platform=watchOS build command I used: xcodebuild -workspace MyApp.xcworkspace -scheme 'MyApp WatchKit App' -destination 'platform=watchOS,id=Watch's ID' And I see this error: (null) needs to connect to determine its availability. Check the connection between the device and its companion iPhone, and the connection between the iPhone and Xcode. Both devices may also need to be restarted and unlocked.``` P.S. Restarting and unlocking doesn't help

UniversalLink and redirectURI are different things. OAuth standard protocol assumes that once the authentication part on the ASWebAuthenticationSession panel is completed successfully, the backend will redirect you to the URI indicated into the redirectURI parameter you used to instruct the request for the ASWebAuthenticationSession. If this doesn't happen for any reason (like a 302 on the redirectURI), then the ASWebAuthenticationSession isn't completed and your call back is never called.

If it's a critical need for your app and you have tight control over the content loaded, you can use a custom scheme with WKURLSchemeHandler to achieve the same effect. There's no way to do this for genera http(s) loads right now. Please file a request with Feedback Assistant with what you'd be using this for to help us prioritize.