Mobile - App crashes when syncing large resources (greated than 10MB) #371
Labels
bug
It's a bug
Comments
|
Does it happen every time at item 613? Were you on a particular screen when it happened? If it was just a one off thing normally you can resume the sync and it should pick up where it left off. |
|
It always happens on Item 613. Than the app crashed. If i restart the app, the sync starts again from beginning. I can't finish the sync. For the sync i open the menu after starting the app and then i press the sychronize button (left bottom of the screen). |
|
Unfortunately it's hard to know what's happening without log. Maybe could you try to connect your phone to your computer via USB, then open the Console and see if you get any stack trace in there when it crashes? You could try to search for "Joplin" to only see crashes relevant to this app. |
|
I am not sure how this should work technically with a iOS device? Can you please explain it in detail? |
|
Simply plug the phone to your macbook with a usb cable, then open the Console app in macOs. Then replicate the crash and it should log it in the Console. |
|
Actually could you simply send a crash report as described below? You can send to this address https://raw.githubusercontent.com/laurent22/joplin/master/Assets/Adresse.png https://developer.apple.com/library/content/qa/qa1747/_index.html Getting Crash Logs Directly From a Device Without Xcode Your users can retrieve crash reports from their device and send them to you via email by following these instructions. (It is not possible to get device console logs directly from a device)
|
|
First the log from the console application (i replace my domain name with example.com): |
|
In the iOS crash data i have only one Joplin crash log from 2018-02-08 (called Joplin-2018-02-08-170251.ips): |
|
Thanks for posting the report. It's crashing because it's running out of memory during the sync. I will check if there's a memory leak somewhere. |
|
If you look at the items in Nextcloud (both the .md files and the files in the ".resources" folder), are there any particularly large file? What would be the biggest file in there? |
|
The biggest markdown file is 188 KB. The biggest resource file is 80 MB. |
|
As a temporary fix I would suggest deleting the 80MB file and associated .md file (they have the same name) as it's probably what's it's crashing on. I see there are also time out issues when uploading large resources so I guess it's not properly supported at the moment. |
|
I found the cause for this crash but as of now it doesn't seem to be fixable. The built-in React Native API is too new and doesn't have the required features, and the module I use is buggy. I will revisit in a few weeks if either RN or the module are updated and fixed. |
laurent22
added a commit
that referenced
this issue
May 3, 2018
laurent22
changed the title
|
Will fix when possible. |
|
An update to keep track of what's been tried:
|
|
Thanks for checking this up regularly. Switching over from OneNote with extensive notebooks this attachment issue is of vital importance for me. Could you please tell us @laurent22 if there is any hope for a solution in prospect at the moment? |
|
Unfortunately the module I'm using was abandoned, then it was taken over by a company, who proceeded to abandon it too. I'm going to check if there's some alternative as things change fast in RN world. |
|
Much appreciated! There are so many attachments/resources exceeding the 10 MB limit in my notebooks that it is practically impossible for me to switch before there is (even a slight hope of) a solution, unfortunately. |
|
@laurent22 Why was this issue closed? Is there a duplicate issue? Or is there a solution for it? |
|
@mblennegard if you follow the link to the commit that closed it, you get your answers. tldr; sync of large files works on desktop now, but not on mobile. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Operating system
Application
I have imported a bunch of notes from Evernote into Joplin (Windows-Version) and sync them per Nextcloud to another Joplin-Instance (Mac Version). That works without problems.
If i sync these to the iOS-Version of Joplin, the sync startet and on 613 from 1000 objects the client creates a new local object and the application closed unexpected and instantly without a message.
There are no warning in the debug protocol, the last entries are (the crash is at 11:56):
The text was updated successfully, but these errors were encountered: