I see it initializing & can even do TelemetryManager.isInitialized checks before/after the process, yet sending any outgoing signal fails to actually send.
I thought perhaps server issues, etc, but after making another "Test app" via TD's web interface, using that App-ID, injecting it into a simple SwiftUI-based app &/or CURL request, I see both of those methods working.
This is running in production fine, ~which leads me to believe this is a newer-OS bug? I'm running Sonoma 14.1.1.~ this can't be, as I'm getting signals from the v1.0 of my app's code, etc, reporting 14.1x. 🤔
I also saw #319's HSTS in some logs.
Is there anyway I can better debug this? See how many signals are stuck in a cache, etc?
For some reason, I'm not able to send signals? This was a sudden change. I tried versions
1.4.4
,1.2.0
, & the latest1.5.0
of the TD Swift Client.Using this code (or at another convenient location):
I see it initializing & can even do
TelemetryManager.isInitialized
checks before/after the process, yet sending any outgoing signal fails to actually send.I thought perhaps server issues, etc, but after making another "Test app" via TD's web interface, using that App-ID, injecting it into a simple SwiftUI-based app &/or CURL request, I see both of those methods working.
This is running in production fine, ~which leads me to believe this is a newer-OS bug? I'm running Sonoma 14.1.1.~ this can't be, as I'm getting signals from the v1.0 of my app's code, etc, reporting 14.1x. 🤔
I also saw #319's
HSTS
in some logs.Is there anyway I can better debug this? See how many signals are stuck in a cache, etc?