Cihat Gündüz

Closing this in favor of https://github.com/TelemetryDeck/SwiftSDK/pull/195. Thanks again @davidrothera!

@Maschina Thank you for bringing this up. I'm happy to discuss the possibilities here. I had considered using the Observation framework from the start, but unfortunately it's not available on...

Closing user feedback like this without objective explanation _why_ is a really disappointing action that I didn't expect. "We're comfortable with (the current design)" is a really subjective explanation which...

Oh, sorry, I'm just seeing this right now. Have you tried your suggested change? Does it compile? I don't remember the exact details of why I implemented it this way,...

@joeljfischer Thank you for requesting this feature and sorry for getting back to you so late. I totally understand your use case and the need to delay the request. But...

@joeljfischer I do understand your point, I will think about that when iterating over this library again. But please note that my idea of making this call is not "after...

@DivineDominion Thank you for reporting this issue. Upon investigating it to find a good fix for it or improve the UX, I couldn't really understand the context of the issue...

@winsmith I just attempted to implement this task, but I failed. My main problem is the "they should query both fields" aspect. Because all the three mentioned insights are of...

We do have support for CocoaPods already, so I'm not sure why this task is open. But we [ran into another pipeline issue](https://github.com/TelemetryDeck/SwiftSDK/actions/runs/11132155601) with CocoaPods in release `2.4.0` and later....

@philliptharris It seems that we can't remove the CocoaPods deployment just yet due to our Flutter SDK depending on it, see https://github.com/TelemetryDeck/FlutterSDK/issues/21. But having that said, since we already have...