IOS App Bug On Initial Connection

[lecramr]

Describe the bug
On initial App Launch after typing in the Server Url, you get directed to the login screen, where I tried to login with my credentials (maybe the Server Url was wrong or at least the Protocol, because the the text in the banner only stated “connecting” no success message), however the login was not working, after afterwards closing the app, it hangs on the splash screen forever, even after uninstall, or uninstall and reboot, I can not get it working. Issue appeared on iPhone and iPad.

To Reproduce
Steps to reproduce the behavior:

1. Fresh install App
2. Type in Server Url (maybe wrong http protocol) (using paperless ngx)
3. Try to login
4. Force close App
5. Restart App

Expected behavior
Working Login, or at least Error Handling of maybe wrong Server Url to try again.

Screenshots
Splash screen

Additional information
Paperless App Version: Newest in App Store
Do you use Paperless NG as a backend: Paperless NGX

Currently on mobile that’s why the short description. If additional info is needed feel free, I’ll glad to respond.

[thiemo]

Probably related to this breaking change in the API of paperless-ngx 1.11.3
paperless-ngx/paperless-ngx#2279

[lecramr]

Are you sure? I am nowhere near that Endpoint. As described, the Issue occurs after Initial Setup / Login, I haven't even seen the UI. I installed TestFlight, same issue there, but maybe now a protocol is shared on the issue.

[gras64]

I have the same problem on first login. try with Android and Iphone. if i delete app data in android i can try it but same problem. iphone save app data. i use a new docker image.

[gras64]

the app scan4paperless is working and first login without problems. i am a new user.

[lecramr]

Issue still persists even with new TestFlight Version. A workaround would be, to implement a Settings Entry to delete Settings & Cache of the App?

[lecramr]

https://www.youtube.com/watch?v=_1ZHTSaQ-zc

https://github.com/bauerj/paperless_app/blob/master/lib/routes/home_route.dart

Found the Issue, the stored Credentials in the Keychain (which survives a App Delete) are somehow throwing errors. Maybe directly fix this invalid character Error or just enable us to wipe the keychain data from a settings menu.