Closed colin-marshall closed 7 years ago
This crash is a symptom of the exception thrown with the bug in issue #5 . The library was not initializing properly, and when trying to access library data stored in Sets the library manager would explode. Along with #5 this issue should now be resolved.
There are likely still issues with Core Data generated accessors lurking around. I'll take some time in the next couple days to root them out and perhaps just rewrite all of the set-related accessors myself. I am about to upload a build incorporating all of these fixes.
Thanks for the reports.
Here's the report. I should note that my library is currently empty so that may be the cause of it, but it should still not crash under those circumstances.