Fatal Exception: com.google.crypto.tink.shaded.protobuf.InvalidProtocolBufferException

[StanleyCocos]

Before creating a new issue, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have tried disabling all browser extensions or using a different browser
• I have tried deleting the node_modules folder and reinstalling my dependencies
• I have read the guide for submitting bug reports.

On which framework/platform are you having an issue?

Android

Which UI component?

Authenticator

How is your app built?

Create React App

What browsers are you seeing the problem on?

Android (React Native)

Which region are you seeing the problem in?

No response

Please describe your bug.

Fatal Exception: com.google.crypto.tink.shaded.protobuf.InvalidProtocolBufferException
Protocol message contained an invalid tag (zero).

What's the expected behaviour?

tink-crypto/tink#504

Help us reproduce the bug!

tink-crypto/tink#504

Code Snippet

// Put your code below this line.

Console log output

No response

Additional information and screenshots

[reesscot]

@StanleyCocos Transferring to Android team repo for triage

[tylerjroach]

It appears that the underlying crash may have been fixed in AndroidX Security/Tink, but it is still in the alpha channel of AndroidX Security. We can pull the fix in once this hits a stable version.

Is this an edge case you are reporting or are you seeing this on a large number of devices?

[StanleyCocos]

What I understand is that this problem should be a known problem, and the problem has been officially fixed. Next, we only need to upgrade to the official repaired version.

[StanleyCocos]

tink-crypto/tink#504

[tylerjroach]

@StanleyCocos As soon as there is an official version that can be used, we will pull the release in. The AndroidX security library the referenced issue is currently only in the alpha channel: https://developer.android.com/jetpack/androidx/releases/security

In the meantime, we are additionally looking into gracefully catching and recovering from the exception. Once this error is seen, the encrypted shared preferences file is corrupted and unreadable. We are looking to better attempt recreating the secure preferences file in the rare cases that this does happen.

[mattcreaser]

This crash is closely related to issues like #2681. I have a workaround implementation in progress that should prevent this from crashing until such a time that we can upgrade to a newer androidx.security version.

In the meantime I'm going to transfer this to the main amplify-android repository, as this is not an issue with Authenticator itself.

[mattcreaser]

This has been released in Amplify 2.14.10 🎉

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.