If you donāt mind, uploading the video would definitely help. (Or if you prefer to do it privately, email to support@dynalist.io.)
If you donāt mind me asking, whatās the name of the document? As we hear from other people, the reloading issue has something to do with the size of the document.
Could you guys please uninstall and reinstall the app and see this issue goes away?
If it does, it might be related to the local session data not working correctly. Please uninstall only after making sure all local changes are synced, thanks!
Re-install is usually tried first to rule out the possibility that the cause of the problem lies in the local data, because in that case, itās nearly impossible for us to repro the issue on our end.
If that doesnāt work, with your permission, weād log into your account on our test device to see if the issue is reproducible. As long as we can make the issue happen on our test device, the rest of work is just to debug and fix the cause.
If we donāt get an account to test with, weāll generate huge documents locally and try to repro the issue with the information provided in this thread⦠Reproāing the issue is half the success!
Is there an update to this, please, @Erica? The app is still restarting on my iPhone after a reinstall and i canāt use Dynalist at all, even with a very small document itās restarting.
P.S. Iāve just reinstalled again to do more testing and even when I go to the file list and use the search function there, the app reloads/restarts even when Iām just typing a search term. You have my permission to use any of my data needed for testing as long as nothing gets deleted.
The cause of the issue is most likely a memory-related one. Although youāre opening a small document, all documents are loaded into memory for tag count, tag autocomplete, and Search Everywhere to work properly. When an app uses over 100 MB of memory, iOS kills the process and hence the reloading issue.
I can try identify which are the biggest documents in your account, and the issue should go away if you export them and then delete them. In the previous case we looked into, the person had a few full books and a copy of Bible in his Dynalist, which caused the out of memory issue.
This does not seem to be a scalable approach. After years of accumulation problem will impact more and more people. Interesting challenge, as the search function is vital, but may need incremental or otherwise managed search database or indexes (server side)?
I checked my documents for larger ones. I deleted PropƦdia which was something interesting, but I do not use it that often. Will monitor impact on IOS.
Yeah. Or not load the entire thing until global search is activated. Itās also a challenge that some people want global tag complete (tag autocomplete with suggestions from other documents) and cross-document link resolution
Another hope is that iOS will give us a way to get more memory. At least if the user decides to grant us more memory. Right now, as we understand it, our app gets assigned a certain amount of memory. The iOS system just wonāt give us more. Apps like Safari use memory though, which is why the web app runs a lot faster on Safari, for the same functionality.
Thanks!
Weāll always keep that document in demo. Feel free to copy it back whenever you want to play with it.