Known Issues
This sections refers to issues potentially caused by a misconfiguration that is solvable. For limitations of the Access App, refer to the chapter Known Limitations.
Platform | Operating System | Manufacturer / Device | Issue | Possible Root Causes | Possible Solutions |
---|---|---|---|---|---|
iOS | All | All | App is not opening from the mobile browser via the Universal link (mobile-only feature). Instead, the browser navigates to the App Store page. | The AASA file (Apple-App-Site-Association file) does not exist. The content of the AASA file does not match with the used App ID. | See Solution for iOS App Link. |
iOS | All | iPhone X | App with version 1.8.0 crashes when you try to change the backend URL | The backend URL was changed to an invalid value. | Reinstall the app. Update to app release 1.9.x. |
Android | All | Samsung S7, Samsung S7 Edge | The authentication QR code is not correctly scanned. | - | Slowly move the camera away from the QR code. |
Android | All | Xiaomi | Biometric credentials registered in a non-work profile show up in the work profile as well but cannot be used for authentication. | The Xiaomi Android OS itself behaves incorrect in combination with work profiles, it does not separate credentials across profiles. When using a working profile the FIDO UAF credentials cannot be protected by the Operating System through user authentication. | Update to Android app release 2.4.x. |
Android | Android 11 and later | Xiaomi Nova 9 | No device passcode fallback screen is displayed when the user provides invalid biometric credentials too many times. | The Xiaomi biometric implementation incorrectly handles the case where the user provides invalid credentials too many times. | Bring the application to the background and then to the foreground. |
iOS | 15.5 | iPhone X | When trying to scan a QR code, the app responds with "Camera Access denied" asking the user to give access via the app system settings. The system settings does not show an option to enable camera access | Another application requested camera access before and something went wrong there. A screen sharing application was used, this is known to cause issues in regards to camera access | A reboot of the iPhone solves the issue. |
Android | All | Pixel | The push notifications are not received if the device is configured in Do Not Disturb mode. | - | Disable Do Not Disturb in the operating system settings. |
Solution for iOS App Link
The AASA file must be placed in the following location:
https://<domain>/.well-known/apple-app-site-association
The domain must be configured in the.entitlements
file of the App:App .entitlements file<key>com.apple.developer.associated-domains</key>
<array>
<string>applinks:domain</string>
</array>The AppID (created by concatenating the teamID and the bundleID) must be listed in the served-out AASA file:
AASA file
{
"applinks": {
"details": [
{
"appIDs": [
"<team id>.<bundle id>"
],
"components": [
{
"/": "<path>",
"?": {
"<parameter>": "*"
},
"caseSensitive": false
}
]
}
]
}
}
The following file is a minimalistic workable example:
Example AASA file
{
"applinks": {
"details": [
{
"appIDs": [
"U8KPBF668H.ch.nevis.accessapp"
],
"components": [
{
"/": "open",
"?": {
"dispatchTokenResponse": "*"
},
"caseSensitive": false
}
]
}
]
}
}
info
For more details of the Mobile-Only feature, see Mobile-Only Authentication / Deep Linking Best Practices.