Closed Bug 1963733 Opened 2 months ago Closed 2 months ago

Add support for alternative unlock methods

Categories

(Firefox for Android :: Privacy, task)

All
Android
task

Tracking

()

RESOLVED INVALID
Tracking Status
firefox140 + disabled

People

(Reporter: mavduevskiy, Assigned: rebecatudor273)

References

(Blocks 1 open bug)

Details

(Keywords: topcrash, Whiteboard: [fxdroid][group2])

Crash Data

We should consider cases where biometric auth isn't being used

  1. the device doesn't have it physically
  2. the user has disabled it
  3. the user has chosen to use the PIN option on anrdoid biometric screen.

The behavior as of right now: biometric disabled and optional pin

Whiteboard: [fxdroid][group2]

Another case:

  1. User does not have any sort of pin or biometric authentication enabled on their device.
Assignee: nobody → rebecatudor273
Duplicate of this bug: 1964409

Adding the crash signature and tracking for Fx140 here since Bug 1964409 was duplicated.
:gela what's the timeline here for landing a fix? This is a top crash in nightly.

Crash Signature: [@ kotlin.UninitializedPropertyAccessException: at org.mozilla.fenix.tabstray.TabsTrayFragment$$ExternalSyntheticLambda7.invoke(R8$$SyntheticClass:77)]
Flags: needinfo?(gmalekpour)

We are moving this entire feature out of Nightly and in Debug only for now until we address some of the outstanding issues. I have reached out to Mike A. for an exact timeline.

Flags: needinfo?(gmalekpour) → needinfo?(mavduevskiy)

:dmeehan

We disabled the feature for the nightly users in this patch.

It turned out that the issue is caused by having the device locked specifically by a PIN – our biometric manager doesn't support that and crashes. The problem should also affect current release versions in different parts of the app (like a password manager), but not so many users a hitting those cases.

All that to say, in order to fix it properly we need to enrich the functionality of the biometric manager which is used across the app. For now, the crash shouldn't be a problem as the private mode feature will be disabled in nightly.

Flags: needinfo?(mavduevskiy)

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 AArch64 and ARM crashes on nightly

For more information, please visit BugBot documentation.

Keywords: topcrash

Setting Fx140 to disabled since, as mentioned in Comment 5, the feature was disabled in central under Bug 1964240.

All scenarios listed in this ticket are either already solved or will be solved as a part of other tickets, so marking this as invalid.

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → INVALID
No longer duplicate of this bug: 1964409
You need to log in before you can comment on or make changes to this bug.