Crash on 0.18.0 with blank screen

[gandalff512]

hello friend! In the new version 0.18.0 for android, there is a white screen after authorization. The version of my firefly-iii is 6.1.18. I tried resetting the application settings, but it didn't help. My phone is Samsung S23

[SimonAkers]

I'm having the same issue, using a Samsung Galaxy S22+. FF3 v6.1.18 (latest).

I first noticed the issue a couple weeks ago after it starting saying "New update available!" in the app itself. Clicking "yes" to update would cause this issue regardless of if I cleared app data and setup credentials again. After authorization, you get a white screen and cannot use the app.

For a while, I was able to get past it by clicking "cancel" on the update notification (after resetting the app data), but now with the latest version of the app being pushed to the Google Play store on July 4th, there's no notification that pops up or workaround I've found.

Let me know if I can be of any extra help, would love to see this fixed so I can keep using the app!

[victorbalssa]

Hey!

I'm trying to replicate this locally, it's working smoothly for me on my Android.

Do you have any special configurations on how you access your Firefly III instance?

Can you try to connect to https://demo.firefly-iii.org/ with OAuth to see if it comes from FIII or Abacus?

Thanks!

[SimonAkers]

I've just tried it out with the demo version and it works fine. I'll have to do some digging after work today to see if I can find anything weird with my configuration, to my knowledge it's fairly standard. It's running in Docker behind NGINX with HTTPS, it could be something I need to update with NGINX if something in FIII changed. Any thoughts?

[victorbalssa]

With HTTPS

Do you have custom local certificates on your android?

[gandalff512]

I have through https://demo .firefly-iii.org / with OAuth, everything works too.

In my configuration, I also use Docker, an HTTP connection

[gandalff512]

All settings are standard, I tried to connect via OAuth and Personal Access Tokens

[SimonAkers]

With HTTPS

Do you have custom local certificates on your android?

I don't believe so. I had previously manually registered the domain with LetsEncrypt using Certbot. I believe that has expired though, but my domain registrar (Porkbun) now automatically manages a LetsEncrypt cert for the domain on my behalf. There could be something conflicting with the old manual cert I made, but I believe that expired some months ago and the issue is within the last 2-3 weeks. The default Firefly web GUI works fine and reports a secure connection on all my devices, so there's no immediately obvious problems.

If you don't mind my asking @victorbalssa, what brand Android are you using? I know Samsung has a pretty heavily modified version of Android so I am keeping in mind that it could be an isolated issue. Though I'm guessing since the demo worked then it's not an Android problem necessarily (however the demo is on the development branch afaik and I'm running release).

I'll try to look into it closer ASAP and get back to you about it (work keeping me busy lately). I'll want to see if NGINX or Docker has any notable logs.

Thanks for the fast responses! I appreciate your hard work.

[advait404]

Hi, I am having this same issue.

I am using http connection to my local WiFi device
(http://192.168.101.10:8080)

It gives the white screen issue in both authentication methods (Oauth token and personal access token)

[igneous80]

Hi, I found same problem both Oauth and personal token.
I've check FFiii docker instance log and everything look fine, no error and server return correct responds.

My phone is Huawei P30 running on official EMUI12 and connect to FFIII docker (6.1.16) via cloudflare tunnel.

[SimonAkers]

If someone has the time, it could be worth trying a fresh instances of the latest development version. Since it works on the demo version which is in develop branch, it could be something that was fixed recently on Fiii's end. I've been meaning to look at this closer but work has had me slammed all week 🤦

[igneous80]

If someone has the time, it could be worth trying a fresh instances of the latest development version. Since it works on the demo version which is in develop branch, it could be something that was fixed recently on Fiii's end. I've been meaning to look at this closer but work has had me slammed all week 🤦

i've tried developer branch Version develop/2024-07-08 but still got white screen.

[victorbalssa]

If you don't mind my asking @victorbalssa, what brand Android are you using?

I have a Samsung Galaxy Tab S6 and a OnePlus both are working fine.

I will try to run it on a virtual device with android 14

[drewzeee]

I'm having the same issue, using a Samsung Galaxy S22+. FF3 v6.1.18 (latest).

I first noticed the issue a couple weeks ago after it starting saying "New update available!" in the app itself. Clicking "yes" to update would cause this issue regardless of if I cleared app data and setup credentials again. After authorization, you get a white screen and cannot use the app.

For a while, I was able to get past it by clicking "cancel" on the update notification (after resetting the app data), but now with the latest version of the app being pushed to the Google Play store on July 4th, there's no notification that pops up or workaround I've found.

Let me know if I can be of any extra help, would love to see this fixed so I can keep using the app!

I had the exact same experience, except on iOS.

[victorbalssa]

I'm building a sentry build to catch and get the error message. I will share the apk file for testing.

[victorbalssa]

It's available here: https://github.com/victorbalssa/abacus/releases/download/0.18.0/abacus-sentry-0.18.2.apk

If someone can try to install this update, I will have access to the error logs and will be able to debug this issue.

Thanks!

[SimonAkers]

If someone can try to install this update, I will have access to the error logs and will be able to debug this issue.

Done, I have installed it and tried logging in. You're a legend for the help!

[victorbalssa]

@SimonAkers for some reasons Sentry SDK wasn't initialize correctly on this version.

I double checked this new version 0.18.2: https://github.com/victorbalssa/abacus/releases/download/0.18.0/abacus-sentry-0.18.2.apk and I should work now (at least I should be able to see the error logs).

Thank you for testing this with me!

[SimonAkers]

@victorbalssa Got it! If it's easier to contact me directly, I have Discord (shayes)

[victorbalssa]

I got it! I will create a patch soon on production release.

[victorbalssa]

@SimonAkers @drewzeee @igneous80 @advait404

New 0.19.0 version available directly from OTA update with a fix for this.

[drewzeee]

@SimonAkers @drewzeee @igneous80 @advait404

New 0.19.0 version available directly from OTA update with a fix for this.

Confirmed working on iOS

[SimonAkers]

New 0.19.0 version available directly from OTA update with a fix for this.

Working on my Android! Thank you for the help 😁

[D4rkT1m0]

Hello guys, how to get the OTA version?

[D4rkT1m0]

I somehow succeed to update the app as I launched it, the app itself asked me to update which I did. It's working now.
But when I look in the App Store, the version is still at 18.0

[SimonAkers]

@D4rkT1m0 OTA means "over the air" and in this context means the update comes from the app directly, instead of from the app store. So the app store won't show the version from the OTA update. It sounds like you did update correctly!

[D4rkT1m0]

@SimonAkers

@D4rkT1m0 OTA means "over the air" and in this context means the update comes from the app directly, instead of from the app store. So the app store won't show the version from the OTA update. It sounds like you did update correctly!

Thanks for je fast reply.
How are we able to launch the OTA update?

Is this something we can interact with? Or do we simply have to wait that the creator make it available from his side?

[SimonAkers]

@D4rkT1m0 Is this something we can interact with? Or do we simply have to wait that the creator make it available from his side?

Oops, forgot to explain that, my bad! When an OTA update is available, that's when it says "New update" in the app itself on launch. You can choose "yes" to accept it and update. If I'm not mistaken you can also do it from the settings menu

[igneous80]

@SimonAkers @drewzeee @igneous80 @advait404

New 0.19.0 version available directly from OTA update with a fix for this.

@victorbalssa
After updated via OTA to 0.19.0, Abacus now back to work!

Thanks!

[gandalff512]

Thanks guys!

@victorbalssa
Thank you very much, I also have version 0.19.0 working!