You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I've been working to integrate opentelemetry into our project which heavily uses GraphQL with the Apollo iOS package . It works great on iOS 16, but have run into frequent indefinite hangs or additional latency for iOS 17.0+. In particular their resultHandler here doesn't seem to be predictably called. Our app is currently built with Swift 5, Xcode 16.2, and SwiftUI and heavily uses async/await concurrency patterns.
I've done some debugging locally and pin pointed my particular issue to the use of assigning the FakeDelegatehere. If I either:
remove the delegate assignment
OR leave the assignment but just comment out the optional function declaration here
then my graphql network calls don't run into any issues and the resultHandler is predictably called (with no additional latency).
I'm wondering - if the FakeDelegate assignment (or the empty func urlSession(_ session: URLSession, task: URLSessionTask, didCompleteWithError error: Error?)) is still required or the original intent? Curious to learn more or understand what might be causing the issue.
Happy to follow up with any additional debugging info.
The text was updated successfully, but these errors were encountered:
Hi! I've been working to integrate opentelemetry into our project which heavily uses GraphQL with the Apollo iOS package . It works great on iOS 16, but have run into frequent indefinite hangs or additional latency for iOS 17.0+. In particular their resultHandler here doesn't seem to be predictably called. Our app is currently built with Swift 5, Xcode 16.2, and SwiftUI and heavily uses async/await concurrency patterns.
I've done some debugging locally and pin pointed my particular issue to the use of assigning the
FakeDelegate
here. If I either:then my graphql network calls don't run into any issues and the resultHandler is predictably called (with no additional latency).
I'm wondering - if the
FakeDelegate
assignment (or the emptyfunc urlSession(_ session: URLSession, task: URLSessionTask, didCompleteWithError error: Error?)
) is still required or the original intent? Curious to learn more or understand what might be causing the issue.Happy to follow up with any additional debugging info.
The text was updated successfully, but these errors were encountered: