You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed a lot of Start/End Session events with 0 or 1 second duration. Do you have any idea why is this happening? It seems like it's happening when user is not actually using his device and app, but it's initialized through notification receiving. This is a quite big issue for us. The data is wrong because user is marked as active even though he never opened the app. I think no one would expect that. Also this is generating a lot of events which are useless.
The text was updated successfully, but these errors were encountered:
@kiko1312 - do you initialize the SDK within the notification handler? The SDK itself doesn't know if it was initialized at app launch or from a notification. When initializing within a notification handler, you can turn off all default tracking so session events aren't fired.
Summary
Hello.
We noticed a lot of Start/End Session events with 0 or 1 second duration. Do you have any idea why is this happening? It seems like it's happening when user is not actually using his device and app, but it's initialized through notification receiving. This is a quite big issue for us. The data is wrong because user is marked as active even though he never opened the app. I think no one would expect that. Also this is generating a lot of events which are useless.
The text was updated successfully, but these errors were encountered: