help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AppStore rejection for ipv6

ANSWERED

‎08-23-2016 21:36

‎08-23-2016 21:36

App reviewers are rejecting apps that don't handle ipv6. It seems that Fitbit's servers do not support ipv6, is this correct? Any idea if they will be upgraded?
Thanks
Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

‎08-24-2016 14:38

‎08-24-2016 14:38

@ThatOneCat: I read Apple's announcement and it seems to suggest that this is a client-side requirement more than a server-side requirement. api.fitbit.com doesn't yet have IPv6 addresses, but Apple doesn't seem to be requiring this—only that servers are configured correctly to be reachable when using DNS64/NAT64 translators.

 

I tried Apple's Test for IPv6 DNS64/NAT64 Compatibility and Fitbit's app was able to communicate with Fitbit's API without issue.

 

If there is a specific issue, please let us know.

View best answer in original post

Best Answer
3 REPLIES 3

‎08-24-2016 14:38

‎08-24-2016 14:38

@ThatOneCat: I read Apple's announcement and it seems to suggest that this is a client-side requirement more than a server-side requirement. api.fitbit.com doesn't yet have IPv6 addresses, but Apple doesn't seem to be requiring this—only that servers are configured correctly to be reachable when using DNS64/NAT64 translators.

 

I tried Apple's Test for IPv6 DNS64/NAT64 Compatibility and Fitbit's app was able to communicate with Fitbit's API without issue.

 

If there is a specific issue, please let us know.

Best Answer

‎08-24-2016 16:53

‎08-24-2016 16:53

Ok thanks for the detailed response. I will investigate further.
Best Answer
0 Votes

‎08-25-2016 01:20

‎08-25-2016 01:20

It was 100% my fault. Just want to say thank you again for confirming everything is working on your end.
Best Answer
0 Votes