-
Notifications
You must be signed in to change notification settings - Fork 18
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
No geolocation context columns in BigQuery when enabled in config #195
Comments
Hi @jkreiz, thanks for reporting the bug! I think this is a problem in the underlying iOS tracker which does not automatically track the geolocation context even in case the We will look into the problem and see how we can address it. |
Thanks @matus-tomlein -- we have an Android build as well, but it's all going to the same table with no geolocation context. Does Android also rely on |
Hi @jkreiz, on Android, the tracker should be able to automatically fill the geolocation context, so you should be able to see it in the events. If this is not the case, there might be another issue on the Android tracker. Can you please confirm that you don't see the geolocation context for all events on Android where you have it enabled in the tracker? We will investigate this as part of this effort as well. |
@matus-tomlein confirmed, we don't see the geolocation context for any events on Android, even though it is enabled in the tracker. |
Hello, asking a tangential question, does setting |
Describe the bug
We are not seeing
contexts_snowplowanalytics_snowplow_geolocation_context_1_0_0
columns in BigQuery, despite having setgeoLocationContext
totrue
in our Snowplow config. We also have Mixpanel implemented and are getting location data there.To Reproduce
Expected behavior
When logging events we should see
contexts_snowplowanalytics_snowplow_geolocation_context_1_0_0
columns in BigQueryScreenshots
Config
Available Contexts
Smartphone (please complete the following information):
All devices, but one example:
The text was updated successfully, but these errors were encountered: