App Crashes After Login (DateTimeParseException)

[tldawson]

App Crashes After Login (DateTimeParseException)

• Passbolt Version: 3.8.3
• Platform and Target:
  -- Passbolt Android App: 1.11.0
  -- Android OS: LineageOS 19-20221117-NIGHTLY-barbet (Android 12)
  -- Phone: Google Pixel 5a
  -- Passbolt API: 3.8.3
  -- Device language: en-US

What you did

1. Install Passbolt mobile from the Play Store
2. Connect existing account by scanning QR codes in desktop browser
3. Enter passphrase on mobile app

What happened

After the passphrase is submitted, the app crashes. The logs seem to indicate its an issue with parsing the datetime string:
passbolt-mobile.log

What you expected to happen

The app to show my list of passwords like on desktop.

[marcin-michalek-miquido]

hello @tldawson, you are correct the issue is with the date time parsing.
On your server the date time field has value of 2021-10-22T19:34:41 and we use ZonedDateTime to parse the date times (so we expect format of 2021-10-22T19:34:41+00:00 or 2021-10-22T19:34:41Z).
I will see with the backend / support team if this can be achieved by configuring the server or we need to handle it some other way.

[tldawson]

I have no idea why the date string format is different than expected. Weird. Thanks @marcin-michalek-miquido!

[claytontstevenson]

hey @tldawson could you let me know what OS your server is and if you installed via source or the package? With that I'll be better able to point you in the correct direction

[tldawson]

@claytontstevenson The server was running Amazon Linux and Passbolt was installed from source.
Ultimately, I migrated to the prebuilt AMI because my users needed access to the mobile app feature... but the mobile app would still benefit from the flexibility of supporting less rigid datetime formats. I still have backups of the previous AMI, if you have any questions about the configuration.

[zipelkopf]

Hi, I recently reported the same issue in the Passbolt Community Forum (see https://community.passbolt.com/t/android-app-1-13-2-crashes-with-no-error/7479) and I agree it would be very beenficial to have this tiny uccups fixed.

My understanding is that time is passed as a string, indeed the exeption I got was about the unhandled situation of trying to parse the index at position 19, which of course does not exists in this type of format 2021-10-22T19:34:41 (having char-index from 0 to 18 only).

The actual time-value is identical across different time formats, perhaps if a shorter version is detected it could be simply extended to the preferable format, by simply appending the char Z, then being parsed.
Example: 2021-10-22T19:34:41 => 2021-10-22T19:34:41Z

Thanks a mill

[pabloelcolombiano]

@tldawson I have add a post on the community forum, where I propose to continue the discussion. Feel free to provide us with additional info, as suggested in this post.

[luisogandob]

Hi, same behavior here, but I'm using the docker version of Passbolt.

[marcin-michalek-miquido]

Hello guys - an additional date format enforcement was added to the API (v.4.1) in this commit. This should fix the issue.