file uri scheme

OK, these old proxy techniques use the HTTP CONNECT verb. The request line is supposed to be CONNECT myHost:myPort HTTP/1.1 (or 1.0). The thing is that myHost:myPort is not a URL. It is a URI, though. But you have to initiallize a URLRequest with a URL. (I tried with URLComponents and defining just the host and port, and I got //myHost:myPort. The extra slahses at the start make it useless here, unless you know some form of CONNECT-URI that allows slash prefixes.)Is there another type of proxy that lets you put full URLs on the CONNECT line? Or doesn't use CONNECT at all? I want to know what kind of proxy connections the authors at Apple (at least the ones at WWDC 2015) had in mind when designing the data-request-to-stream-task conversion delegate method.If I can't customize URLRequest the way I need, then I have to resort to the CFHTTPMessage API (or straight up manual work).

We have the same problem here, the new Service ID does not work: invalid_client The old one works like a charm (we did not delete it though) We also cannot use newly added redirect URIs to old Service IDs, invalid_redirect_uri Looks like something does not get updated correctly on the Apple side

Are you choosing a scheme or a device. These are very different things. In xCode there is a dual drop down, on the leftis the scheme, on the right, is the device. Click on the right drop down and select your connected iPad.

Found the solution. Go to ProductSchemesManage Schemes Select your scheme and click edit Select the options tab for the run section For 'GPU Frame Capture', select 'Metal' or 'disable'

Hey. You can go into the Scheme Editor of the test scheme under Options, and change App Region/Language to one you prefer, and that will be independent of your current device language. Hope this helps.

if (navigationType == UIWebViewNavigationTypeLinkClicked) { if ([[[request URL] scheme] isEqualToString: @file]) { NSArray<NSString*>* components = [request.URL.absoluteString componentsSeparatedByString:@#]; if (components.count == 2) { NSString* anchor = components.lastObject; NSString* code = [NSString stringWithFormat:@el = document.getElementsByName(%@)[0]; if (el) el.scrollIntoView();, anchor]; (void) [webView stringByEvaluatingJavaScriptFromString:code]; return NO; } } return YES; }

I solved the issue I had. Turns out I didn't set the StoreKit config in my scheme. Go to Edit Scheme -> Run and check if the config is set. If not, follow this guide: https://developer.apple.com/documentation/xcode/setting-up-storekit-testing-in-xcode/ It should look something like this if the scheme is set up correctly:

I think you only get this error when you're trying to preview, say, an iOS Home Screen widget but your active scheme is for something else, like a watchOS target. If you're previewing something in an iOS target, make sure to select the scheme that builds the iOS target. If you're trying to preview a watchOS target, select the watchOS scheme, etc.

UPDATE: I've viewed a WWDC22 video (What's new in StoreKit testing) which says to create a second storekit configuration file syncing it with the in-app purchase defined in Apple Store Connect. The new read-only file is indeed syncing; but, it is STILL NOT WORKING.A print statement to the console, says that, in sandbox mode, requestProducts() in the Store manager is unable to find any products (though it works as expected when the scheme is reading either of the local store kit config files).

Product is not on the list of schemes that's supported because we don't index anything directly from the Product itself other than AggregateRating and Offer. Of course, what we pull out of this markup is potentially changing over time, but at the moment we don't pull info from Product itself. If there's information you think we should be including from Product, please file bug reports with the details.

Yes this is a known issue. Currently previews are not supported inside of static libraries. As a workaround you could create a dynamic library or framework target in addition to the static library and put the file in both targets. Then, make sure your scheme is building the framework/dynamic library target even if it's not being included into any of your shipping apps, etc.

Solved: In my development debug Scheme, I had a leftover StoreKit Configuration in the Scheme Options. The fix was to set StoreKit Configuration to None. The latent StoreKit config was masking the App Store Connect products.