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

App is crashing when writing posts on iPhone #940

Closed
1 task done
WhereCanI opened this issue Feb 12, 2023 · 2 comments
Closed
1 task done

App is crashing when writing posts on iPhone #940

WhereCanI opened this issue Feb 12, 2023 · 2 comments
Milestone

Comments

@WhereCanI
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When you are writing a new update-adding a post in the iOS app, it will crash once you have written approx. 100-150 characters. First the app gets stuck and then it crashes.

Expected Behavior

No response

Steps To Reproduce

  1. Add a new post in the app.
  2. Write a story, and once you reach 100-150 characters the app will get stuck and eventually crash.

Environment

- Device: iPhone SE2
- OS: 16.3
- Version:
- Build:

Anything else?

No response

@j-f1
Copy link
Contributor

j-f1 commented Feb 12, 2023

Duplicate of #705 — I’ve never been able to reproduce this myself so I haven’t been able to find a real fix but I did open #932 in an attempt to make the issue less severe.

@SinghDominik
Copy link

Duplicate of #705 — I’ve never been able to reproduce this myself so I haven’t been able to find a real fix but I did open #932 in an attempt to make the issue less severe.

I don't know if it is really a duplicate as it literally crashs instead of just hanging. And it has nothing to do with an amount of chars because it happens at all char amount ranges.

zeitschlag added a commit that referenced this issue Feb 19, 2023
This is more of a guess to fix a crash, but it's not guaranteed, that it fixes the bug. When posting a new status, the app crashed occasionally when `try save()` in NSManagedObjectContext.swift. It seemed that the instance of NSManagedObjectContext just ... disappeared? The error-message was: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)

So, instead of async black magic fuckery, just ... wait until it's done?
zeitschlag added a commit that referenced this issue Feb 19, 2023
zeitschlag added a commit that referenced this issue Feb 20, 2023
Due to some audio-based debugging this could be identified as the place where the managedObjectContext disappeared. The idea is now: when we wait Core Data to finish its job, there's no way that a managedObjectContext in another thread can go south.
zeitschlag added a commit that referenced this issue Feb 20, 2023
zeitschlag added a commit that referenced this issue Feb 25, 2023
@zeitschlag zeitschlag added this to the 1.4.12 milestone Feb 25, 2023
zeitschlag added a commit that referenced this issue Feb 25, 2023
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

4 participants