Re: Crash on account addition
Hi coders!
After the steps of filling in baseURL, username and password one is prompted for the final account name (called email?!) and in this step the app crashes. This does not happen with the same account data in 2.4.0.1 so this is a regression. When then restarting the app, the account seems to exist but is nonfunctional. The account created looks fine but when pressing the sync button there are not even any IP packets sent to the server in question. There is no error message neither.
There is nothing about the account in the debug info nor does the “verbose logging” option give any more logs.
The baseURL of the account can not be checked or changed after that the account is created (only username and password). This limits the ability to check how the app is configured considerably.
- Your regression testing is lacking
- Your error handing towards the user is lacking
- Your config options are lacking
The last two are probably in the name of making it easy for the user but while simple is good, oversimplifiction is bad.
When the username is part of the URL (which is not a requirement as I see it) it may be possible to create a working account with 2.5. When using shared calenders (baseURL something like https://server:port/shared/) the username is not part of the URL. If there are constraints on the baseURL, then there should be an error message if these are not met.
My guess for the cause would be a null pointer derefernce due to sloppy coding and then saving an empty baseURL into the config.
Server: Radicale 2.1.8 (but as said, not even contacted)
Android version 6.0.1 LTE_D0201121.0_S60_0.038.00
Device: BullitGroupLimited S60 (CatS60)
In hope that this helps you to make a better app and regards,
Harald.