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
There is a slight problem if user kills the app using task manager and then restarts it again, before the events were dispatched. Since the user was online all of the time, the events were not stored into the disk cache, rather just kept in-memory, so they are lost forever (or at least that's what I think happens)
A proposition of fixing that would to never go past the disk cache, always store events in the file, and always drain the disk cache when calling the dispatch() method.
This would prevent from loosing tracking data in the example I mentioned, but probably in other cases as well.
The text was updated successfully, but these errors were encountered:
There is a slight problem if user kills the app using task manager and then restarts it again, before the events were dispatched. Since the user was online all of the time, the events were not stored into the disk cache, rather just kept in-memory, so they are lost forever (or at least that's what I think happens)
A proposition of fixing that would to never go past the disk cache, always store events in the file, and always drain the disk cache when calling the dispatch() method.
This would prevent from loosing tracking data in the example I mentioned, but probably in other cases as well.
The text was updated successfully, but these errors were encountered: