Closed nashfive closed 2 years ago
Metrics may fire after URLSession:task:didCompleteWithError:
is called, the delegate may be nil, so it may cause the error.
I've centralized the way HTTPMetrics
object is created for a response so it may solve the issue.
Have you tried to reproduce the issue?
@malcommac thanks for your feedback! Unfortunately I can't reproduce it.. The trace is from Sentry and it has been triggered somehow by one of our users.. I couldn't reproduce or trigger any crash during development and testing... but nothing beats real-usage made by daily users apparently...
I'm inviting you to try 1.7 when it will be out. I'll check in our products too but I'm confident it's gone with the latest changes. Thank you again for your feedback!
Thanks @malcommac I'll upgrade to 1.7 as soon as it's available and will report back if the problem still arises
@malcommac do you have an ETA for the 1.7 release? Should I switch to the main
branch in the meantime so my users can benefit from the fix ?
Hi! We'll release 1.7 the upcoming week. After the release we also plan to move the HTTPStubber as separate package too.
released
Bug Report
Summary
It seems that there is still something going on with HTTPMetrics in the 1.5.2 version. I can't reproduce it since I don't really know what's going on, but our crash report shows a considerable amount of these issues...
FYI, we use the Sentry and NewRelic SDKs and I am not sure if they could interfere with RealHTTP somehow 🤔