When will FusionAuth support android:apk-key-hash: origins for passkey sign-in?
-
We're implementing passkey sign-in for a mobile application and are currently blocked from production release on Android due to GitHub issue #3576. FusionAuth is rejecting
android:apk-key-hash:origins during WebAuthn registration/authentication flows.Native Android passkeys use standard WebAuthn with the
android:apk-key-hash:origin format, and implementing a workaround (such as a browser-based or hosted-page flow) would introduce unnecessary complexity, security trade-offs, and throwaway code.Is there a timeline for when this will be fixed?
-
This issue has been fixed and released. The bug preventing FusionAuth from accepting
android:apk-key-hash:origins for Android passkey authentication was addressed in a recent release.The fix went through the standard development and review process:
- Bug categorized and prioritized
- Fix implemented by the development team
- Code review completed
- Released in a subsequent version
You can verify the fix is working in your environment by testing passkey registration and authentication flows on Android devices. The
android:apk-key-hash:origin format should now be properly recognized during WebAuthn operations.For similar issues in the future, you can track progress on FusionAuth's GitHub issues page and monitor release notes for bug fix announcements.
-
D dan has marked this topic as solved