Background crashes

[tealshift]

Hi, I've been getting very frequent background crash reports from ParseOfflineDatastore

Termination Reason: Namespace SPRINGBOARD, Code 0xdead10cc Termination Description: SPRINGBOARD com.xxx.xxx was task-suspended with locked system files: | /var/mobile/Containers/Shared/.../ParseOfflineStore | ProcessVisibility: Background | ProcessState: Suspended Triggered by Thread: 0

My understanding is that Local Datastore has been basically a poorly supported, unscalable feature since it came out. (queries on 1000+ stored objects eats CPU like cotton candy) Source: http://rawrmaan.com/why-parse-failed/ <- section on Local Datastore -and I don't really expect this to get "fixed" soon.

However I wanted to post this here for future reference, if nothing else. I'm trying to see if there's anything I can do in my source code to stop the problem.

http://blog.supertop.co/post/152615019837/how-not-to-crash-1 This blog post explains that this crash code 0xdead10cc comes from an SQLite locked file at the time the app is suspended. Perhaps Parse SDK can proactively close Local Datastore (unlocking the SQLite file) before app suspension.

I would remove Local Datastore (by not enabling it) from my app, but doing so would require huge changes that I'd prefer not to do right now. Thank you, anyone reading this!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. If you believe it should stay open, please let us know! As always, we encourage contributions, check out the Contributing Guide

[TomWFox]

With there being no longtime maintainer on this SDK currently it’s unlikely this will get looked at anytime soon. If possible, it would be great if you could make a PR for this.

Although what with the underlying issues you’ve raised I wonder whether our time is better spent investing in the swift SDK which is in development.

[brianyyz]

@Tom-Fox1 which Swift SDK are you referring to? Would love to find out more about it!

[TomWFox]

@brianyyz The Parse-Swift repo. Unfortunately it's at a bit of a stand still at the moment as really the only maintainer was @flovilmart.

Although some people have expressed an interest of helping to continue development in #1356.

If you are able to help out in anyway I'm sure it would be hugely appreciated by the community, I think it would put Parse for iOS in a much healthier position as new devs learn swift first/only so are unlikely to contribute to an already outdated Objective-c SDK.

[drdaz]

... is there any documentation of what was happening with Parse-Swift? Or is it a matter of digging in and reverse-engineering his work?

[TomWFox]

@drdaz nothing to my knowledge (apart from any discussion in prs & issues)