diff options
| author | 2024-04-30 13:57:43 -0700 | |
|---|---|---|
| committer | 2024-05-10 15:06:19 -0700 | |
| commit | 76ea19d902613f4b997e1e2628877c9fafff977d (patch) | |
| tree | ecfe0a0a54a619a03e7d17607a5f51bc93aa92b5 /libs/androidfw/StringPool.cpp | |
| parent | 812805e8e193d6ad01c7b1996b0da0025f75a3b3 (diff) | |
More logging for views filling
Add more log for views filling
1. Add confirmed success. Confirmation is done via call by fetching
autofillValue, or if app calls notifyValueChanged.
If views aren't included in the success, it doesn't neccessarily
mean that the autfilling failed. It could very well be that the app
has implemented autofill functionality improperly.
2. If for some reason, the autofill callback is for an autofill id that
wasn't being tracked, we log count of such cases. We expect it to be
0. This is only to catch such occurences, and investigate them, and
fix tem later.
Bug: 332943845
Test: atest CtsAutoFillServiceTestCases
Change-Id: I69b9dcd7749b0b9d4ac7ea6cca910e8d0a8cd2da
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions