Fixed
Status Update
Comments
la...@google.com <la...@google.com> #2
Since this is happening in Tink, rather than in the AndroidX library, it would be best to open an
la...@google.com <la...@google.com> #3
ap...@google.com <ap...@google.com> #4
Tink is the library that does the heavy lifting in Jetpack Security.
And yes, potentially raising that issue with the Tink team directly could help.
cc...@google.com <cc...@google.com> #5
@4 Well why didn't Google offer it there? Crashes are far more important than warning logs...
Here, created it there too:
https://github.com/google/tink/issues/535
Here, created it there too:
Description
See sample trace:https://ui.perfetto.dev/#!/?s=c733d216b22e916988fd8a9e3511dc4f383161fca4d6eb1d225bf386e747b
Has several errors, Lalit said it's likely a configuration error, and recommended using compact sched on Q+.