Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash while using MR_findAllSortedBy:ascending:withPredicate:inContext #1307

Open
adibuildup opened this issue Jun 4, 2017 · 0 comments
Open

Comments

@adibuildup
Copy link

Hi,

We integrated Magical Record to our app a few month ago, and we encountered a few issues:

  1. when we open the app we want to update the core data in the background, but let the user use the app and not disable the UI completely, The problem is the ui get stuck when we do saveWithBlock, I read that if you don't use with completion it should be faster, but then duplicate entities appear. so we use saveWithBlock with completion, but the UI get stuck, especially if the battery is low.

  2. we get a lot of crashes from magical record, that we can't reproduce or understand why they only happen sometimes to some of our users, most of the crashes came from this code:

__67+[NSManagedObject(MagicalRecord) MR_executeFetchRequest:inContext:]_block_invoke (in Buildup) (NSManagedObject+MagicalRecord.m:54)

after we are trying to use sort method:

+[NSManagedObject(MagicalFinders) MR_findAllSortedBy:ascending:withPredicate:inContext:] (in Buildup) (NSManagedObject+MagicalFinders.m:56)

do you have any idea what can cause it? we added try and catch but the app still crashes, and I can't understand why it works most of the times but happen every now and then.

*those crashes/problem happen with the newest XCode version and iOS 10.1.1 and above
** we use version 2.3.2 of Magical record (I think that's the newest)

let me know if you need any more information ...Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant