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
Assertion Failure when using file URLs #47
Comments
Thanks for opening this issue. I'm looking at it and remove it as possible 👍 |
Hey @kenjitayama, Can you share with us:
I tried to reproduce but it's working fine (Proxyman 2.15.1, iOS 14 and Atlantis 1.4.3) let url = URL(string: "https://proxyman.io/img/background/proxyman-dashboard-home.png")!
let task = URLSession.shared.downloadTask(with: url)
task.resume() let url = URL(string: "https://proxyman.io/img/background/proxyman-dashboard-home.png")!
let task = URLSession.shared.downloadTask(with: url) { (_, response, error) in
if let error = error {
print(error)
return
}
if let response = response as? HTTPURLResponse {
print(response)
}
}
task.resume() Both URLSessionDownloadTasks are still working |
One more thing, when the The easier way is that you set the breakpoint at |
@NghiaTranUIT Thanks for checking the issue!!
I am using iOS 14.0 and Atlantis 1.4.3.
Did this when assertionFailure occured (I changed the app name in the URL):
You need to use a |
Thanks. I'm able to reproduce this bug. Fixing now 👍 |
@kenjitayama please check out the 1.5.0 version, which I've released (https://github.com/ProxymanApp/atlantis/releases/tag/1.5.0) It fixes your problem 👍 Thank you and Merry Christmas 🎉 |
@NghiaTranUIT Thanks for the quick fix! |
Glad to know it works 🎉 |
I get this assertion failure when using file URLs.
It can be reproduced with this code in an iOS app.
In our app, many resources are retrieved from a web server, while some are bundled in the app.
For a specific kind of resource, we want to use the same implementation for web and bundled file, which uses URLSessionDownloadTask.
It would be helpful if this assertionFailure is removed.
The text was updated successfully, but these errors were encountered: