“file uri scheme”

I have created a landing page in my webapp that will attempt to redirect to my native app's URL scheme if the app is installed and if it is not, I have a timeout set to redirect to the normal webapp URL as discussed here.My code looks like this:$(document).ready(function() { window.location.href = urlScheme://; setTimeout(function() { window.location.href = http://foo.bar/webappurl }, 500); })The app redirects to 'http://foo.bar/webappurl' no matter what, even when the app is installed. I can see the do you want to open this in your app? dialog for a split second before it redirects, but it always redirects no matter what.Can anyone tell me what I'm doing wrong here or recommed a better way to check to see if the app is installed and then redirect there using Javascript?

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?

I have taken over managing an older enterprise app that is deployed to target iOS 5.0. We are having random problems with the app after recompiling changes to the content data. The problems seem to only effect 64bit iPads. There are random failures to overwrite existing data. The most obvious being changes to the URL Scheme in xCode is not being reflected in the app. The result is that when the new enterprise app version is deployed some of the new info doesn't seem to be getting replaced for all iPads all the time. Hence calls to a given URL scheme are failing to open that app on some pads and not others.There are other details that I have sussed out but those are the big points. Any comments would be most welcome.

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?

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