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
Alamofire should more gracefully handle system interference #3413
Labels
Comments
This was referenced Mar 1, 2021
Hi, is this problem solved or it is actual bug? |
It's an ongoing issue. Not really a bug, more of something Alamofire could detect and either workaround or warn about so users aren't surprised. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, Alamofire doesn't deal well when system frameworks or the Obj-C runtime interfere with
URLSession
orURLSessionTask
identity.These include:
URLProtocol
, as seen in Wormholy, assertionFailure - needNewBodyStream did not find UploadRequest #3373URLSession
swizzling, as seen in Splunk MINT and Crittercism, Creating NXProxy for URLSession which is creating issue in RequestMap monitor class #3238.These sort of issues may explain reports of crashes within
RequestTaskMap
where the task identity is changed under the hood.The text was updated successfully, but these errors were encountered: