How to report a bug in Passbolt Android App?

Hi all,
I would like to report a bug in the App running on my Samsung S5 and S8 phone.
Passwords are saved wrong!
The password field contains extra characters before and after the set password.
{“password”:“MyPasswordAs Saved”,“description”:""**
This makes the App useless.
Please point me in the right direction if this is not the place to report this bug.

Hi @Nikau :wave: and welcome to Passbolt community forum :slight_smile:

You are in the good place to report bugs and give feedback :slight_smile:

Passbolt mobile application for Android has not been released yet but will be available very soon. Last User Acceptance Testing is currently in progress before submit it to the play store.

If you have installed you should remove it ASAP as it is not the official Passbolt Android app.


Hi again @Nikau ,

Passbolt Android App has been published :

Please use this one for your tests.




Thank you…I did not realize I was using an unofficial version!

Now got the official version installed on my Android Tablet. However, I am not able to connect to an existing account. My browser extension / Profile page does not have the Mobile section to scan the QR code ?

Am I missing something obvious here ?

The mobile plugin is disabled, as the security audit is currently in progress. If you want to enable it, you can follow instructions from this blog post: Passbolt mobile app is here.. Beta testers needed! | by Maxence Zanardo | Nov, 2021 | passbolt

OK…Just enable the Mobile Plugin…App works fine on my Android :slight_smile:
Thank you.

Great, the current known issue is you won’t be able to connect to a passbolt instance if you are using a self-signed certificate, even if it is imported in your Android smartphone. A fix is on the way.

Are you referring to the SSL certificate on a Passbolt server ?
(My server is set up with SSL certificate that is verified by Let’s Encrypt and I can connect)

Yep, some users got issues and we will ship in the coming days a new release with more debug to keep track on this.

First test: LineageOS, Android 10

The transfer process using QR codes: the phone read the first code okay, and then hung. The phone was continuing to attempt the read and was re-focusing, but no progress. I scaled up my screen on my laptop to make the code larger, and the phone picked it up right away and progressed through the remaining codes.

I’m getting stuck after passphrase entry on setup with a display of app error:
Incorrect passphrase or decryption error. I have double-checked the passphrase so I think’s it’s a decryption error.

Android logs show:

  • before the authentication process an error of:
    Window Manager App trying to use insecure INPUT_FEATURE_NO_INPUT_CHANNEL flag. Ignoring.
  • Authentication steps show receipt of csrfToken and then success message for /auth/verify.json and there is a fingerprint and keydata shown.
  • This is followed by:
    Not performing software digesting for symmetric cipher keys
  • and ultimately InputDispatcher is reporting an error of:
    Window handle ... no registered input channel

On the server side:
Web server shows this sequence at the end:

"GET /auth/verify.json HTTP/2.0" 200 2128 "-" "okhttp/4.7.2"
"GET /auth/jwt/rsa.json HTTP/2.0" 200 1072 "-" "okhttp/4.7.2"
"GET /auth/jwt/rsa.json HTTP/2.0" 200 1072 "-" "okhttp/4.7.2"
"GET /auth/verify.json HTTP/2.0" 200 2128 "-" "okhttp/4.7.2"

NGINX is reporting client prematurely closed connection while processing HTTP/2 connection.

Second test: Android phone #2, Samsung S5 LineageOS 11

QR transfer codes can’t be read - the autofocus on camera is for some reason not functional on this step.

This seems resolved with recent update (or possibly I used a different browser with different render scaling).

At this point I am having the same issue on both devices after trying again with v1.1 - maybe it is related to something on each device. Is there a default Android library or some Google-based requirement possibly? Both devices run a microG build of LineageOS. One is Android 10, the other is Android 11. For each it appears that keystore version 3 is running, and not version 4.

Permissions are checking out fine so I really don’t know at this point what might be the cause. Device logs show the app receives jwt.pem and then the server side says it disconnects prematurely.

@max Posting again to note that a 2019 Moto G7 Plus (shipped with Android 10 and currently running Android 11) has the same behavior and error message. Cannot proceed past the passphrase entry.

Does your instance is publicly accessible? If so could it be possible to add my email to it? I will try to setup an android device.

Thanks @max and @remy for the assistance on my instance. The server gpg keys, both public and private, had an extra empty line before the closing tag. Not exactly sure how those got there, but my sense is somehow I created those empty lines. App works fine now on the Moto G7 Plus. Will test the other devices as well.

Our Sales and Marketing teams would like access to passwords for websites on their mobiles. password manager and Passbolt is an great option for us only the lack of mobile is holding us back at the moment.

@Hodkiewicz Try the mobile app, we think it’s great. If you have trouble, post back.