Skip to main content
Version: 2.5.x.x RR

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.

PlatformOperating SystemManufacturer / DeviceIssuePossible Root CausesPossible Solutions
iOSAllAllApp 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.
iOSAlliPhone XApp with version 1.8.0 crashes when you try to change the backend URLThe backend URL was changed to an invalid value.Reinstall the app. Update to app release 1.9.x.
AndroidAllSamsung S7, Samsung S7 EdgeThe authentication QR code is not correctly scanned.-Slowly move the camera away from the QR code.
AndroidAllXiaomiBiometric 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.
AndroidAndroid 11 and laterXiaomi Nova 9No 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.
iOS15.5iPhone XWhen 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 accessAnother 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 accessA reboot of the iPhone solves the issue.
  • 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":[
    {
    "paths":<path>,
    "appID": "<teamID>.<bundleID>"
    }
    ],
    "apps": []
    }
    }

    The following file is a minimalistic workable example:

    Example AASA file
    {
    "applinks": {
    "details": [
    {
    "paths": [
    "/open"
    ],
    "appID": "ABCDEFGHIJ.ch.nevis.accessapp"
    }
    ],
    "apps": []
    }
    }
info

For more details of the Mobile-Only feature, see Mobile-Only Authentication / Deep Linking Best Practices.

Nevis recommends using the simpler custom URIs.