“file uri scheme”

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

>impersonationI think/hope you meant synchronization...Once you've connected to the other macs via sharing, I'd use applescript to read files/permissions and sync folders accordingly. See the docs on both.Just keep in mind that Apple already provides user-facing schemes for this, so you may be attempting a new wheel.

so we should not use it?The general rule for Apple URL schemes is that, if it’s not documented, you shouldn’t use it. Lots of folks have discovered the hard way that relying on undocumented URL schemes usually ends in binary compatibility tears down the line.is there any correct and proper way how to jump to watch app?I’m not aware of such an option, although it seems like a reasonable enhancement request based on the existence of UIApplicationOpenSettingsURLString. If you do file an ER, please post your bug number, just for the record.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I am also curious about this! However, I think in this example, the File/Folder Scheme is explicitly about URL-based filesystem items. Now, your notes could be stored as files, and the folders could be literal folders. You could use two different Entities, each conforming to the appropriate Schemas and then allow them to be interchangeable with one another by implementing transferable on them. (I think!) I've gotten things like that to work for in-app-actions, but not yet for cross-app actions.

While that scheme works for 'arkit', I don't yet see a more restrictive key for arkit 3.0https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW3You may want to file an enhancement request for such a key via the bug reporter.Good luck

Hello all,As a workaround, I recommend that you try running your app with Metal API validation disabled (Click your build target -> Edit Scheme -> Options -> Metal API Validation -> Disabled).Additionally, please file a bug report for this issue using our feedback assistant tool at: https://developer.apple.com/bug-reporting/

>All the hardware people are still required to set itDon't conflate specific MFi licensing requirements and vendor firmware update schemes with general developer needs.As always, devs are encouraged to file bugs to help make themselves heard - be sure to add your report #(s) here for reference, thanks and good luck.

By default, the profile action uses a release configuration, while the run action uses debug. If you change your scheme so the run action uses a release configuration (from the Product menu, select Scheme, then Edit Scheme), does it match the performance you see while profiling?Note that using the release configuration can make debugging more difficult, so you normally want it on debug while you're working on your app.

As an additional background, I use a m3u8 file, which contains the following metadata. #EXT-X-VERSION:5 #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID=audio,NAME=Original Audio,LANGUAGE=qag,AUTOSELECT=YES,URI=audio-13-64000/prog_index.m3u8?start=2023-03-01T10%3A29%3A04%2B0000&end=2023-03-01T11%3A09%3A18%2B0000&sourcetimestamps=1&returnType=hls,DEFAULT=YES #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID=audio,NAME=Original Audio 1,LANGUAGE=qaf,AUTOSELECT=YES,URI=audio-12-64000/prog_index.m3u8?start=2023-03-01T10%3A29%3A04%2B0000&end=2023-03-01T11%3A09%3A18%2B0000&sourcetimestamps=1&returnType=hls #EXT-X-STREAM-INF:BANDWIDTH=388328,RESOLUTION=426x240,CODECS=avc1.4dc01f,mp4a.40.2,AUDIO=audio 300/prog_index.m3u8?start=2023-03-01T10%3A29%3A04%2B0000&end=2023-03-01T11%3A09%3A18%2B0000&sourcetimestamps=1&returnType=hls #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=388328,RESOLUTION=426x240,CODECS=avc1.4dc01f,URI=300/prog_index.m3u8?start=2023-03-01T10%3A29%3A04%2B0000&end=2023-03

I found the same issue when testing with SwiftUI tutorial - creating a watchos/macos app. I can't get away with the error The run destination iPhone 12 Pro Max is not valid for Running the scheme 'WatchLandmarks'. anyway even when only WatchKitExtension is selected as the target. It only happens to the watchos scheme, but not the macos scheme. This seems to be a defect of XCode Previews.

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:

Is there a URL scheme that I can use to directly open that panel? No. I have general advice on this topic in this post. Many settings show up both some centralised area within Settings and in the app-specific settings, and you could file an enhancement request for Apple to do that with Sign in with Apple. Alternatively, file an ER for a way to open its entry in the the centralised area. If you do file any bugs about this, post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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).

I have worked around this issue by disabling GPU Frame Capture in the application's Scheme. Find that setting under Edit Scheme > Run > Options > GPU Frame Capture. Set it to Disabled.

I get the same error, but only when BuddyBuild tries to compile it. As far as I know, BuddyBuild uses the same schemes that I've checked into the project, and my schemes are not trying to build for Catalyst.