github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4706] Not able to access Bitwarden-hosted vault on Android Bitwarden 2025.1.1 (S23 Ultra Android 14 Security patch Jan 2025) #21425

New Issue
Closed
opened 2026-04-16 21:54:37 -05:00 by GiteaMirror · 14 comments
GiteaMirror commented 2026-04-16 21:54:37 -05:00
Owner
Copy Link

Originally created by @vrosu on GitHub (Feb 8, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/4706

Steps To Reproduce

Issue started after updating to 2025.1.0, reported to Customer Support as request 585921 on Jan 17 2025.
2. Open Bitwarden Android client
3. Login by providing user, password and the associated MFA (either Authenticator code or Yubikey)
4. Error message appears: "We were unable to process your request. Please try again or contact us"

Expected Result

Be able to view my vault content in Bitwarden Android client

Actual Result

I am not able to view my vault content in Bitwarden Android client (started on 2025.1.0, the same on 2025.1.1)

Screenshots or Videos

Image

Additional Context

The following unsuccessful attempts to solve were done via the Customer Support interaction:

  1. Reset data and cache
  2. Remove app, shutdown phone, install app
  3. Connected on via mobile network instead of WiFi
  4. Used another completely new phone to attempt the same operations on WiFi
  5. Deauthorize sessions in web interface

Accessing the web version (vault.bitwarden.com) via browser from the same home network works.
Accessing the vault via the Bitwarden IoS 2025.1.2 client from the same home network works.

Build Version

2025.1.1

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

-Samsung S23 Ultra
-Android 14, Security patch level: Jan 1 2025

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.
Originally created by @vrosu on GitHub (Feb 8, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/4706 ### Steps To Reproduce Issue started after updating to 2025.1.0, reported to Customer Support as request 585921 on Jan 17 2025. 2. Open Bitwarden Android client 3. Login by providing user, password and the associated MFA (either Authenticator code or Yubikey) 4. Error message appears: "We were unable to process your request. Please try again or contact us" ### Expected Result Be able to view my vault content in Bitwarden Android client ### Actual Result I am not able to view my vault content in Bitwarden Android client (started on 2025.1.0, the same on 2025.1.1) ### Screenshots or Videos ![Image](https://github.com/user-attachments/assets/11391755-10c9-415b-b5b6-d46b0b6add58) ### Additional Context The following **unsuccessful** attempts to solve were done via the Customer Support interaction: 1. Reset data and cache 2. Remove app, shutdown phone, install app 3. Connected on via mobile network instead of WiFi 4. Used another completely new phone to attempt the same operations on WiFi 5. Deauthorize sessions in web interface Accessing the web version (vault.bitwarden.com) via browser from the same home network **works.** Accessing the vault via the Bitwarden IoS 2025.1.2 client from the same home network **works.** ### Build Version 2025.1.1 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details -Samsung S23 Ultra -Android 14, Security patch level: Jan 1 2025 ### 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.
GiteaMirror added the bug label 2026-04-16 21:54:37 -05:00
GiteaMirror commented 2026-04-16 21:54:38 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 8, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-18140

<!-- gh-comment-id:2645934470 --> @bitwarden-bot commented on GitHub (Feb 8, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-18140
GiteaMirror commented 2026-04-16 21:54:38 -05:00
Author
Owner
Copy Link

@vrosu commented on GitHub (Feb 8, 2025):

On Feb 5th 2025 I've been told via CS that "Version 2025.1.2 should be available for Android clients as well". Obviously incorrect, since we're still on version 2025.1.1 at the time of writing this post. When is that expected to be released? (seeing this as a last resort attempt)

<!-- gh-comment-id:2645935056 --> @vrosu commented on GitHub (Feb 8, 2025): On Feb 5th 2025 I've been told via CS that "Version 2025.1.2 should be available for Android clients as well". Obviously incorrect, since we're still on version 2025.1.1 at the time of writing this post. When is that expected to be released? (seeing this as a last resort attempt)
GiteaMirror commented 2026-04-16 21:54:39 -05:00
Author
Owner
Copy Link

@yodasad commented on GitHub (Feb 12, 2025):

Version 2025.1.2 (19740) the problem remains unsolved :(

<!-- gh-comment-id:2653652550 --> @yodasad commented on GitHub (Feb 12, 2025): Version 2025.1.2 (19740) the problem remains unsolved :(
GiteaMirror commented 2026-04-16 21:54:40 -05:00
Author
Owner
Copy Link

@vrosu commented on GitHub (Feb 12, 2025):

Hi @yodasad . Are you experiencing the same issue like me? You're using vault hosted by BW, right?

<!-- gh-comment-id:2653894549 --> @vrosu commented on GitHub (Feb 12, 2025): Hi @yodasad . Are you experiencing the same issue like me? You're using vault hosted by BW, right?
GiteaMirror commented 2026-04-16 21:54:40 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Feb 12, 2025):

Hi all,

Would anyone be willing to check for logs in a dev build? If there is an error connecting to our servers or decrypting vault data you should see logs emitted in logcat.

<!-- gh-comment-id:2654033267 --> @SaintPatrck commented on GitHub (Feb 12, 2025): Hi all, Would anyone be willing to check for logs in a dev build? If there is an error connecting to our servers or decrypting vault data you should see logs emitted in logcat.
GiteaMirror commented 2026-04-16 21:54:41 -05:00
Author
Owner
Copy Link

@vrosu commented on GitHub (Feb 12, 2025):

@SaintPatrck Absolutely. What are the steps to do this? I can install a separate apk (is the dev build mentioned above the dev build from the existing releases?), but I just need to have the proper steps.

<!-- gh-comment-id:2654189958 --> @vrosu commented on GitHub (Feb 12, 2025): @SaintPatrck Absolutely. What are the steps to do this? I can install a separate apk (is the dev build mentioned above the dev build from the existing releases?), but I just need to have the proper steps.
GiteaMirror commented 2026-04-16 21:54:42 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Feb 13, 2025):

@vrosu

Thank you for assisting. Before we go through capturing logs, can you check if the change from #4721 resolves your issue?

A build with the change can be downloaded from this job run: https://github.com/bitwarden/android/actions/runs/13315247004

You'll want to download either com.x8bit.biwarden.dev.apk (dev build) or com.x8bit.bitwarden.beta.apk (beta build) so that you don't overwrite your production installation.

I suggest downloading directly onto your device to makes things easier. Once complete, navigate to the downloaded APK and tap it to start installation. If this is the first time you've installed an application outside of Play Store, you may be prompted to allow installations from other sources. Follow the system prompts to grant permission and complete installation.

If your vault loads after logging in, it will confirm you're running into an issue similar to the one @cseufert is experiencing and submitted a fix for (#4721).

If the change from #4721 does not fix your issue we can look into capturing logs, which is a little more involved. A quick search led me to a Citrix article that does a great job explaining how to connect your device and capture logs using ADB.

<!-- gh-comment-id:2657603048 --> @SaintPatrck commented on GitHub (Feb 13, 2025): @vrosu Thank you for assisting. Before we go through capturing logs, can you check if the change from #4721 resolves your issue? A build with the change can be downloaded from this job run: https://github.com/bitwarden/android/actions/runs/13315247004 You'll want to download either [com.x8bit.biwarden.dev.apk](https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588291401) (dev build) or [com.x8bit.bitwarden.beta.apk](https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588330038) (beta build) so that you don't overwrite your production installation. I suggest downloading directly onto your device to makes things easier. Once complete, navigate to the downloaded APK and tap it to start installation. If this is the first time you've installed an application outside of Play Store, you may be prompted to allow installations from other sources. Follow the system prompts to grant permission and complete installation. If your vault loads after logging in, it will confirm you're running into an issue similar to the one @cseufert is experiencing and submitted a fix for (#4721). If the change from #4721 does not fix your issue we can look into capturing logs, which is a little more involved. A quick search led me to a Citrix article that does a great job explaining [how to connect your device and capture logs using ADB](https://support.citrix.com/s/article/CTX232375-how-to-install-and-collect-adb-logs-on-android-device?language=en_US).
GiteaMirror commented 2026-04-16 21:54:42 -05:00
Author
Owner
Copy Link

@cseufert commented on GitHub (Feb 13, 2025):

Hi

Yes, #4721 is my PR, and this fixed my issue (vault wont load), tested in
android studio before submitting the PR.

My device is running under google Advanced Protection Program which makes
it super hard to sideload apps on the device.

On Fri, 14 Feb 2025 at 07:06, Patrick Honkonen @.***>
wrote:

@vrosu https://github.com/vrosu

Thank you for assisting. Before we go through capturing logs, can you
check if the change from #4721
https://github.com/bitwarden/android/pull/4721 resolves your issue?

A build with the change can be downloaded from this job run:
https://github.com/bitwarden/android/actions/runs/13315247004

You'll want to download either com.x8bit.biwarden.dev.apk
https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588291401
(dev build) or com.x8bit.bitwarden.beta.apk
https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588330038
(beta build) so that you don't overwrite your production installation.

I suggest downloading directly onto your device to makes things easier.
Once complete, navigate to the downloaded APK and tap it to start
installation. If this is the first time you've installed an application
outside of Play Store, you may be prompted to allow installations from
other sources. Follow the system prompts to grant permission and complete
installation.

If your vault loads after logging in, it will confirm you're running into
an issue similar to the one @cseufert https://github.com/cseufert is
experiencing and submitted a fix for (#4721
https://github.com/bitwarden/android/pull/4721).

If the change from #4721 https://github.com/bitwarden/android/pull/4721
does not fix your issue we can look into capturing logs, which is a little
more involved. A quick search led me to a Citrix article that does a great
job explaining how to connect your device and capture logs using ADB
https://support.citrix.com/s/article/CTX232375-how-to-install-and-collect-adb-logs-on-android-device?language=en_US
.

—
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/android/issues/4706#issuecomment-2657603048,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANHO55CY2FRJAATMSSZFNL2PT3MDAVCNFSM6AAAAABWYBLDCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGYYDGMBUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>
[image: SaintPatrck]SaintPatrck left a comment (bitwarden/android#4706)
https://github.com/bitwarden/android/issues/4706#issuecomment-2657603048

@vrosu https://github.com/vrosu

Thank you for assisting. Before we go through capturing logs, can you
check if the change from #4721
https://github.com/bitwarden/android/pull/4721 resolves your issue?

A build with the change can be downloaded from this job run:
https://github.com/bitwarden/android/actions/runs/13315247004

You'll want to download either com.x8bit.biwarden.dev.apk
https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588291401
(dev build) or com.x8bit.bitwarden.beta.apk
https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588330038
(beta build) so that you don't overwrite your production installation.

I suggest downloading directly onto your device to makes things easier.
Once complete, navigate to the downloaded APK and tap it to start
installation. If this is the first time you've installed an application
outside of Play Store, you may be prompted to allow installations from
other sources. Follow the system prompts to grant permission and complete
installation.

If your vault loads after logging in, it will confirm you're running into
an issue similar to the one @cseufert https://github.com/cseufert is
experiencing and submitted a fix for (#4721
https://github.com/bitwarden/android/pull/4721).

If the change from #4721 https://github.com/bitwarden/android/pull/4721
does not fix your issue we can look into capturing logs, which is a little
more involved. A quick search led me to a Citrix article that does a great
job explaining how to connect your device and capture logs using ADB
https://support.citrix.com/s/article/CTX232375-how-to-install-and-collect-adb-logs-on-android-device?language=en_US
.

—
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/android/issues/4706#issuecomment-2657603048,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANHO55CY2FRJAATMSSZFNL2PT3MDAVCNFSM6AAAAABWYBLDCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGYYDGMBUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Chris Seufert

M. 0424 066 016 T. 03 9510 7477
The Well - 1 / 21 Wellington St, St Kilda, Victoria 3182, Australia
modd.com.au http://modd.com.au/ - udo.net.au
http://udo.net.au/ - artsphere.com.au http://artsphere.com.au/

<!-- gh-comment-id:2657906565 --> @cseufert commented on GitHub (Feb 13, 2025): Hi Yes, #4721 is my PR, and this fixed my issue (vault wont load), tested in android studio before submitting the PR. My device is running under google Advanced Protection Program which makes it super hard to sideload apps on the device. On Fri, 14 Feb 2025 at 07:06, Patrick Honkonen ***@***.***> wrote: > @vrosu <https://github.com/vrosu> > > Thank you for assisting. Before we go through capturing logs, can you > check if the change from #4721 > <https://github.com/bitwarden/android/pull/4721> resolves your issue? > > A build with the change can be downloaded from this job run: > https://github.com/bitwarden/android/actions/runs/13315247004 > > You'll want to download either com.x8bit.biwarden.dev.apk > <https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588291401> > (dev build) or com.x8bit.bitwarden.beta.apk > <https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588330038> > (beta build) so that you don't overwrite your production installation. > > I suggest downloading directly onto your device to makes things easier. > Once complete, navigate to the downloaded APK and tap it to start > installation. If this is the first time you've installed an application > outside of Play Store, you may be prompted to allow installations from > other sources. Follow the system prompts to grant permission and complete > installation. > > If your vault loads after logging in, it will confirm you're running into > an issue similar to the one @cseufert <https://github.com/cseufert> is > experiencing and submitted a fix for (#4721 > <https://github.com/bitwarden/android/pull/4721>). > > If the change from #4721 <https://github.com/bitwarden/android/pull/4721> > does not fix your issue we can look into capturing logs, which is a little > more involved. A quick search led me to a Citrix article that does a great > job explaining how to connect your device and capture logs using ADB > <https://support.citrix.com/s/article/CTX232375-how-to-install-and-collect-adb-logs-on-android-device?language=en_US> > . > > — > Reply to this email directly, view it on GitHub > <https://github.com/bitwarden/android/issues/4706#issuecomment-2657603048>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AANHO55CY2FRJAATMSSZFNL2PT3MDAVCNFSM6AAAAABWYBLDCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGYYDGMBUHA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > [image: SaintPatrck]*SaintPatrck* left a comment (bitwarden/android#4706) > <https://github.com/bitwarden/android/issues/4706#issuecomment-2657603048> > > @vrosu <https://github.com/vrosu> > > Thank you for assisting. Before we go through capturing logs, can you > check if the change from #4721 > <https://github.com/bitwarden/android/pull/4721> resolves your issue? > > A build with the change can be downloaded from this job run: > https://github.com/bitwarden/android/actions/runs/13315247004 > > You'll want to download either com.x8bit.biwarden.dev.apk > <https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588291401> > (dev build) or com.x8bit.bitwarden.beta.apk > <https://github.com/bitwarden/android/actions/runs/13315247004/artifacts/2588330038> > (beta build) so that you don't overwrite your production installation. > > I suggest downloading directly onto your device to makes things easier. > Once complete, navigate to the downloaded APK and tap it to start > installation. If this is the first time you've installed an application > outside of Play Store, you may be prompted to allow installations from > other sources. Follow the system prompts to grant permission and complete > installation. > > If your vault loads after logging in, it will confirm you're running into > an issue similar to the one @cseufert <https://github.com/cseufert> is > experiencing and submitted a fix for (#4721 > <https://github.com/bitwarden/android/pull/4721>). > > If the change from #4721 <https://github.com/bitwarden/android/pull/4721> > does not fix your issue we can look into capturing logs, which is a little > more involved. A quick search led me to a Citrix article that does a great > job explaining how to connect your device and capture logs using ADB > <https://support.citrix.com/s/article/CTX232375-how-to-install-and-collect-adb-logs-on-android-device?language=en_US> > . > > — > Reply to this email directly, view it on GitHub > <https://github.com/bitwarden/android/issues/4706#issuecomment-2657603048>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AANHO55CY2FRJAATMSSZFNL2PT3MDAVCNFSM6AAAAABWYBLDCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGYYDGMBUHA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- Chris Seufert *M.* 0424 066 016 *T.* 03 9510 7477 *The Well* - 1 / 21 Wellington St, St Kilda, Victoria 3182, Australia *modd.com.au <http://modd.com.au/> - udo.net.au <http://udo.net.au/> - artsphere.com.au <http://artsphere.com.au/>*
GiteaMirror commented 2026-04-16 21:54:43 -05:00
Author
Owner
Copy Link

@vrosu commented on GitHub (Feb 15, 2025):

@SaintPatrck Thanks a lot for the time taken to help and @cseufert for that PR. In short:

  1. I tried the dev build from #4721 . It did not resolve my issue. For clarity, the About, Version shows: 2025.2.0 (19806).
  2. With the same dev build from the change above, I ran logcat based on that article exactly at the time of logon (after I cleared the data and cache, I tried logging on once, it failed, then after that I tried doing the logcat, to minimize the window of investigation since the 2FA was not prompted again).
    What I observed was the following error:
    02-15 13:37:45.784 20883 23221 D BitwardenNetworkClient: <-- END HTTP (1773879-byte body)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: Network Error: https://api.bitwarden.com/sync
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: java.lang.IllegalArgumentException: Unknown value 1
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.platform.datasource.network.serializer.BaseEnumeratedIntSerializer.deserialize(BaseEnumeratedIntSerializer.kt:32)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.platform.datasource.network.serializer.BaseEnumeratedIntSerializer.deserialize(BaseEnumeratedIntSerializer.kt:16)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableValue(AbstractDecoder.kt:43)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableElement(AbstractDecoder.kt:70)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableElement(StreamingJsonDecoder.kt:168)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$Cipher$SecureNote$$serializer.deserialize(SyncResponseJson.kt:774)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$Cipher$SecureNote$$serializer.deserialize(SyncResponseJson.kt:774)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableValue(AbstractDecoder.kt:43)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeNullableSerializableElement(AbstractDecoder.kt:78)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$Cipher$$serializer.deserialize(SyncResponseJson.kt:435)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$Cipher$$serializer.deserialize(SyncResponseJson.kt:435)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableValue(AbstractDecoder.kt:43)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableElement(AbstractDecoder.kt:70)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableElement(StreamingJsonDecoder.kt:168)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.CompositeDecoder.decodeSerializableElement$default(Decoding.kt:539)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.internal.CollectionLikeSerializer.readElement(CollectionSerializers.kt:80)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.internal.AbstractCollectionSerializer.readElement$default(CollectionSerializers.kt:51)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.internal.AbstractCollectionSerializer.merge(CollectionSerializers.kt:36)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.internal.AbstractCollectionSerializer.deserialize(CollectionSerializers.kt:43)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableValue(AbstractDecoder.kt:43)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeNullableSerializableElement(AbstractDecoder.kt:78)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$$serializer.deserialize(SyncResponseJson.kt:26)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$$serializer.deserialize(SyncResponseJson.kt:26)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.Json.decodeFromString(Json.kt:149)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.converter.kotlinx.serialization.Serializer$FromString.fromResponseBody(Serializer.kt:26)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.converter.kotlinx.serialization.DeserializationStrategyConverter.convert(DeserializationStrategyConverter.kt:11)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.converter.kotlinx.serialization.DeserializationStrategyConverter.convert(DeserializationStrategyConverter.kt:7)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.OkHttpCall.parseResponse(OkHttpCall.java:246)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:156)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
    02-15 13:37:45.836 20883 23221 W NetworkResultCall: at java.lang.Thread.run(Thread.java:1012)
    02-15 13:37:45.837 20883 20942 I t.bitwarden.dev: Explicit concurrent mark compact GC freed 4330(292KB) AllocSpace objects, 1(1736KB) LOS objects, 49% free, 10MB/20MB, paused 235us,1.709ms total 24.275ms

If needed, I can paste the relevant logcat file in its entirety, just that I'll need to obfuscate my profile data that's being output in the lines above.

A few observations:

  1. The same error appeared when trying to logon the first time (when I was prompted for the 2FA) and the second time (when I needed to insert just the master password)
  2. The count of bytes from the "END HTTP (1773879-byte body)" line in the beginning is identical in both the cases above.
  3. In case it matters: this vault was created programmatically with the BW CLI from a MSecure exported CSV (I had custom fields that required importing). Those custom fields still exist nowadays.
<!-- gh-comment-id:2660886161 --> @vrosu commented on GitHub (Feb 15, 2025): @SaintPatrck Thanks a lot for the time taken to help and @cseufert for that PR. In short: 1. I tried the dev build from [#4721](https://github.com/bitwarden/android/pull/4721 ) . It did not resolve my issue. For clarity, the About, Version shows: 2025.2.0 (19806). 2. With the same dev build from the change above, I ran logcat based on that article exactly at the time of logon (after I cleared the data and cache, I tried logging on once, it failed, then _after_ that I tried doing the logcat, to minimize the window of investigation since the 2FA was not prompted again). What I observed was the following error: 02-15 13:37:45.784 20883 23221 D BitwardenNetworkClient: <-- END HTTP (1773879-byte body) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: Network Error: https://api.bitwarden.com/sync 02-15 13:37:45.836 20883 23221 W NetworkResultCall: java.lang.IllegalArgumentException: Unknown value 1 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.platform.datasource.network.serializer.BaseEnumeratedIntSerializer.deserialize(BaseEnumeratedIntSerializer.kt:32) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.platform.datasource.network.serializer.BaseEnumeratedIntSerializer.deserialize(BaseEnumeratedIntSerializer.kt:16) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableValue(AbstractDecoder.kt:43) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableElement(AbstractDecoder.kt:70) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableElement(StreamingJsonDecoder.kt:168) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$Cipher$SecureNote$$serializer.deserialize(SyncResponseJson.kt:774) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$Cipher$SecureNote$$serializer.deserialize(SyncResponseJson.kt:774) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableValue(AbstractDecoder.kt:43) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeNullableSerializableElement(AbstractDecoder.kt:78) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$Cipher$$serializer.deserialize(SyncResponseJson.kt:435) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$Cipher$$serializer.deserialize(SyncResponseJson.kt:435) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableValue(AbstractDecoder.kt:43) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableElement(AbstractDecoder.kt:70) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableElement(StreamingJsonDecoder.kt:168) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.CompositeDecoder.decodeSerializableElement$default(Decoding.kt:539) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.internal.CollectionLikeSerializer.readElement(CollectionSerializers.kt:80) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.internal.AbstractCollectionSerializer.readElement$default(CollectionSerializers.kt:51) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.internal.AbstractCollectionSerializer.merge(CollectionSerializers.kt:36) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.internal.AbstractCollectionSerializer.deserialize(CollectionSerializers.kt:43) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeSerializableValue(AbstractDecoder.kt:43) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.encoding.AbstractDecoder.decodeNullableSerializableElement(AbstractDecoder.kt:78) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$$serializer.deserialize(SyncResponseJson.kt:26) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at com.x8bit.bitwarden.data.vault.datasource.network.model.SyncResponseJson$$serializer.deserialize(SyncResponseJson.kt:26) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.internal.StreamingJsonDecoder.decodeSerializableValue(StreamingJsonDecoder.kt:69) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at kotlinx.serialization.json.Json.decodeFromString(Json.kt:149) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.converter.kotlinx.serialization.Serializer$FromString.fromResponseBody(Serializer.kt:26) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.converter.kotlinx.serialization.DeserializationStrategyConverter.convert(DeserializationStrategyConverter.kt:11) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.converter.kotlinx.serialization.DeserializationStrategyConverter.convert(DeserializationStrategyConverter.kt:7) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.OkHttpCall.parseResponse(OkHttpCall.java:246) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:156) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644) 02-15 13:37:45.836 20883 23221 W NetworkResultCall: at java.lang.Thread.run(Thread.java:1012) 02-15 13:37:45.837 20883 20942 I t.bitwarden.dev: Explicit concurrent mark compact GC freed 4330(292KB) AllocSpace objects, 1(1736KB) LOS objects, 49% free, 10MB/20MB, paused 235us,1.709ms total 24.275ms If needed, I can paste the relevant logcat file in its entirety, just that I'll need to obfuscate my profile data that's being output in the lines above. A few observations: 1. The same error appeared when trying to logon the first time (when I was prompted for the 2FA) and the second time (when I needed to insert just the master password) 2. The count of bytes from the "END HTTP (1773879-byte body)" line in the beginning is identical in both the cases above. 3. In case it matters: this vault was created programmatically with the BW CLI from a MSecure exported CSV (I had custom fields that required importing). Those custom fields still exist nowadays. 4.
GiteaMirror commented 2026-04-16 21:54:43 -05:00
Author
Owner
Copy Link

@vrosu commented on GitHub (Feb 17, 2025):

I tried today to ask ChatGPT what could cause this:

  1. I disabled PrivateDNS - now it uses the network provided DNS - no change
  2. I don't have Data Saver enabled
  3. No Knox setup
    To take a wild guess, it seems that there's a network error that stops the whole vault content to be received by my Android (not sure whether the Server stops the connection or the Client stops it).
<!-- gh-comment-id:2664054357 --> @vrosu commented on GitHub (Feb 17, 2025): I tried today to ask ChatGPT what could cause this: 1. I disabled PrivateDNS - now it uses the network provided DNS - no change 2. I don't have Data Saver enabled 3. No Knox setup To take a wild guess, it seems that there's a network error that stops the whole vault content to be received by my Android (not sure whether the Server stops the connection or the Client stops it).
GiteaMirror commented 2026-04-16 21:54:43 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Feb 18, 2025):

@vrosu thank you for providing those logs. We've identified the issue and are working on a fix.

<!-- gh-comment-id:2666811704 --> @SaintPatrck commented on GitHub (Feb 18, 2025): @vrosu thank you for providing those logs. We've identified the issue and are working on a fix.
GiteaMirror commented 2026-04-16 21:54:44 -05:00
Author
Owner
Copy Link

@vrosu commented on GitHub (Feb 22, 2025):

@SaintPatrck thanks. When would you estimate a build I can test would exist?

<!-- gh-comment-id:2676176241 --> @vrosu commented on GitHub (Feb 22, 2025): @SaintPatrck thanks. When would you estimate a build I can test would exist?
GiteaMirror commented 2026-04-16 21:54:44 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Feb 27, 2025):

@vrosu Unfortunately we will not be able to resolve this with code changes to the Android client. Please reach out to our CS team and reference this ticket. They will work with you to clean up the erroneous data in your vault. If asked, let them know that your vault contains invalid "SecureNoteType" identifiers.

<!-- gh-comment-id:2688649292 --> @SaintPatrck commented on GitHub (Feb 27, 2025): @vrosu Unfortunately we will not be able to resolve this with code changes to the Android client. Please reach out to our CS team and reference this ticket. They will work with you to clean up the erroneous data in your vault. If asked, let them know that your vault contains invalid "SecureNoteType" identifiers.
GiteaMirror commented 2026-04-16 21:54:45 -05:00
Author
Owner
Copy Link

@vrosu commented on GitHub (Feb 28, 2025):

I do not understand why this issue can't be solved via code, considering the Windows app is capable of opening the vault. By closing this it means that there will be different (rather drastic) behavior between Windows and Android apps.
I canceled my subscription and moved to Proton Pass but I must say thanks for the responsive community in diagnosing this.

<!-- gh-comment-id:2691701170 --> @vrosu commented on GitHub (Feb 28, 2025): I do not understand why this issue can't be solved via code, considering the Windows app is capable of opening the vault. By closing this it means that there will be different (rather drastic) behavior between Windows and Android apps. I canceled my subscription and moved to Proton Pass but I must say thanks for the responsive community in diagnosing this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21425
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?