Mobile app crashes in LinageOS

Hello,

I m using joplin’s mobile app in Android actually on my Cell and the tablet, and it is working Great.

On both devices is 1.0.312 installed.
The Cell is an old Samsung S4a with Android 5.0.1, tablet is a newer one samsung S5e running in Android 9.

Now i m heading to a younger cellphone , a Samsung S7 Exynos with Android 8.1 and 9 /LineageOS (i grabbed two old businessphones)

I’ve tried the 1.0.319 First, then the known as running version 1.0.312.

On both S7 the app crashes when synching with my Nextcloud.

Where is my mistake?

Cheers,

Gerry

We need the crash log http://joplinapp.org/debugging

This is android 8.1

bugreport-heroltexx-OPM7.181205.001-2020-05-02-14-38-24.zip (1.7 MB)

Android 9
bugreport-heroltexx-PQ3A.190801.002-2020-05-02-13-21-46.zip (2.1 MB)

Another OutOfMemoryError, it seems

05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: Process: net.cozic.joplin, PID: 10799
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: java.lang.RuntimeException: Could not invoke FileReaderModule.readAsText
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:383)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:158)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:873)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:99)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:193)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:232)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:764)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: Caused by: java.lang.reflect.InvocationTargetException
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	... 8 more
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: Caused by: java.lang.OutOfMemoryError: Failed to allocate a 287129096 byte allocation with 8388608 free bytes and 75MB until OOM, max allowed footprint 465913992, growth limit 536870912
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at java.lang.StringFactory.newStringFromBytes(StringFactory.java:225)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at java.lang.StringFactory.newStringFromBytes(StringFactory.java:65)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	at com.facebook.react.modules.blob.FileReaderModule.readAsText(FileReaderModule.java:53)
05-02 11:02:28.295 10107 10799 10839 E AndroidRuntime: 	... 10 more
05-02 11:02:28.304  1000  3647  6243 W ActivityManager:   Force finishing activity net.cozic.joplin/.MainActivity

Do you have any large attachments?

Hi,
i don’t have any attachments.
Actually joplin is syncing three buying lists.
Just textfiles with Variable lines.

Edit:
The Appinfo on the Tab tells me Data -1,7 MB.

Thank you guys,

the Hint to large Files made my day.

To be honest-IT was a brainbug…
I’ve struggeld with the subdirectories.
Doing some testing witb an other webdav client Shows my mistake.

Many thanks for helping me .

BR Gerry

Just out of interest what was causing the issue?

It was the Problem of the directory.
As i installed joplin my nextcloud wasnt filled with files.
Over the time it became more and more, but joplin Shows only kompatible files, so i didnt recognize my problem, cause the other files Are hidden for me.

Now, with a frech install, the amount of files and filesize was to much.
Your hint to Big files was the Clue for me.

Now a new directory structure was Build, and syncing is possible.
At the beginning with Joplin i wasn't Sure, wether the app is creating a subdirectory At the replicationsite or not.
Now i know the not.
:slight_smile:

Typical problem of grown systems...

So again, thanks for your patience, and for the terrible up and lowercase caused by the German autocorrection From my Tab.

BR,

Gerry