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: 

Fetch from settings jsx blocked by CORS

‎03-01-2022 14:19 - edited ‎03-01-2022 14:20

‎03-01-2022 14:19 - edited ‎03-01-2022 14:20

I want to use fetch from the settings jsx, but it is getting blocked by CORS.

 

 

Access to fetch at 'SERVER_URL' from origin 'https://app-settings.fitbitdevelopercontent.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

 

 

I have no control over the server to add the Access-Control-Allow-Origin header. How can I get around this? Can I fetch it from the companion and send it to the settings through messaging? Should I store it in a file?

Best Answer
Labels:
0 REPLIES 0