Maciek Grzybowski

Hello @JetForMe @odaeagle 👋. We've been discussing this in the team and unfortunately this isn't something we're considering for close future as it seems very specific. Today, `env` can be...

Hello everyone 👋. In version [**2.7.0**](https://github.com/DataDog/dd-sdk-ios/releases/tag/2.7.0), we introduced the `stopInstance()` method, which can be leveraged to restart the SDK with a new configuration. This can be particularly useful in internal...

🚀 @shagedorn We're happy to hear that this approach works for your use case! For that reason, I'll go ahead and close this issue (feel free to still add comments...

👋 Hey all! We're actively working on tracking this issue ☝️. Unfortunately, we couldn't manage to reproduce it locally and our efforts lead to conclusion that this might be occurring...

Hello @leearmstrong 👋. So far we collected ~1K samples from our dogfood projects (mainly our iOS app in beta channel). None of ~3.7K resolved IPs led to local network connection...

Hey @eseay 👋. Although we haven't manage to reproduce this issue (also with VPN as pointed out by @leearmstrong), recently we got one hit in telemetry we collect in our...

Closing - fixed in [`1.11.0`](https://github.com/DataDog/dd-sdk-ios/releases/tag/1.11.0). Thanks to everyone who helped nailing this problem 🍻🙂. We hope it's ultimately gone.

Hello 👋🥲 thanks for reports folks. There are two things that come to my mind for now: * The [private IP check](https://github.com/DataDog/dd-sdk-ios/blob/ef343b1781218392790bd7085fad4b27628ea44b/Sources/Datadog/Kronos/KronosInternetAddress.swift#L46-L90) we added in #830 is too weak and...

> Yes, we are 100% sure this is caused by Datadog SDK, because the app release we did only contained the SDK implementation and network permission prompt reports started on...

@victor-yn thanks a lot! It's great data - I will analyse it tomorrow. To clairfy - do you have a device at your dosposal that reproduces this problem easily 😲?...