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 had a problem with a Pi-Hole in my network. It was blocking traffic to the TelemetryDeck server. Even after disabling the Pi-Hole I was still blocked. My guess is that the URLSession.shared was caching the response for a while.
At least for testing/debugging purposes, I would suggest adding the optional ability to use a custom URLSession in SwiftSDKs SignalManager provided via TelemetryManagerConfiguration.
I had a problem with a Pi-Hole in my network. It was blocking traffic to the TelemetryDeck server. Even after disabling the Pi-Hole I was still blocked. My guess is that the
URLSession.shared
was caching the response for a while.At least for testing/debugging purposes, I would suggest adding the optional ability to use a custom URLSession in SwiftSDKs
SignalManager
provided viaTelemetryManagerConfiguration
.SwiftSDK/Sources/TelemetryDeck/Signals/SignalManager.swift
Line 234 in 359a1df
Thank you (also for the great communication via mail)!
The text was updated successfully, but these errors were encountered: