Hi, I have updated my self-hosted Passbolt, CentOS 7 and script based, to the latest Master version.
I have also updated the Android App to the latest 1.13.2 version.
After having succesfully trasnfered the access with the QR code to the mobile, as soon as I login with my password the app crashes without returning any error, it simply closes down.
Steps to reproduce:
Transfer the account credentials with the QR code
Open the App and type my Password
Deny the usage of fingerprints
Deny the usage of auto-fill
The app seems opening when suddently closes down, crashing with no errors to the user. Impossibile to do anything before that.
Can you confirm the model of your Android device and/or which Android version it’s running?
Also try to find passbolt logs on the server side indicating what is happening. If you can’t find them, how did you install your passbolt? Via package or source?
Thanks, I checked the server time Vs mobile phone and they are both spot on!
Also, I guess if the server time wasn’t right then I would not be able to login from other desktop/laptops.
The issue points to a parsing error in Java… it seems more an unhandled exception to me… isnt’t it?
How can I contact the Passbolt Android developers to forward the stack trace?
Best regards
as a back-end developer, I am trying to reproduce your issue, with no success. You say you use CentOS7.
Which PHP version do you use? php -v
What is the output of the following command: /usr/share/php/passbolt/bin/cake passbolt version
Which database engine do you use, and which version?
If you call the url on your browser /resources.json?contain[permission]=1&contain[favorite]=1&contain[tag]=1&contain[permissions.group]=1&limit=1
without pasting the complete output here, can you indicate the format in which the dates created and modified are returned?
Please note everything works perfectly in Passbolt itself.
Based on the Android stack trace that I provided earlier, would it be feasible to handle in Android the different date/time format that may be returned? Perhaps jsut adding the missing index[19] to the date/time parameter before being parsed?
I have some good and bad news… let’s start witht he good one
I confirm that this issue is resolved when performing a clean install with version 4.2.0
Please note I installed from Source, in Ubuntu 22.04.
THANKS A LOT!
Unfortunatelly there’s another issue (not related to this one) in relation to the database migration from 4.0.0 to 4.2.0 …to put it simple, once migrated the existing accounts are no longer recognised so I had to start with a clean database and import all passwords from a backup… but that’s another story
I just wish to thanks everybody involved with upkeeping the project!