“file uri scheme”

I'm running iOS 9b5.In my app, if a device can make a phone call, I want to color the text blue so it looks tappable. If not, I leave it black.In order to determine the device capabilities, I use:[[UIApplcation sharedApplication] canOpenURL:@telprompt://5555555555]As we all know, iOS 9 requires we whitelist any URL schemes we'll be using in our app as a privacy measure.I have this in my Info.plist:<key>LSApplicationQueriesSchemes</key> <array> <string>telprompt</string> </array>No matter what I do, I still get canOpenURL: failed for URL: telprompt:// - error: (null). I've tried tel:// and sms:// and I can't seem to avoid that syslog warning.Does anybody know of a way to detect whether or not a device can make a phone call wtihout triggering these warnings?

I have a requirement to launch an app from another app (there is no requirement to launch the app from a website), and if its not installed then for the user to be redirected to the app store to download the app. The app already has a custom url scheme implemented, however the documentation and tutorials in this area are confusing and unclear. In order to launch the app, the custom url scheme will provide that, however, in order to get the redirection to the app store then firstly does the custom url scheme have to be replaced with universal links? Secondly, is it necessary to have a webpage that links to the app store? Is it possible to get this behaviour without having a website? Is it the case that Apple doesn't provide this functionality and developers have to have the hassle of hosting a website purely just for the sake of redirecting to the App Store?

Hi, what is the process for providing justification for the apps outlined in our whitelist for canOpenURL. Will we need to provide this detail in iTunes Connect when we submit or elsewhere? Thanks.

Xcode's test scheme info, arguments, options and diagnostics tabs were once visible by pressing Command + Option + U, but they've been moved. Where do I find the corresponding sections, now? Here's the old UI (credit: https://betterprogramming.pub/easy-unit-testing-for-firebase-in-xcode-874842f79d84): Here is the new one:

My app has it's debug and release schemes. A client had a specific request which meant adding a couple of Swift packages that we only use with said client, and we proceed to install the app directly on their devices; however, on our repository we've been managing this request in its own branch, planning to eventually merge it to the development and master branches, and I am unsure of what to do regarding the client's package dependencies. Therefore, is there a way to manage which package dependencies to include when publishing to the App Store? Or is this an all or nothing situation?

Hello, I'm encounter crashes when integrating a company internal package through SPM only when I compile my app with the release scheme. My solution so far was to directly integrate sources into my project to solve theses crashes. For the context, the library use Metal and AVPlayer to manipulate AVPlayerItem and render video. Crashes frequently happened on those following lines: self.playerItem = AVPlayerItem(asset: asset) self.videoOutput = AVPlayerItemVideoOutput(outputSettings: [ kCVPixelBufferPixelFormatTypeKey as String: NSNumber(value:kCVPixelFormatType_32BGRA), kCVPixelBufferMetalCompatibilityKey as String: NSNumber(value: true)]) self.playerItem?.add(self.videoOutput!) The videoOutput variable is becoming nil resulting a crash. I have tried to disable compilation optimization of Apple Clang and Swift Compiler in the app and in the package (I don't know if compilation parameters of a package have any influence at all). I tried this because theses compilation parameters are different in release