-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Region/City/DMA reporting (none)
after upgrading to React Native package v1.4.2
#627
Comments
Interestingly, I've found that using an older version in my
This causes the I'm not familiar with how yarn/npm packages work - at all, really - but comparing to other public repos, it looks like the Amplitude tagging naming schema (e.g. So: I kind of suspect this caused by some kind of tag resolution issue, and perhaps in the past it just happened to work because of timing (i.e. latest tag lined up w/ what I was already using). Or maybe there are local cache issues. I'm just reaching. (It's almost like the Pod version is using the semver operators from my |
(none)
after upgrading from React Native package v1.2.2 ~> v1.4.5(none)
after upgrading to React Native package v1.4.2
Update: can confirm the breaking package version is v1.4.2. Makes sense given the commits related to the country setter: https://github.com/amplitude/Amplitude-TypeScript/releases/tag/%40amplitude%2Fanalytics-react-native%401.4.2 |
Hi @go-sean-go thanks for reporting the issue! We just released a new version and not track country value by default. This should help. Feel free to upgrade and let us know if that's still an issue. |
Thank you! I will test after the holiday break & report back in the early new year. |
Version 1.4.7 fixed this issue for me 👍 |
After upgrading from
"@amplitude/analytics-react-native": "^1.2.2"
to"@amplitude/analytics-react-native": "^1.4.5"
, DMA and City info has starting returning(none)
in all of my Amplitude dashboards for all new users (i.e. users whoseStart Version
was after the Amplitude v1.4.5 release). Existing users who had installed before v1.4.5 rolled out still persist their historical/preexisting location info - even when using v1.4.5.Note that we do not supply any location info; we rely on the GeoIP Lookups described here: https://help.amplitude.com/hc/en-us/articles/360016257391-FAQ-User-counted-under-none-or-an-unexpected-value
(This has worked for us for almost a year, for new and existing users - and only started failing after the v1.4.5 update.)
Here is a chart showing the change - Nov 9 is when we released the Amplitude library update (from 1.2.2 to 1.4.5):
Expected Behavior
Current Behavior
On number (3) above, location fields are all reporting empty/null/none. See:
Environment
The text was updated successfully, but these errors were encountered: