Saoiray
November 12, 2024, 6:55am
5
@PappaDanceA big thing is it’s been asked and answered a few times. Sadly people don’t look for existing posts and instead just come to create their own.
opened 02:03PM - 18 Feb 24 UTC
closed 05:57PM - 06 Dec 24 UTC
feature/sync
feature/password-manager
QA/Yes
release-notes/include
OS/Android
QA Pass - Android ARM
QA Pass - Android Tab
QA/Test-All-Platforms
OS/ChromeOS
## Description
It states I need to enable biometrics features/PIN first. The… device doesn't have any biometrics features, however it does use encryption and I'm already using a PIN to unlock the device
## Steps to reproduce
1. Install any Brave version on Chromebook/Android (including Nightly, Beta)
2. Open Sync Preferences
3. Try to enable Password sync
## Actual result
See error message
## Expected result
Just work
## Issue reproduces how often
Everytime
## Version/Channel Information:
- Can you reproduce this issue with the current Play Store version? Yes
- Can you reproduce this issue with the current Play Store Beta version? Yes
- Can you reproduce this issue with the current Play Store Nightly version? Yes
## Device details
- Install type (ARM, x86): ARM
- Device type (Phone, Tablet, Phablet): Phone (Pixel 8 - Android 15), Chromebook Lenovo Duet Tablet
- Android version: Android 15 (beta), ChromeOS (stable, beta & dev)
## Brave version
Stable, Beta & Nightly
### Website problems only
- Does the issue resolve itself when disabling Brave Shields?
- Does the issue resolve itself when disabling Brave Rewards?
- Is the issue reproducible on the latest version of Chrome?
### Additional information
And then of course…
@BoundlessDomain issue is only with your Android, right? If so, it’s a known issue and being worked on. GitHub link you can use to track the issue is below:
Thanks for confirming that. I see there is an open Github for this, which I’ll link below. But let me also tag in @Mattches and possibly @Serg to see if they might be able to get eyes on it or perhaps share what might be happening.
I had the same issue. It was resolved by using PIN input instead of fingerprint recognition.
