# BUG: Export function does not work on Android app

**URL:** <https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576>\
**Category:** Authenticator\
**Tags:** auth:android, app:mobile\
**Created:** [October 1, 2025, 10:14am UTC](https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576 "2025-10-01T10:14:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lousybyte](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/lousybyte/32/42587_2.png) [@lousybyte](https://community.bitwarden.com/u/lousybyte)\
**Post date:** [October 1, 2025, 10:14am UTC](https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576/1 "2025-10-01T10:14:09Z")

</div>

The Export function on the Android app does not actually export anything, tried several times, all I get is this in the exported file:

authenticator\_export\_20251001110150.json

{“encrypted”:false,“items”:}

---

<div class="post-metadata">

**Author:** ![Nail1684](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/nail1684/32/47626_2.png) [@Nail1684](https://community.bitwarden.com/u/Nail1684)\
**Post date:** [October 1, 2025, 10:29am UTC](https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576/2 "2025-10-01T10:29:54Z")

</div>

@lousybyte Welcome to the forum!

Are you trying to export local codes which are stored in the authenticator app – or synced codes, that are synced with the password manager app/vault?

---

<div class="post-metadata">

**Author:** ![lousybyte](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/lousybyte/32/42587_2.png) [@lousybyte](https://community.bitwarden.com/u/lousybyte)\
**Post date:** [October 1, 2025, 10:42am UTC](https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576/3 "2025-10-01T10:42:53Z")

</div>

They are synced yes, are those not supported by the export function? If that’s the case, a suggestion would be to make it clear that’s the case somewhere when choosing that option.

---

<div class="post-metadata">

**Author:** ![Nail1684](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/nail1684/32/47626_2.png) [@Nail1684](https://community.bitwarden.com/u/Nail1684)\
**Post date:** [October 1, 2025, 10:46am UTC](https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576/4 "2025-10-01T10:46:27Z")

</div>

Aha… Yes, I agree. If you can, it would help to express that here as well:

> <https://github.com/bitwarden/android/issues/5637>
>
> \### Steps To Reproduce
> 
> 1. Prerequisite: have the TOTP sync between password man…ager/vault and authenticator app active - and the synced TOTP codes get shown in the authenticator app. (besides locally stored TOTP codes in the authenticator app)
> 3. Go to the Authenticator app und "unlock" it.
> 4. Go to Settings.
> 5. Choose "Export" (and then either json or csv and follow through with the export)
> 
> \### Expected Result
> 
> The user gets informed, that the export only considers the locally stored TOTP seeds and DOESN'T include any synced codes.
> 
> \### Actual Result
> 
> There is no information about the fact that not "all" of your TOTP codes get exported (the synced one's don't get exported!), but only the locally stored TOTP codes get exported.
> 
> Ideally, not only should the authenticator app show, that the synced TOTP codes don't get exported, but that those codes are still only exported, when one makes an export of the BW vault via one of the password manager clients.
> 
> \### Screenshots or Videos
> 
> \_No response\_
> 
> \### Additional Context
> 
> I really do consider it as a (UI/UX) "bug", that the export function of the authenticator app wasn't "updated" in that regard, to make it transparent to the user what export does (or does not) now since the "sync" functionality is also available - and you can have two "kinds" of TOTP codes in the authenticator app (locally v. synced), but the export function doesn't take into account that new situation.
> 
> \### Build Version
> 
> 2025.7.1 (601) --\> authenticator app
> 
> \### What server are you connecting to?
> 
> EU
> 
> \### Self-host Server Version
> 
> \_No response\_
> 
> \### Environment Details
> 
> \- Fairphone 5
> \- Android 15
> 
> \### 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.

&nbsp;

And the corresponding Help Sites need that info as well.

→ Summary: synced codes can’t be exported via the authenticator app.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/bitwarden1/original/1X/681d35175c3ce2ae5f010fa0bb448862f79a2399.png) [@system](https://community.bitwarden.com/u/system)\
**Post date:** [October 31, 2025, 8:46pm UTC](https://community.bitwarden.com/t/bug-export-function-does-not-work-on-android-app/89576/5 "2025-10-31T20:46:33Z")

</div>

Closed on October 31, 2025, 8:46pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
