08-15-2019 09:59 - edited 08-16-2019 06:32
08-15-2019 09:59 - edited 08-16-2019 06:32
Problem solved. Code tweaks fixed it. Now works fine.
08-15-2019 16:44
08-15-2019 16:44
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
08-15-2019 17:01
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.
08-15-2019 17:51
08-15-2019 17:51
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
08-15-2019 20:38
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.