AnomalyReport catch any exception when try to read deviceConfig
If the app context, likely tests that didn't mock permission, doesn't have deviceConfig read permission, don't try to enforce server-side flag . Fix: 247700179 Test: manual trigger + https://android-build.googleplex.com/builds/abtd/run/L02900000956490923 Change-Id: I8f0e84219057974649def4bcc312ae0dc38670d1
Loading
Please register or sign in to comment