Yes, this is a common bug with passkeys—it’s not an issue with your phone.
There are two ways to create a passkey:
Directly on your phone—which often fails on xeggex.com.
In this scenario, your phone acts as both the browser and the secure vault. Many sites, like Xeggex, use an outdated WebAuthn implementation. They request the creation of a passkey incorrectly, and Android or iOS blocks it for security reasons. As a result, the process might just spin, throw an error, or fail to offer the option to save the passkey at all.Via PC + QR code—which works.
This is known as the "hybrid" or "cross-device" method:
The PC acts as the browser.
Your phone acts solely as the secure vault.
When you scan the QR code, your PC and phone communicate via Bluetooth to verify that they are close to each other; then, your phone securely creates the passkey within Google Password Manager or iCloud.
Why does this work better? Because it is much simpler for the website to process. Instead of asking the phone to handle everything on its own, the site simply says, "Okay, send me a key from another device."
In short:
Direct method = your phone has to act as both client and server simultaneously, which some sites block.
QR code method = the PC acts as the client and the phone as the server—a setup that works reliably.
My recommendation: stick with this approach. Always create your passkeys from a PC (or another browser) by selecting the option "Use another device / iPhone / Android phone" and scanning the QR code. Once created, the passkey will be available on your phone, allowing you to log in to Xeggex directly from your phone without needing a PC.