dwbit
September 1, 2025, 9:20pm
1
2 Likes
@dwbit , do you mean that the application might be unstable, or that database corruption is probable? I don’t mind the former, but the latter I do.
Has CXP yet been implemented? I’m using 2025.9.0
, but don’t see it:
Hi, Apparently with the 2025.9.0 (2578) version release of Bitwarden's iOS client application on iOS 26, there's a new CXP import/export support with compatible apps. Is this option behind a server...
The Release Notes claim it has been implemented:
1 Like
@Nail1684 , yet bitwarden.com/help/import-data
lacks any mention of importing from the “Passwords” application, which, presumably, means no support for exporting the Apple ID passkey. I cannot imagine that that is an accidental oversight, or technical limitation that they haven’t bothered to document.
It does mention it - in the “mobile app” tab: Import Data | Bitwarden
1 Like
@Nail1684 , thanks. That process invokes the cited modal:
keychain, passkey
However, with Bitwarden, it fails:
opened 12:10AM - 24 Sep 25 UTC
bug
beta
app:password-manager
### Steps To Reproduce
1. Register BW Beta as an autofill provider with the OS.…
1. Enter "Passwords".
1. Select the pill button.
1. Select the exportation context menu entrant.
1. Select a credential that solely includes a username and FIDO2 key.
1. Select "Continue".
### Expected Result
Bitwarden should have accepted the export.
### Actual Result
It does not.
### Screenshots or Videos
https://github.com/user-attachments/assets/8d400caa-dc2b-4186-a29d-6941160129b1
### Additional Context
_No response_
### Build Version
`2025.9.0`
### What server are you connecting to?
US
### Self-host Server Version
_No response_
### Environment Details
1. ~~~sh
#!/bin/sh
ufetch
~~~
1. <blockquote>
~~~YAML
OS: iPhone OS 26.1
KERNEL: Darwin 25.1.0
~~~
</blockquote>
### Issue Tracking Info
- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Considering that exportation fails too, CXP support may not work:
opened 04:02AM - 12 Aug 25 UTC
bug
app:password-manager
### Steps To Reproduce
1. Go to settings.
2. Tap on vault.
3. Export vault.
4. … Export as. JSON
### Expected Result
The exported json does not include passkeys is this an issue? I’m exporting via bitwarden on iPhone.
### Actual Result
The exported json does not include passkeys is this an issue? I’m exporting via bitwarden on iPhone.
### Screenshots or Videos
_No response_
### Additional Context
_No response_
### Build Version
Latest
### What server are you connecting to?
US
### Self-host Server Version
_No response_
### Environment Details
_No response_
### Issue Tracking Info
- [ ] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Regardless, I have begun to believe that Apple’s passkey may be excluded:
macos, ios, passkey
1 Like
… just out of curiosity: same result with the 2025.9.0 release (non-Beta) version?
… or “still” not there in the 2025.9.0 release?
1 Like
@Nail1684 , there, exportation works!
opened 12:10AM - 24 Sep 25 UTC
bug
beta
app:password-manager
### Steps To Reproduce
1. Register BW Beta as an autofill provider with the OS.…
1. Enter "Passwords".
1. Select the pill button.
1. Select the exportation context menu entrant.
1. Select a credential that solely includes a username and FIDO2 key.
1. Select "Continue".
### Expected Result
Bitwarden should have accepted the export.
### Actual Result
It does not.
### Screenshots or Videos
https://github.com/user-attachments/assets/8d400caa-dc2b-4186-a29d-6941160129b1
### Additional Context
Tangentially, this is the opposite of https://github.com/bitwarden/ios/issues/1850#issue-3312436164.
### Build Version
`2025.9.0` (2520)
### What server are you connecting to?
US
### Environment Details
1. ~~~sh
#!/bin/sh
ufetch
~~~
1. <blockquote>
~~~YAML
OS: iPhone OS 26.1
KERNEL: Darwin 25.1.0
~~~
</blockquote>
### Issue Tracking Info
- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Thanks. Turns out that the Beta application is an older build.
1 Like
… seems like it was a short Beta test period… and then it was already incorporated in the release.
1 Like
@Nail1684 , I presume that it should remain updated, though. Otherwise, you’ve a situation similar to flathub-beta
’s:
opened 02:29PM - 24 Sep 25 UTC
This is common enough that it has sparked multiple discussions, per https://gith… ub.com/flathub-infra/linux-store-frontend/issues/305#issuecomment-926946046. That issue would have progressed, had its repository not been archived. I apologise for requiring this much time to transfer it. [^1]
I suggest that, when a new version is pushed to `flathub` for a package identifier that corresponds to a lesser version on `flathub-beta`, that `flathub-beta` incorporate that stable package as an update. This means that application developers can push `//beta` updates solely when need be.
[^1]: [`discourse.flathub.org/t/1710/4`][1]
[1]: https://discourse.flathub.org/t/flathub-beta-is-storing-old-versions-of-software/1710/4
If that isn’t occurring, I’ll file an issue for it.
1 Like