tink-crypto / tink-crypto/tink-java
A lot of ANRs in Google Play Console
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 305
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug:
We started using EncryptedSharedPreferences and now receive a lot of ANR from Google Play Console. There is not much information, but some of ANRs points to com.google.crypto.tink library.
What was the expected behavior?
No ANRs
How can we reproduce the bug?
Unfortunately, we have no reproduce, only data from Google Play Console.
Do you have any debugging information?
Console points to that lines of code (they are all different, it is not single stacktrace):
com.google.crypto.tink.shaded.protobuf.MessageSchema.newSchemaForRawMessageInfo+3804
com.google.crypto.tink.daead.AesSivProtoSerialization.parseKey
com.google.crypto.tink.internal.MutablePrimitiveRegistry.registerPrimitiveWrapper
com.google.crypto.tink.proto.AesSivKeyFormat.dynamicMethod
javax.crypto.Cipher.init+66
com.google.crypto.tink.shaded.protobuf.ProtobufArrayList.mutableCopyWithCapacity
com.google.crypto.tink.KeyManagerRegistry$2.getUntypedKeyManager
com.google.crypto.tink.shaded.protobuf.MessageSchema.mergeFromHelper+8504
What version of Tink are you using?
1.8.0 inside AndroidX.Security.Crypto-1.1.0-alpha06
Can you tell us more about your development environment?
Xamarin.Android
Android 24+
There is no statistically significant differences in ANR per devices or Android version.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Google Play Console ANR traces and compare them with Tink 1.8.0 as bundled by AndroidX.Security.Crypto 1.1.0-alpha06 in the stated Xamarin.Android and Android 24+ environment. Done means identifying a reproducible cause or narrowing the reports to an actionable Tink or integration issue; the report provides no named source files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- cryptography, mobile-dev, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100