iOS Issues - RUM Events Not Population about dd-sdk-flutter HOT 7 CLOSED

Is there something that I'm missing in the setup here? If I had to guess, I would say that there is something being triggered incorrectly on the iOS side with the await DatadogSdk.instance.rum?.initialize(); function.

from dd-sdk-flutter.

Hi @mikhael28,

If you remove the event mappers, does iOS report properly?

I have a feeling Flutter got stricter about what threads can call into method channels. We may be incorrectly calling the mappers from off the main thread, and while I think Flutter may have always had the requirement that you should only call the method channel from the main thread, it didn't actually prevent it until recently.

If removing the mappers fixes the issue let me know and I'll get a fix out for them ASAP.

from dd-sdk-flutter.

I just ran my integration test for the mappers and they still pass, so unfortunately that's probably not your issue (something I still intend to fix, just not what's causing this). I would remove the mappers for now anyway, unless you need them for something.

You also shouldn't need to call DdRum.initialize manually. It's called automatically by DatadogSdk.initialize if a rumConfiguration is present. Since this actually sets up the mapper method channel, there's a possibility that's partially causing the issue. Can you try removing it and see if that helps?

I'll add some protections to make sure double calling that issues a warning and mark the method as internal.

from dd-sdk-flutter.

Hey @fuzzybinary good news - the issue was only showing up in the local dev test, even with the mappers. When deploying to prod, it reports the RUM events as expected. Well, good news / bad news I guess. All in all, things are working which is good, but the situation seems brittle.

from dd-sdk-flutter.

I will be looking forward to the 2.0 release - will update this ticket at that time with anything else I've found, and hopefully be able to close this out. Updated the name of the ticket.

from dd-sdk-flutter.

@mikhael28 That's great to hear. This may be a significant enough issue I'm going to back port it to 1.x, but I won't put it at p0 for the time being.

from dd-sdk-flutter.

This should now be now fixed in v2.0

from dd-sdk-flutter.