diff options
| author | 2023-10-30 15:28:42 +0000 | |
|---|---|---|
| committer | 2023-10-30 14:01:50 -0700 | |
| commit | 9a22714fddb4473bb49fedf1a0072b9e5584bdff (patch) | |
| tree | c4050f1d118a83bc57f06854a815588e99756fc3 /api/api_test.go | |
| parent | b654506f44827dbfc0283b91862b928ad61bc2f8 (diff) | |
[SettingsProvider] fix SettingsProvider on work profile restart
A recent CL ag/25164661 changed SettingsProvider from lazily initializing to promptly initializing all the tables on-user-added. The old implementation of SettingsProvider used to promply clear all the settings tables when a user is stopped. This no longer works if we initialize the tables when the user is created, resulting in NullPointerExceptions. In this CL, we no longer clear the settings tables when a user is stopped. Instead, we only clear the tables when the user is removed.
Change-Id: I6d64f7256e99e3519158e62768519107a423723e
BUG: 307323531
Test: manual; stop and start work profile and observe no crashes
Diffstat (limited to 'api/api_test.go')
0 files changed, 0 insertions, 0 deletions