When the user configures the tracker using remote configuration and sets a default configuration, the default configuration will always be replaced by the fetched configuration regardless of whether it is different or not. This causes a new session to start (since a new tracker is created).
To prevent replacing the tracker in case the remote configuration is the same as the default configuration, we should add a configuration version to the default configuration and only replace it if the fetched configuration has a higher version.
When the user configures the tracker using remote configuration and sets a default configuration, the default configuration will always be replaced by the fetched configuration regardless of whether it is different or not. This causes a new session to start (since a new tracker is created).
To prevent replacing the tracker in case the remote configuration is the same as the default configuration, we should add a configuration version to the default configuration and only replace it if the fetched configuration has a higher version.
The same issue on the Android tracker.