“file uri scheme”

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!

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.

Xcode supports this really nicely but setting it up is a bit tricky. I took a run at this today and was quite happy with the results. Here’s what I did: On macOS 12.1, I started with a Hello directory that contains my source file and a make file: % find hello hello hello/hello.c hello/Makefile % cat hello/hello.c #include int main(int argc, char ** argv) { printf(Hello Cruel World!n); } % cat hello/Makefile hello: hello.c cc -o hello -g hello.c IMPORTANT The second line in hello/Makefile starts with a tab. I run Xcode 13.2.1 and chose File > New > Project and selected Other > External Build System. I named it XHello, just to keep things clear. I closed that project window. This left me with the following structure on disk: % find XHello XHello XHello/XHello.xcodeproj … lots of Xcode goo … I used the Finder to move XHello.xcodeproj to my hello directory. I opened that in Xcode. I chose Product > Build to check that it actually builds. I chose Product > Scheme

This was solved by changing Build/Override Architectures from Match Run Destination to Use Target Settings in the settings window displayed after executing the Product/Scheme/Edit Scheme... menu.

Would you mind sharing the outputs of the following commands? xcodebuild -project YourProject.xcodeproj -scheme YourScheme -showdestinations xcodebuild -project YourProject.xcodeproj -scheme YourScheme -showBuildSettings — Ed Ford,  DTS Engineer

This is not clear to me. You say that it is happening because the webview is trying to render the custom URL scheme?Why this is not happening if the application is used without the installer?I made a test calling the custom url scheme from safari and it says 'Safari can't open specified address' because it does not recognize the custom protocol. (In a mac with the working custom url scheme Safari is able to open the address)

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)

That's what I did (in fact direct aceess to scheme edit for the app by clicking on the left of the present scheme).But, in XCode 9.4, no such Launch application without state restoration option.

Hey, try this out: Go to Product Schemes New Scheme... Select the name of your Cocoapod then click OK. After you do this, build the project (click cmd + B) This worked for me.

This may seem like a silly question, but did you check you have the correct scheme selected? It's easy to forget to switch back to the app target's scheme before you do the archive, especially when the project is a complex combination of targets.

Well there is always smart app banners. They now want you to use the universal link for that but it has the App Store ID (as do some of the other meta schemes) but that doesn't give you any way to open the app. The smart app banner open/download logic is all controlled by Apple. The best the rest of us can do with an App Store ID is send someone to the download page.While I'm sure Apple wants to move away from the custom URL schemes. They are still acknowledging that the other schemes like Twitter cards and Applinks use custom URL schemes. I think the custom schemes are ok for the time being, especially if you support pre 9. I say that because even the new web markup validation tool acknowledges them:https://search.developer.apple.com/appsearch-validation-tool