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
We've had a couple issues come in where it could be either a bug in a mobile app causing data to be sent more than once, or a bot hitting the data collection endpoint. Bots hitting that endpoint are very unlikely, but the information we send right now makes it hard to be certain. We should attach a diagnostic UUID (or any random number) to each request made so they can be uniquely identified. This would remove at least one source of uncertainty in our investigations.
The text was updated successfully, but these errors were encountered:
We've had a couple issues come in where it could be either a bug in a mobile app causing data to be sent more than once, or a bot hitting the data collection endpoint. Bots hitting that endpoint are very unlikely, but the information we send right now makes it hard to be certain. We should attach a diagnostic UUID (or any random number) to each request made so they can be uniquely identified. This would remove at least one source of uncertainty in our investigations.
The text was updated successfully, but these errors were encountered: