User Profile

Hi,we are currently trying to test universal links also on our development server which is behind a VPN. From my understanding, correct if I am wrong, I thought it is enough that during app installation, the corresponding device (iPhone) is also connected via VPN so that iOS is able to download the AASA file?But at the moment I am not able to test this successfully. So my question is, is that possible in general to put the file on a server which is only reachable via VPN, and if yes, what could be the error?Best regardsChris

Hi. I have defined the following AASA File for my app: { "applinks": { "apps": [], "details": [ { "appID": "xxxxxx.com.company.app", "paths": [ "NOT /", "/path1/*", "/path2/*"], } ] } } The goal was to just allow path1 and path2 to be opened by the app - all other urls like password reset urls .. should be opened in browser. I have deleted the app from the phone and restarted the phone. Afterwards I have installed the current app. I have sent multiple types of urls via iMessage to the test device then. After first try, the url which does not include path1 or path2 opens in browser. Then I tried one which should be opened by the app - worked also. After that I retried the excluded url -> app is also opened! From that point on the app is always opened. So my question is why is the excluding logic only working on first try, and then the app is always opened?! What is the best way to achieve this? Is my definition maybe wrong? (Testdevice is running 14.6)

We are using the CoreNFC API for reading the NFC tag of the locking components of our customer. We have not implemented the scan functionality within our app, instead we are using only the iOS built-in mechanism. Normally the NFC notification is triggered and the user can open our app which then handles the provided data. BUT if the wallet app on the iPhone has a valid credit card enabled, most of the time (but more or less randomly) the wallet app is triggered instead of our app. I checked the callbacks and we are not called by the iOS NFC mechanism in that case. My first idea was to update the AASA file on the server because of the changes introduced with iOS13. My question is if there are other possible solutions for this issue. At the moment our NFC feature makes only sense for users which have not setup the wallet. :-/