08-15-2019 09:59 - edited 08-16-2019 06:32
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-15-2019 09:59 - edited 08-16-2019 06:32
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Problem solved. Code tweaks fixed it. Now works fine.

08-15-2019 16:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-15-2019 16:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Tried multiple variations of the Fetch post function and nothing works on the Pixel 3a phone. My other mentioned phones and the simulator show the code working fine. Weird. I saw there was a Fitbit app update to 3.3, but that didn't fix it.

08-15-2019 17:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


08-15-2019 17:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
What error message or other symptoms are you getting?
There's a small chance that the phone is injecting one or more additional headers that the web site isn't liking (CORS?). It shouldn't be that, but it's all I can think of.
Gondwana Software

08-15-2019 17:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-15-2019 17:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I don't have any error messages to consider. My son uses a Versa Lite. I suppose I could try posting errors to a text field on the watch face itself. Just annoyed because it works on other android phones. I contacted Google, and they said I should factory reset the phone. Did it. Nothing got fixed.

08-15-2019 20:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-15-2019 20:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Well, I just connected my Ionic to my son's Pixel 3a and everything worked. I was able to use the fetch Post method to send data to a web API. So I guess this means I now have to pair the Versa Lite to a non-Pixel 3a phone and see what happens.

