File Transfer sample application

[BobFrankston]

It works fine in simulator. I also did an app based on it which successfully interacts with websites.

But when I run the sample app as-is unmodified on my Versa it fails -- just does the initial "Waiting..." and nothing more.

In my more complex app I add handlers that send error messages from the companion to the app. The app portion worked in my more complex example by updating a counter. But the companion failed. This is why I went back to the unmodified sample for testing.

[JonFitbit]

Have you granted the "Internet" permission? Can you post the project on Github?

[BobFrankston]

yes. Gave permissions.

I'll need to get up to speed on Github but here is a pointer to the ZIP file https://1drv.ms/u/s!AglBpbKyzKIQjIFWZHh0qjk4XIr_9A (with one URL changed to protect the guilty)

[JonFitbit]

I think it might be because you're trying to fetch an http resource, are you able to change that to https?

[BobFrankston]

It worked in the emulator. Why would it fail on the watch itself? I also catch errors and send messages to the app so that I'd be able to detect such problems but the error message don't seem to arrive.

Is there an equivalent to console.log that sends messages back to Fitbit Studio from the device?

[JonFitbit]

The mobile device has security restrictions which I'm guessing the desktop browser does not have.

console.log can be used on the device and the companion.

[BobFrankston]

I'll try to do some experimenting later today. 

[BobFrankston]

To keep things simple I took the file transfer app and ran it essentially as-is and it worked in the emulator but on the Versa did not get beyond "waiting ..."

https://1drv.ms/u/s!AglBpbKyzKIQjIFfRpnA_UCyNHRoXA

(BTW, had 1006 error connecting to the server but eventually it connected).