“file uri scheme”

The change to include the email address in the ID token is currently being worked on and will be available soon. Currently the email address is provided to the application front-end through the post to the redirect uri.

Right. And that leads you to the last paragraph of Supported URL Schemes. That is, if there’s no documented way to achieve this goal, you should file an enhancement request for such a mechanism. That’s kinda the whole point of my Supported URL Schemes post. You can’t just cons up your own URL that happens to work, because if it’s not documented then it’s an implementation detail that you can’t rely on. If you do file an ER, please post the bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Objective-C. The target membership seems fine ... how do I check whether there's something wrong with the scheme or not? It indexes most of the files just fine ... just a few (important ones) that are off

Feel free to file a bug against the process via the link, below right, adding your report # to your thread for reference.Otherwise I'm unaware of any petitioning scheme you might leverage.Good luck.

This is likely due to the match patterns for file and ftp. Safari does not support extensions for those schemes, so the matches array will appear empty after those unsupported patterns are filtered out.

I have a similar problem starting 6/18/2023. Expected identifier or '(' in a perfectly valid .h file also the analyzer thinks the header is not in the project's scheme. Did you ever fix this?

This is indeed undesirable behavior. I'm not sure whether Apple is aware but you should file a feedback for it. In the meantime, there's a workaround you can propose to your third party libraries' maintainers to adopt, and it consists on using an xcworkspace as the scheme container as opposed to .swiftpm. Example: https://github.com/sideeffect-io/AsyncExtensions/pull/29. As I said, unfortunately this is up to the maintainers to adopt, not you, as Xcode reads the checked in .swiftpm folder from your dependencies and grabs the schemes from there without you having a say in it. Again, probably undersirable behavior and an oversight from the Xcode team, so worth filing a radar.

Make sure that you are distributing your app using the release scheme instead of the debug scheme. To configure your app to be built using the Release scheme, go to Product → Scheme → Edit Scheme. Then set the Build Configuration dropdown to Release.

I’m not sure if anything else is going on here but your isInTrash(…) function has a serious bug. Specifically, this code is incorrect: guard let fileURL = URL(string: file) else { You should be using init(fileURLWithPath:). What you’re constructing here is as scheme-less URL that just contains a path. While you want is a URL with the file scheme. Consider: import Foundation let u1 = URL(fileURLWithPath: /Users/quinn/Test) let u2 = URL(string: /Users/quinn/Test)! print(u1) // file:///Users/quinn/Test/ print(u2) // /Users/quinn/Test Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi, I have also observed the same error Unsupported audio track codec: Unknown for the below unencrypted playlist when i run with media stream validator (version - v1.20.7). Unsupported audio track codec: Unknown Rendition #5 Below is the playlist; #EXTM3U #EXT-X-VERSION:5 #EXT-X-INDEPENDENT-SEGMENTS #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID=audio-ac3,LANGUAGE=en,NAME=English,AUTOSELECT=YES,CHANNELS=6,URI=var7031966/aud135/playlist.m3u8?device_profile=hls #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID=audio-aac,LANGUAGE=mul,NAME=Multiple,AUTOSELECT=YES,CHANNELS=2,URI=var7031966/aud138/playlist.m3u8?device_profile=hls #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID=audio-aac,LANGUAGE=ang,NAME=Old English,AUTOSELECT=YES,CHANNELS=2,URI=var7031966/aud139/playlist.m3u8?device_profile=hls #EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID=subs,LANGUAGE=en,NAME=English,AUTOSELECT=YES,URI=subs/eng_2/playlist.m3u8?device_profile=hl s #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=6700000,CODECS=ac-3,avc1.64002a,RESOLUTION=1920x1080,AUDIO=a

If your app is linked on or after iOS 9.0, you must declare the URL schemes you pass to this method by adding the LSApplicationQueriesSchemes key to your app's Info.plist file. This method always returns false for undeclared schemes, whether or not an appropriate app is installed. Apps linked on or after iOS 15 are limited to a maximum of 50 entries in the LSApplicationQueriesSchemes key. https://developer.apple.com/documentation/uikit/uiapplication/1622952-canopenurl

Posted in July, and filed Feedback about it with Apple. After some back and forth they said **Thank you so much for providing the built products! We’ve identified that object files for this project are built as universal. There’s a known issue with the new Previews execution mode that projects built in debug mode as universal can run into this exact error. We’re working on a fix. But in the meantime can you check your scheme build settings? Open up the scheme editor by choosing the “Product > Scheme > Edit Scheme” menu item. Click on the “Build” sidebar tap in the modal window. You should see a control in the middle labeled Override Architectures. We’re pretty sure you have yours set to Universal. If you set that to “Match Run Destination” then your debug build products will just focus on building the architecture that you’re targeting to build-and-run. That should be sufficient! Please let us know if now. Note that this only affects local developmen