-
Notifications
You must be signed in to change notification settings - Fork 734
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
Publisher crash in 1.1 #2932
Comments
@calvincestari Any initial thoughts on what could be causing this? If not, lets start putting together a reproduction case! |
Hmm. I don't have any idea what could be the cause right now, we'll need to get a reproduction case so we can properly debug it.
We had to jump through a few hoops with the interceptor chain to introduce the multipart subscriptions in a way that wasn't breaking for existing users; the description of #2870 describes the implementation details of that. I don't think anything changed about the |
Hi @yonaskolb, we've got a fix up on branch |
Yes, this seems to fix the error in our case, thank you! 🙏 |
Just coming here because we were getting similar crash but while using the new Swift concurrency APIs. In our case, we had a wrapper around the provided
The app was crashing at
The issue was due to NSLock being sent a message after being deallocated. Pointing to this branch alone fixed it. Hope this helps someone else too. |
Hi @mariano-mix 👋🏻 - as you've verified, PR #2943 should resolve that issue too since the |
Thanks for the confirmation too @yonaskolb. I'll get the PR merged and |
were seeing something similar on our end with RxSwift |
@BrentMifsud the fix is merged into |
ill try it out |
can confirm this fixes the issue. |
OK, thanks for confirming. It'll be included with |
Just a heads up, one thing I just noticed is that the Not sure if thats related to any of the changes, or if its just Xcode being Xcode. Edit: this is probably a false alarm. I just switched back to 1.1.1 and it's still not there. Probably just an Xcode 14.3 bug. |
Yup, we're tracking that in #2919 for now. |
Summary
I don't have too many details, but we're seeing a crash in our Combine Publisher integration with Apollo in 1.1.0. It's based off this code /~https://github.com/joel-perry/ApolloCombine
Not really sure what's going on yet, but thought I'd open this issue early.
A colleague shared this image where the errors array was completely filled with the same error, but don't know if the debugger is acting up as I didn't see that 🤷♂️
My best guess is that something changed in a breaking way in the multipart subscriptions work, but that's a total guess. #2870
Version
1.1.0
Steps to reproduce the behavior
Logs
Anything else?
Our Apollo Publisher code if something sticks out as incorrect when integrating with Apollo 1.1
The text was updated successfully, but these errors were encountered: