-
Notifications
You must be signed in to change notification settings - Fork 348
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
getData EXC_BAD_ACCESS #63
Comments
Thanks for reporting. I have not seen this one before. Is it crashing consistently, can you reproduce the problem? If so, could you isolate this bug into a demo app and post here please, so I can try and debug it? I googled the error text and found this stackoverflow discussion. They suggested changing deployment target. Not sure if that's relevant to your case. |
It’s not every time, but it does happen frequently. I’ll get a sample project together using the same type data that is stored. I’m also going to make sure it is not an iOS 11 bug
|
A sample project would be great, thank you. |
This is happening to me many times when I try to use getData into an Operation.
KeychainSwift.swift line 169 And this is what I see in the console: |
This was probably fixed by this pull request. |
I am having the same problem with the last version and i am using iOS 11. |
This happens to me as well. Here's the relevant info from the crashed thread:
Error is:
|
@RamblinWreck77, @MouldiGABSI, thanks for reporting. There was a multithreading issue fixed since version 10 of the library. Make sure you are at version 10 at least. |
@evgenyneu My Apologies, I didn't mention the version. This is on v11.0.0 |
I'm encountering this crash with v11.0.0 on iOS 11. I noticed:
|
Any solutions? |
Using the getData method, I am getting a random EXC_BAD_ACCESS on the lastQueryParameters = query line.
malloc: *** error for object 0x61800045c31e: Invalid pointer dequeued from free list
Here is the error from the console. I'm not sure if this is related to #15 or not? Thanks for your help. Let me know if you need more information.
The text was updated successfully, but these errors were encountered: