-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Empty response for async bytes #646
Comments
Platform+Version: iOS 15.x, 16.2 I think this is an issue specific to iOS 16 with capturing the response body when using the new async interface methods of URLSession introduced in iOS 15's Foundation updates. (Not just bytes, I see it with data as well) I am experiencing the same behavior only when using the new async interface for URLSession, specifically In the iOS 16.2 simulator, FLEX behaves exactly as shown above in @flejmer 's post. The response body shows as empty and it shows as "Awaiting Response" in the list of requests even after the app has received and process data from this call. The exact same code in an iOS 15.0 simulator does show responses in FLEX. |
I can confirm the same issue on my side. |
Hey! An example project would be really helpful if someone can make one :) |
I can also confirm this issue. I use standard |
I took a quick stab at a demo project for this bug: https://github.com/brianplattenburg-delta/FLEXAsyncEmptyDemo |
Is there any progress for this issue? |
I had the same issue, empty response |
Is there any progress on this issue? |
I have the same issue |
Hi all, I took a stab at investigating this. I think the issue is that At the moment, it would require more work than I can spare to figure this one out. It will possibly involve hooking a Swift function, which is a delicate process. If anyone knowledgable with this sort of thing can help or offer any insight, it would be much appreciated! |
Environment
Bug Report
I checked the FLEX networking debugger and requests that I make appear with empty response. That is not correct since I'm getting the data that is displayed on the app. I looked into similar issues mentioned in #603 and #611 but I'm not using firebase so it's not related.
I do networking using concurrency so perhaps that could be part of an issue with FLEX.
URLSession
withbytes(for request: URLRequest, delegate: URLSessionTaskDelegate?)
to be specific.Mechanism in network history is listed as
The text was updated successfully, but these errors were encountered: