-
Notifications
You must be signed in to change notification settings - Fork 7
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
IPv6 Support for GeoIP #111
Comments
Can you produce the same issue in other internet browsers? |
May need to increase the maximumAge in regards to enableHighAccuracy. Indication that the application is willing to accept a cached position whose age is no greater than the specified time in milliseconds. for ex. https://dev.fitbit.com/build/reference/device-api/geolocation/ |
Browser makes no difference. I do the API calls from PHP, so it is all server-side. Here is my IPv6 you can use for testing. 2604:3d09:a579:6500:f0ef:cbce:5ae4:22c5 The timeout is not where you should focus. That's a symptom, and how you know there is a deeper problem. The problem is that your system works fine for IPv4 format, but not for IPv6. |
I don't know what makes you think FitBit's API is relevant in any way. |
Here's two examples: This one works: And this one does not: |
Hello,
When a network sends an IPv6 address, your API times out trying to geolocate.
This needs to be worked in, as most IPs are switching to over to IPv6.
The text was updated successfully, but these errors were encountered: