Jeff Ward

Hey @dballance Thanks for all the excellent info. My guess here as to the source of your race condition is the wait on the platform channel to perform its operations...

Hi @RustamG , Adding official support still on my radar, but I was under the impression that `attachToExisting` was a usable workaround, and `BackgroundIsolateBinaryMessenger.ensureInitialized` should have initialized the BinaryMessenger to...

Hey @RustamG , Yes that's the main issue -- I'm curious why @dballance didn't run into it. In reality, we should not attempt to set the callback handlers in background...

@dballance Did you update to the newest version includes [this pr](https://github.com/DataDog/dd-sdk-flutter/pull/626)?

@dballance Keep me posted. If it turns out it's unrelated to background isolates (either related to multiple engines or something else entirely) let's open a separate ticket for better tracking.

Hi @toussam, So I can be clear on what you're expecting -- for a global attribute added through `DatadogSdk.instance.rum?.addAttribute`, you're expecting a view to have the value of the attribute...

Yes, the behavior you were seeing was expected. Attributes are considered a stateful property of the view, so changing them updates the property in the view. However, we do capture...

@toussam Following up on this -- The original bug is as designed, but I'd still like to make sure `startView` is working as expected on iOS. Do you have an...

Hi @toussam, Thanks for doing the legwork here. I'll take a look into it. If the platforms are not behaving the same that is definitely a bug I want to...

@toussam Is it possible you're sending multiple `startView` events with the same name? From an initial investigation, I think it's possible that iOS isn't reporting the new view if it...