Log cached WooCommerce version along track events #16464
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Description
We have found ourselves a few times in iOS with lack of data when trying to check WooCommerce versions from the track events dashboard, for example, recently when deciding if would be good enough to increase the threshold of a feature from 9.6 to 9.7, since we could only rely on Android data and guess iOS user base distribution would be similar
This PR mimics Android's approach to pass the WooCommerce version as default property along track events.
For this we retrieve, store in memory, and pass the woo version through the
cached_woo_core_versionproperty (for consistency with Android naming) to all track events, following the same pattern as others likeisWpcomStore.Test Steps
cached_woo_core_versiontracks the woo versionStore 1:
Store 2:
Screenshots
N/A
RELEASE-NOTES.txtif necessary.