“file uri scheme”

You can either click the scheme popup button to edit a particular scheme, or press Command+Option+R to edit the current scheme and then run.The settings you're looking for are GPU Frame Capture and Metal API Validation. Set both to Disabled to avoid this runtime overhead.

Environment Variable? I know in SwiftUI you can: struct SmileyFaceView: View { @Environment(.colorScheme) var scheme var body: some View { Image(systemName: face.smiling) .foregroundColor(scheme == .light ? .black : .white) // this is to change to color according to the scheme .environment(.colorScheme, .light) // This is to force the icon to the face.smily } } for your need not sure in UIKit

I fixed the issue by deleting and re-adding the test scheme for one of my internal frameworks in the Schemes management screen. This resolved the problem with xcodebuild.

Hey guys. There is temporary (I hope) solution to this issue: Scheme -> Edit Scheme Select Wait for executable to be launched Launch an app manually

How are you sure textDidBeginEditing is not called at all ?console log didn't print for me.Now I am not able to recreate the issue in the release scheme. Now it's working as expected.Not sure how it got fixed. maybe switching between schemes?Have you ever faced similar issues in the past due to any scheme/target issues?

Check the release notes - I'd wonder if has to do w/the new vend schemes... Create a fresh sample using an applicable template and see if those calls persist. Feel free to file bugs against the beta, being sure to add your report #(s) to your thread for ref., thanks and good luck.

The subscription success popup now always shows the environment as “xcode. When you enable StoreKit Testing in Xcode, all your purchases occur in the local environment. When you disable StoreKit Testing in Xcode , purchases occur in the sandbox environment. To test in the sandbox, remove the StoreKit configuration file from your scheme's run options.

Thanks, the solution with the '-scheme' worked for me but it is odd that the same result can't be achieved with the '-target' parameter. There is only one scheme for a target so what could even go wrong here?

@madsolar8582 xcodebuild clean archive -workspace MyApp.xcworkspace -scheme MyApp -configuration Release -archivePath results/artifacts/App.xcarchive -destination generic/platform=iOS -derivedDataPath build -allowProvisioningUpdates -authenticationKeyID **** -authenticationKeyIssuerID **** -authenticationKeyPath /Users/MyUser/MyKey.p8 Running xcodebuild with the authentication API keys only supports exporting archives. This workflow doesn't support building and archiving. To upload your binary, first archive your binary, create a plist file that configures archive exporting, gather your Enterprise Authentication API keys from the portal, then run the following command in Terminal: xcodebuild -exportArchive -archivePath -exportPath -exportOptionsPlist -allowProvisioningUpdates -authenticationKeyPath -authenticationKeyID -authenticationKeyIssuerID The -exportArchive option specifies that xcodebuild should distribute the archive specified by -archivePath using the options specified by -ex

I believe I know the root of this issue. In my case, the webview has its base URL set as a valid location, with a scheme of https. WKWebView sees custom schemes as insecure. WKWebView also does not allow pages loaded with a secure scheme to fetch from domains which are not secure. If I set the base url of my page to nil or an http URL, fetch loads from the custom scheme handler as expected. I haven't yet found any way to change the policy to allow the insecure fetch to proceed.

If you want to hide these errors do this: 1 - From Xcode menu open: Product > Scheme > Edit Scheme 2 - On your Environment Variables set OS_ACTIVITY_MODE = disable

Links between apps are fine and and can be achieved by using a custom URL scheme. Apple have some great document on this to get you started.Using URL Schemes to Communicate with Apps- Tom

You can also do this in the scheme. In your app's scheme, enable Malloc Stack logging for Live Allocations. This is under Diagnostics. Make sure to enable this in the approprate operation, Run or Test.

this sounds like the user of a custom URL scheme. https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app or do you have something else in mind?

This worked for me You should be able to work around it by turning off Metal Validation in Scheme -> Edit Scheme -> Run -> Diagnostics -> Metal API Validation