App crashes after setting Recipe Directory #4

Closed
opened 1 year ago by kaffeepalme · 7 comments

As stated in the title, the app crashes after I set the recipe directory and click on the back arrow.
Also, when I try to open the app again, it crashes instead of opening.

As directory path I've set /storage/emulated/0/Android/media/com.nextcloud.client/nextcloud/[my account]/Recipes

Any idea why this is happening?

Thanks for creating the app!

Versions
NC Cookbook App 0.30.0
Android 9
Nextcloud 19

As stated in the title, the app crashes after I set the recipe directory and click on the back arrow. Also, when I try to open the app again, it crashes instead of opening. As directory path I've set `/storage/emulated/0/Android/media/com.nextcloud.client/nextcloud/[my account]/Recipes` Any idea why this is happening? Thanks for creating the app! **Versions** NC Cookbook App 0.30.0 Android 9 Nextcloud 19
Owner

Did you give the permission to access the storage?
You can see the permission in the device settings / apps / Nextcloud Cookbook / Permissions.
The app needs storage access.

Second idea: Have you synchronized the folder Recipes (in Nextcloud App showing a green arrow)? The files must be on the local storage.

I can look, if I handle errors wrong. A crash is the wrong behaviour to errors in the app.

Did you give the permission to access the storage? You can see the permission in the device settings / apps / Nextcloud Cookbook / Permissions. The app needs storage access. Second idea: Have you synchronized the folder Recipes (in Nextcloud App showing a green arrow)? The files must be on the local storage. I can look, if I handle errors wrong. A crash is the wrong behaviour to errors in the app.
MicMun self-assigned this 1 year ago
Poster

Yes, the app has permisssion to access the storage and the Recipes folder is synchronized.

When I try to open the app it crashes after half a second or so, in the header bar it says "fragment_reci..." and the body stays blank. May that helps!

Yes, the app has permisssion to access the storage and the Recipes folder is synchronized. When I try to open the app it crashes after half a second or so, in the header bar it says "fragment_reci..." and the body stays blank. May that helps!
MicMun added the
bug
label 1 year ago
Owner

I try to find the bug, but before tomorrow evening I don't have the time.

Have you technical knowledge about the adb tool?
With the messages in adb logcat ((eg. Exceptions) it would be easier to find.

I try to find the bug, but before tomorrow evening I don't have the time. Have you technical knowledge about the *adb* tool? With the messages in *adb logcat* ((eg. Exceptions) it would be easier to find.
Poster

Great, thank you! Take your time.

I never really did something with adb but I managed to use adb logcat.
This is the output, when I try to start the app:

Great, thank you! Take your time. I never really did something with *adb* but I managed to use *adb logcat*. This is the output, when I try to start the app:
Owner

Thats great. I see the problem, its the json parsing.
There is minimum one recipe with a publish date and that is a problem for the parser.
Now I can fix this, thanks a lot for the adb logcat.

Thats great. I see the problem, its the json parsing. There is minimum one recipe with a publish date and that is a problem for the parser. Now I can fix this, thanks a lot for the *adb logcat*.
MicMun added this to the 0.40.0 milestone 1 year ago
Owner

If its possible to edit the json files: Remove the blank and the time from the field "datePublished", then the app works.
This workaround is only short needed, because the fix is planned for the weekend.

If its possible to edit the json files: Remove the blank and the time from the field "*datePublished*", then the app works. This workaround is only short needed, because the fix is planned for the weekend.
MicMun referenced this issue from a commit 1 year ago
MicMun closed this issue 1 year ago
Poster

Thank you, the app works for me now!

Thank you, the app works for me now!
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.