A flexible widget for user notification. Customize your text, button, duration, animations and much more. For Android devs, it is made to replace Snackbars and Toasts.
Describe the bug
When using the another-flushbar package to display flushbar notifications in a Flutter application, Firebase Analytics is incorrectly tracking the route /flushbarRoute as a screen view. This behavior causes /flushbarRoute entries to appear in Firebase Analytics as screen views, leading to inaccurate analytics data and inflating screen view counts with unwanted entries.
To Reproduce
Initialize Firebase Analytics in the Flutter app.
Use the another-flushbar package to display a flushbar notification.
Observe Firebase Analytics, where /flushbarRoute appears in the screen views list.
Expected behavior
When using the another-flushbar package, flushbars should display as overlays without triggering a new screen view event in Firebase Analytics. Specifically:
Flushbar notifications should not register as new routes or screen views in Firebase Analytics.
Firebase should only track actual user-navigated screens in screen_view events, ensuring accurate analytics data.
This will prevent /flushbarRoute or any similar unintended route from appearing in Firebase Analytics, maintaining accurate screen view counts for user navigation.
Screenshots
Additional context
This issue impacts the accuracy of Firebase Analytics data, which is especially critical for applications that rely on precise user behavior tracking.
Would it be possible to implement a fix that either prevents /flushbarRoute from being tracked by Firebase or provides an option to disable this route tracking?
Describe the bug When using the another-flushbar package to display flushbar notifications in a Flutter application, Firebase Analytics is incorrectly tracking the route /flushbarRoute as a screen view. This behavior causes /flushbarRoute entries to appear in Firebase Analytics as screen views, leading to inaccurate analytics data and inflating screen view counts with unwanted entries.
To Reproduce
Expected behavior When using the another-flushbar package, flushbars should display as overlays without triggering a new screen view event in Firebase Analytics. Specifically:
Flushbar notifications should not register as new routes or screen views in Firebase Analytics. Firebase should only track actual user-navigated screens in screen_view events, ensuring accurate analytics data. This will prevent /flushbarRoute or any similar unintended route from appearing in Firebase Analytics, maintaining accurate screen view counts for user navigation.
Screenshots
Additional context This issue impacts the accuracy of Firebase Analytics data, which is especially critical for applications that rely on precise user behavior tracking.
Would it be possible to implement a fix that either prevents /flushbarRoute from being tracked by Firebase or provides an option to disable this route tracking?