Yuri Ufimtsev 55b7b0613d Allow the LockPatterUtils to be null ...

In some tests it could inconsistently become a null, crashing with NPE, for the reason I can't understand (maybe there is a race condition somewhere between mocking and accessing the LockPatterUtils in such tests)
Let's accept it gracefully

Test: atest SettingsUnitTests
Bug: 382637173
Flag: EXEMPT bugfix
Change-Id: I35d5faa1a29307fc780207a816680a32b2796bc0

2025-02-05 14:38:46 +00:00

..

anomaly-tester

…

componenttests

[Catalyst] Sync APM preference key value

2024-11-18 13:14:02 +08:00

Enable16KbTests

16KB: Fix failing tests for AOSP targets

2025-01-22 00:12:56 +00:00

legacy_unit

…

perftests

…

robotests

[Catalyst] Introduce SettingsContract file

2025-02-04 18:24:46 +08:00

screenshot

Merge "Removing Dead Flag Test: CI Bug: 386652866" into main am: ccf197b366 am: 9b18787489

2025-01-08 12:55:43 -08:00

shared

Spit up FingerprintManagerInteractor 2/N

2024-09-18 19:33:04 +00:00

spa_unit

Provide a way to customize biometric SafetySourceIssue

2025-02-02 18:46:25 -08:00

uitests

…

unit

Allow the LockPatterUtils to be null

2025-02-05 14:38:46 +00:00