This guide provides detailed information about inherent limitations of the Nevis Access App, unrelated to configuration issues. Understanding these constraints will help users navigate potential challenges and optimize their authentication experience.
Universal Limitations: App Link Restrictions
App links initiated from the following scenarios will fail to redirect properly to Access App:
-
Private/incognito browser sessions on Android
-
Chrome browser on iOS devices
Recommended Solution:
Avoid using app links in these scenarios or switch to alternative browsers.
Android-Specific Challenges
Android platforms present several unique constraints, primarily concerning biometric authentication, OS compatibility, and device-specific issues.
1. Biometric Authentication: Sensor Compatibility
The Android biometric verifier only supports Class 2 and Class 3 biometric sensors. For optimal security, Class 3 sensors are strongly recommended.
Currently, facial recognition with Class 3 support is limited to specific Google Pixel models running Android 10+. Iris recognition with Class 3 support is only available on select Samsung Galaxy devices running Android 10.
Security Note:
While Class 2 sensors can enable facial recognition on additional devices, this configuration presents security tradeoffs.
2. Operating System Compatibility Issues
|
OS
|
Manufacturer/Device
|
Issue
|
Solution
|
|
GrapheneOS, LineageOS
|
All
|
App displays root detection error
|
No current solution; future support possible
|
|
Android 10
|
Nokia
|
Intermittent push notification failures
|
Use QR codes or disable battery optimization
|
|
Android 9 and earlier
|
Huawei/others
|
Push notification delivery issues
|
Disable battery optimization in OS settings
|
|
All
|
Budget devices
|
App fails to launch
|
Requires device with proper encryption hardware
|
3. Workaround for GrapheneOS Users
GrapheneOS users may attempt the following configuration change, though this reduces overall device security:
-
Navigate to Security and Privacy settings
-
Select Exploit Protection
-
Disable Secure App Generation
-
Reboot device
iOS-Specific Considerations
Apple devices present their own set of unique behaviors that users should understand.
1. Device Passcode Requirements
The Access App requires an active device passcode to function. Disabling the passcode through iOS settings will invalidate existing app registrations.
Note:
Modifying fingerprint configurations or changing the passcode won't affect registrations, but fingerprint authentication requires OS-level fingerprint enrollment.
2. Multiple Push Notification Handling
When network conditions cause delayed notification delivery, simultaneous arrival of multiple push notifications may cause the app to hang on the loading screen.
Resolution:
Restart the application and reinitiate the operation.
3. Screen Mirroring Interference
Active screen mirroring applications may prevent push notifications from reaching the device.
Alternative:
Disable mirroring applications or use QR code authentication instead.
4. iOS 15 Automatic Cleanup Bug
Versions 15.0 through 15.x cannot detect fresh installations due to an Apple system bug, potentially causing random account losses. This was resolved in iOS 16.
Manual Solution:
Use the "Reset Nevis Access" button in app settings when needed.
Your message must be between 20-3,000 characters!
