Stop being the product.
Become the owner.
or
sign uplog in
yearworker
@yearworker
badge
519
posts
15
comments
38
reactions
102
subscribers
8
subscriptions
32,597
views
badge
badge
badge
> **Couldn't use a passkey here: this device's passkeys can't derive a wallet key (no PRF support)**

This isn't a Coinos bug; it's your browser/passkey manager.

**Reminder:**

Coinos v3 doesn't use the passkey just to verify your identity. It uses the **PRF** extension. The passkey must be able to extract a 32-byte secret to derive the wallet key.

If your manager doesn't support PRF, Coinos will reject it. This is exactly your situation.

In your screenshot, we can see that you're using **Brave Android**. Brave Android doesn't use the Android Credential Manager for PRF, so it fails. Known bug: "Right now only Chrome is supported for Android" for PRF.

**Quick Fix:**

1. **Open ` v3.coinos.io ` in Chrome** (not Brave), Android 14+ (updated)
2. In Chrome, go to `Settings > Google Password Manager` > enable passkeys
3. Try `Lock with fingerprint or face` again - it should offer you the option to "Create a passkey in Google Password Manager" - this is the one that supports PRF

Alternatives that support PRF:

- **1Password, Bitwarden** (recent versions advertise PRF)
- iPhone: iCloud Keychain iOS 17+
- Windows Hello alone often does NOT support PRF encryption -> same error

If you stay on Brave / Samsung Pass / older Android: impossible. You must remain on `Lock Wallet` with a password, not biometrics.
This situation demonstrates that using good tools is not enough: it is also essential to remain attentive, organized, and responsible. Synchronized systems facilitate work, but human verification remains crucial for identifying errors and ensuring the reliability of operations. This experience serves as a reminder that technology must be accompanied by rigor, transparency, and a constant drive for improvement. In both professional and personal life, progress means learning from each situation and implementing better methods to prevent the same problems from recurring.
Thought I was smart using WPLocal.
No hosting fees, fast, offline. Perfect.

Then my SSD died last week.
I lost 3 client projects. ∼40 hours of work. Gone. Because WPLocal saves everything in AppData on your C drive. If you don't manually export, it doesn't exist anywhere else.

I was stupid. Don't be me.

My fix now is brain-dead simple:
Right-click on site in WPLocal > Export > Save directly to my Drive folder. I do it every time I stop working. 20 seconds.

Anyone else here learned this the hard way? How do you guys automate LocalWP backups? I'm testing WP Migrate to push DB to a private repo.
loved
1