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
I utilized the leak instrument and detected the memory leak originating from the function adapt in the file RequestInterceptor.swift. In fact, this function failed to add a weak reference in its closure.
What did you expect to happen?
I expected to add weak or unowned into the adapt function's closure, as this would prevent the memory leak from occurring.
What happened instead?
It still retained the reference that caused the memory leak.
Can you provide an example project that reproduces this leak? There really shouldn't be a leak here, as all of the captures should be released once the nested adapt calls are complete.
What did you do?
I utilized the leak instrument and detected the memory leak originating from the function
adapt
in the fileRequestInterceptor.swift
. In fact, this function failed to add a weak reference in its closure.What did you expect to happen?
I expected to add weak or unowned into the
adapt
function's closure, as this would prevent the memory leak from occurring.What happened instead?
It still retained the reference that caused the memory leak.
Alamofire Environment
Alamofire Version: 5.7.1
Dependency Manager: SPM
Xcode Version: 14.3.1 (14E300c)
Swift Version: 5
Platform(s) Running Alamofire: iOS Simulator
macOS Version Running Xcode: 13.5.1 Ventura
The text was updated successfully, but these errors were encountered: