-
Notifications
You must be signed in to change notification settings - Fork 731
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 Thread 1: Fatal error: No data found for task 1, cannot append received data #3409
Comments
Interesting! I don't think we've ever had anyone hit this assertion failure before! It's possible there is a race condition going on here, but I would need more information in order to determine what's going on here. Are you using a custom |
Thanks for your response @AnthonyMDev
and our ApolloClientProxy class we added to perform some business needs but its simple
please advise is there any idea to help ? |
@KhaledElsherbeny is this a consistent crash? Is it reproducible? |
The cause of the assertion is that the internal task ( There are a number of ways the internal task data can be removed:
I recommend checking whether you call any of those methods in your own code. Also trying to nail down the circumstances of, and how reproducible, the error is would be helpful in tracking down the root cause. |
@KhaledElsherbeny were you ever able to resolve this one? We're going to need some more information on this in order to determine if there is a bug in our code and how to resolve it. We're closing this for now due to inactivity, but we will be happy to re-open if you respond with additional information. |
Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better. |
Summary
crash occurred randomly while starting calling query
Version
1.13.0
Steps to reproduce the behavior
crash occurred randomly while starting calling query
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: