You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(android-unhandled: androidx.credentials.TYPE_CREATE_PUBLIC_KEY_CREDENTIAL_DOM_EXCEPTION/androidx.credentials.TYPE_SECURITY_ERROR, The incoming request cannot be validated, The incoming request cannot be validated, null)
#82
Running the example app seems to work fine but when I generate my own key for signing in apps or resuing the same key in a different app it shows the same error (PlatformException(android-unhandled: androidx.credentials.TYPE_CREATE_PUBLIC_KEY_CREDENTIAL_DOM_EXCEPTION/androidx.credentials.TYPE_SECURITY_ERROR, The incoming request cannot be validated). Tried various other things and saw that only the given example.keystore works for me. Any other signin using keytool isn't begin valid. The command used to generate my own keys: keytool -genkey -v -keystore ./android/example2.keystore -keyalg RSA -keysize 2048 -validity 10000 -alias example
I am not sure if this is the issue but according to trying different things the app only throws the exception here. So, I assumed maybe the package only handles it's own key file (or) the documentation should be updated to show how to signin keys properly.
My flutter version and the build tools versions:
❮ flutter doctor --verbose
[✓] Flutter (Channel , 3.24.3, on Arch Linux 6.11.3-arch1-1, locale en_US.UTF-8)
• Flutter version 3.24.3 on channel at /usr/lib/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision archlinuxaur (unknown (arch linux aur package)), 2038-01-19 03:14:08
• Engine revision 36335019a8ea
• Dart version 3.5.3
• DevTools version 2.37.3
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /home/sarath/Android/Sdk
• Platform android-34, build-tools 34.0.0
• Java binary at: /usr/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.13+11)
• All Android licenses accepted.
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
• clang version 18.1.8
• cmake version 3.30.5
• ninja version 1.12.1
• pkg-config version 2.1.1
[✓] Android Studio (version 2024.2)
• Android Studio at /opt/android-studio
• Flutter plugin version 82.1.3
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 21.0.3+-12282718-b509.11)
[✓] Connected device (2 available)
• RMX2081 (mobile) • 192.168.29.223:38221 • android-arm64 • Android 11 (API 30)
• Linux (desktop) • linux • linux-x64 • Arch Linux 6.11.3-arch1-1
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 1 category.
The text was updated successfully, but these errors were encountered:
Running the example app seems to work fine but when I generate my own key for signing in apps or resuing the same key in a different app it shows the same error (
PlatformException(android-unhandled: androidx.credentials.TYPE_CREATE_PUBLIC_KEY_CREDENTIAL_DOM_EXCEPTION/androidx.credentials.TYPE_SECURITY_ERROR, The incoming request cannot be validated
). Tried various other things and saw that only the given example.keystore works for me. Any other signin using keytool isn't begin valid. The command used to generate my own keys:keytool -genkey -v -keystore ./android/example2.keystore -keyalg RSA -keysize 2048 -validity 10000 -alias example
This works but this doesn't
I am not sure if this is the issue but according to trying different things the app only throws the exception here. So, I assumed maybe the package only handles it's own key file (or) the documentation should be updated to show how to signin keys properly.
My flutter version and the build tools versions:
The text was updated successfully, but these errors were encountered: