DataDog / dd-sdk-flutter

Flutter bindings and tools for utilizing Datadog Mobile SDKs
Apache License 2.0
43 stars 42 forks source link

[Web] RUM stopped working on 16-05-2024 #616

Closed Arthurius closed 4 months ago

Arthurius commented 4 months ago

Describe the bug

For all our products running on Flutter web (4 different projects), all sessions stopped coming in.

Screenshot 2024-05-24 at 10 17 01

I do see a new error popping up in the browser console:

Screenshot 2024-05-24 at 10 10 41

Reproduction steps

Just look at the session explorer for any Flutter app running on web.

SDK logs

No response

Expected behavior

No response

Affected SDK versions

2.4.0 and 2.5.0

Latest working SDK version

No response

Did you confirm if the latest SDK version fixes the bug?

Yes

Flutter Version

3.19.6

Setup Type

No response

Device Information

No response

Other relevant information

Everything has been working for months. It stopped working for all our products on the same data, without any deployments or changes from our side.

Arthurius commented 4 months ago

Interesting find: when I change

  <script type="text/javascript" src="https://www.datadoghq-browser-agent.com/us1/v5/datadog-logs.js"></script>
  <script type="text/javascript" src="https://www.datadoghq-browser-agent.com/us1/v5/datadog-rum-slim.js"></script>

from v5 to v4, sessions start coming in again.. So it seems to be a bug in the v5 scripts

fuzzybinary commented 4 months ago

Hi @Arthurius,

Thanks for pointing this out. I'll see if I can get a fix up for it soon. Switching to v4 may work for you if you're only using logging, but might cause other errors if you use RUM.

Arthurius commented 4 months ago

Hi @fuzzybinary, Thanks for checking! Switching is indeed not a valid option. I just switched our dev environment to v4 to test it out.

I hope the issue can get resolved soon.

fuzzybinary commented 4 months ago

Hey @Arthurius ,

What are you setting your DatadogConfiguration.version to? My simple checks aren't reproducing the issue.

fuzzybinary commented 4 months ago

Nevermind, I reproduced, and my guess is you're not setting version in the configuration. If you're looking for a quick fix while we work on an official fix, set version and service in your configuration to non-null values and you'll be back up and running again.

Arthurius commented 4 months ago

Thanks, I've set both the version and the service. Now it works.

fuzzybinary commented 4 months ago

The Browser SDK team is now allowing null as possible values for service and version. A new version should be rolled out to CDNs in the near future.

BenoitZugmeyer commented 4 months ago

👋 Just to let you know, this has been fixed in the latest Browser SDK release v5.19.0