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
SCENARIO TO REPRODUCE ISSUE:
Tracker instance must be singleton.
Disable network
Start an android app
Produce some matomo events more than cache size
Enable network. Matomo events go to the server.
Disable network
Produce some matomo events.
Enable network.
ISSUE> NEW events does not send to the server!
ENV / AND CACHE CONFIGURATION:
Android version - 8 (api 26)
Matomo SDK version - 1.4.0
Dispatch Mode - DispatchMode.ALWAYS
Dispatch Interval - 0 Milliseconds
Offline Cache Age - 1440 hours
Offline Cache Size - 1Kb
Technical DESCRIPTION:
SDK doesn't refresh value of "mCurrentSize" variable in class "EventDiskCache" after it sends events to the server (when deletes all cache files in the file system). Files doesn't exist on file system, but SDK think that file system is full and deletes new matomo events. (new matomo events are lost)
Could you fix or explain the workaround for this issue?
The text was updated successfully, but these errors were encountered:
Just did a quick look at the code and I think you are right. Will have to find some time to further look into it. Maybe someone else can submit a PR with a bugfix and tests for this?
SDK losts events in offline mode
SCENARIO TO REPRODUCE ISSUE:
Tracker instance must be singleton.
ENV / AND CACHE CONFIGURATION:
Android version - 8 (api 26)
Matomo SDK version - 1.4.0
Dispatch Mode - DispatchMode.ALWAYS
Dispatch Interval - 0 Milliseconds
Offline Cache Age - 1440 hours
Offline Cache Size - 1Kb
Technical DESCRIPTION:
SDK doesn't refresh value of "mCurrentSize" variable in class "EventDiskCache" after it sends events to the server (when deletes all cache files in the file system). Files doesn't exist on file system, but SDK think that file system is full and deletes new matomo events. (new matomo events are lost)
Could you fix or explain the workaround for this issue?
The text was updated successfully, but these errors were encountered: