FLEXTool/FLEX

Empty response for async bytes

Open

#646 opened on Jan 12, 2023

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Objective-C (14,597 stars) (1,777 forks)batch import
bughelp wanted

Description

Environment

  • Platform+version: iOS 16.1.2
  • FLEX version: 5.22.10

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 with bytes(for request: URLRequest, delegate: URLSessionTaskDelegate?) to be specific.

Mechanism in network history is listed as

NSURLSessionDataTask (delegate: _TtC10FoundationP33_1935C07EE287982D980AA89BB85ACEFA28URLSessionAsyncBytesDelegate)

Contributor guide

Tech stack
objective ciosswift
Domain
mobiledeveloper experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
iOS developmentURLSessionFLEX usageasync/await
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the FLEX network recorder's handling of URLSession async/await methods, particularly the bytes(for:delegate:) API. Look at the mechanism identification code that detects delegate types and ensure response data capture works for the URLSessionAsyncBytesDelegate. Consider testing with a sample iOS app using async/await networking and verify that the response body is properly recorded. Reference similar issues #603 and #611 for prior context.