Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

liveness crash due to Caused by android.security.KeyStoreException: Invalid key blob (so far happens on two samsung devices according to firebase crashlytics) #206

Open
2 tasks done
hereisderek opened this issue Dec 18, 2024 · 1 comment
Labels
feature-request New feature or request liveness This issue relates to the Liveness component

Comments

@hereisderek
Copy link

Before creating a new issue, please confirm:

Which UI component?

Liveness

Gradle script dependencies

// Put output below this line
liveness 1.3.0

Environment information

# Put output below this line

------------------------------------------------------------
Gradle 8.10.2
------------------------------------------------------------

Build time:    2024-09-23 21:28:39 UTC
Revision:      415adb9e06a516c44b391edff552fd42139443f7

Kotlin:        1.9.24
Groovy:        3.0.22
Ant:           Apache Ant(TM) version 1.10.14 compiled on August 16 2023
Launcher JVM:  23.0.1 (Homebrew 23.0.1)
Daemon JVM:    /opt/homebrew/Cellar/openjdk/23.0.1/libexec/openjdk.jdk/Contents/Home (no JDK specified, using current Java home)
OS:            Mac OS X 15.2 aarch64

Please include any relevant guides or documentation you're referencing

received crashlytics report This issue has 102 crash events affecting 2 users

Describe the bug

crashlytics reports that this issue so far happened on only two Samsung devices, the app doesn't have much user base so it could happen to other devices as well. i have not personally experienced this crash but I don't have a Samsung to test on

62% Galaxy A90 5G
38% Galaxy S22 Ultra

full crash report has been attached

co.hud.app_issue_98cd5b27c6c47f551c310e6dbb1d94ce_crash_session_676328E402A900010EFF66B17129E032_DNE_0_v2_stacktrace.txt

Reproduction steps (if applicable)

No response

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line


amplifyconfiguration.json

{
"auth": {
"plugins": {
"awsCognitoAuthPlugin": {
"CredentialsProvider": {
"CognitoIdentity": {
"Default": {
"PoolId": "us-east-1:***",
"Region": "us-east-1"
}
}
}
}
}
}
}

Additional information and screenshots

No response

@github-actions github-actions bot added pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Dec 18, 2024
@vincetran
Copy link
Member

Hi @hereisderek and thanks for the report. This is an issue coming from the underlying Amplify library that Liveness depends on. We're tracking this issue in the main Amplify repo and can be found here: aws-amplify/amplify-android#2845

@github-actions github-actions bot removed the pending-maintainer-response Issue is pending response from an Amplify team member label Dec 18, 2024
@vincetran vincetran added liveness This issue relates to the Liveness component feature-request New feature or request labels Dec 18, 2024
@github-actions github-actions bot removed the pending-triage Issue is pending triage label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request liveness This issue relates to the Liveness component
Projects
None yet
Development

No branches or pull requests

2 participants