RNSScreen in analytics events

[thomasblom]

I'm using @react-native-firebase/analytics in combination with react-native-screens . In every event there is a property firebase_screen_class that contains the current classname of the screen.
By default react-native-screens sets this property as RNSScreen, but i change the value with analytics().logScreenView(...).
After a couple of events it changes back to RNSScreen and i'm not sure where that happens..

Does anyone know more about this value and where it comes from and how it resets to the initial value?

Thanks in advance!

[Panda-ref]

Happens to us as well. Mostly happens on iOS.

const handleNavigationStateChange = useCallback(async () => {
    const previousRouteName = routeNameRef.current;
    const currentRouteName = navigationRef.current.getCurrentRoute().name;

    if (previousRouteName !== currentRouteName) {
      await logScreenView({
        screen_name: currentRouteName,
        screen_class: currentRouteName,
      });
    }
    routeNameRef.current = currentRouteName;
  }, []);

Always keeping the @react-native-firebase/* packages up to date with dependabot.
@mikehardy Is there any recommendations on how to avoid that or what can cause it?

[Romaric-CH]

I have the same issue. Any updates on this ? 🙏

[ammaarkhan]

Were any of you able to find a fix for this? @thomasblom @Panda-ref @Romaric-CH @mikehardy

[ammaarkhan]

I'm trying out and seeing if stopping the automatic screen tracking might fix it. Credit: https://stackoverflow.com/questions/61056541/how-to-remove-mainactivity-and-uiviewcontroller-from-screen-tracking-in-react-na/74313385#74313385.

[tadeumx1]

This solution fix that ?

[ammaarkhan]

Oh sorry I forget about updating, yes it did!

[daviddamilola]

hi @ammaarkhan , did this solution mean that those values are set as not set in the firebase dashboard?

[ammaarkhan]

hey. I'm sorry unfortunately I cannot recall exactly. I stopped working on apps early this year so I haven't been looking at it.