-
Notifications
You must be signed in to change notification settings - Fork 491
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 with error: Thread 1: EXC_BAD_ACCESS (code=2, address=0x7fff86533e38) #226
Comments
Hey @vivek4292, thanks for reporting the issue. I'm unable to reproduce it, would you be able to provide a sample project demonstrating the crash? |
Hey, @ephread thanks for the response. I tried this in a separate project with the same environment and it is working fine. But it's still not working in my project. "error: Execution was interrupted, reason: EXC_BAD_ACCESS (code=1, address=0x6). The moment I released the breakpoint, the app got crashed on the same line (like the previous screenshot). |
This may be a trivial question, but how and where is |
@ephread Yeah it's a trivial question but I can understand in such case anyone can think of this possible reason. Agreed, it looks like an object is getting released soon. But the crash is still there. |
I had the same problem with a project I am working on, I solve it by moving the code that was causing the bug to the main queue since that code was directly related to UI. this was in Xcode 13. |
How do you move the code to main queue? where do I find the main queue? |
Describe the bug
When I was using 1.2.0 and Xcode 10.2 it was working fine. As I switched to Xcode 11.2 and 1.4.0 version of Instruction. I found a crash while assigning a delegate to CoachMarksController instance.
To Reproduce
Assign a delegate to an instance of CoachMarksController. In Xcode 11.2
Expected behavior
It should display coach mark views smoothly.
Screenshots
Environment:
The text was updated successfully, but these errors were encountered: