-
Notifications
You must be signed in to change notification settings - Fork 11
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
NSException * "executeFetchRequest:error: A fetch request must have an entity." #21
Comments
Can you please share with us the crash stack trace? |
10.11.1 Via PODS |
I've done everything I can, just going to commit out the use of Instabug to get my app running again. |
Did ya'll go to bed on me here. |
@gunyduny while our SDK goes through very intense testing before any release, we have tried again using our existing integrations but this is not reproducible at all on our end. Can you provide us with a scenario for reproducing this or a project that reproduces this issue? |
Still doesn;t answer the question why am I getting these errors. Scerario, is when I had the Instabug.start() it crashes 10 seconds later. with the above error. When I remove the Instabug.start(), my app works fine.. |
So i downgraded to a more stable version 10.1.2 and it works fine for me. SO the issue has to 10.11.1 |
Thanks for the scenario, however we tested more complex scenarios with no luck. We are suspecting that you are getting an incomplete Instabug framework, to make sure this is the problem and help both of us spot the difference in your setup and the root cause of the issue, please try to use this sample project to reproduce the crash. The project can be found here: https://drive.google.com/file/d/1Zf_aofFNQ1fII-MG4Tnm7rNChYDt8ekd/view |
Nothing but issues. Deleted App, cleaned App, nothing. Worked before you updated.
Installed both Via Coca Pods and Swift Package, nothing but crashes.
Happens when I initiate Instabug
I comment out the above, my app works.
web.instaBug() & web.instaBugBeta() are just references to my KEYs.
The text was updated successfully, but these errors were encountered: