emu-app-config + Edge + Clay = error when saving

[a1291762]

I raised this against pebble-tool (coredevices/pebble-tool#73), but I'm not sure it's a pebble tool issue, and might rather be a clay issue?

I'm not exactly sure when this started happening, but it seems to be something in Edge.

I eventually found that I could get this working again by visiting this URL and disabling the local network access check.
edge://flags/#local-network-access-check

I was given this page as a reference for the feature
https://chromestatus.com/feature/5152728072060928

I do not see a way to allow local network access for clay.pebble.com.s3-website-us-west-2.amazonaws.com, perhaps becuse it is a http URL and not a https URL?

I am able to paste the URL into Safari and save from there.

I'm not even sure there is anything that can be done here, since this comes from the browser. But if this is how browsers intend to behave in the future, then this may start to impact more people?

I'm not sure what this cloud server is doing. I read about the design of clay, and it does not seem that the server itself would be doing anything. So maybe a mitigation is to run a local server to send the URL to instead of an AWS URL? But that's more complexity on the local tooling and I don't know how that interacts with non-clay config. Indeed, given the URL has "clay" in it, this may actually be a clay-specific issue?

(I'll note that I'm using Rebble Clay, since Pebble Clay appears to be unmaintained).
ie. https://github.com/pebble-dev/clay

[a1291762]

I think I have tracked the steps...

1. pebble-clay encodes a URL into the package.
2. pebble build writes this into the .pbw, which gets installed onto the emulator.
3. pebble emu-app-config pulls this URL out of the emulator and loads it into a browser.
4. The browser is expected to serve a (small) HTML page, with most content arriving in the URL itself.

I copied the small HTML page served up by http://clay.pebble.com.s3-website-us-west-2.amazonaws.com/ and saved it as ~/Sites/clay.html. I have apache enabled, so this is accessed vi http://localhost/~link/clay.html.

I modified the URL in pebble-clay, built the package, installed it into my project.

I found out that you have to remove node_modules from pebble-clay after building, because otherwise pebble build goes looking for package.json files and barfs because they don't include the expected name and version fields. That details is not mentioned in the README!

I installed my project to the emulator.

I ran pebble emu-app-config, which loaded http://localhost/~link/clay.html#... Since this isn't a remote host, the fact that is isn't https didn't matter, and I could click Save and have it work, without needing the browser to disable the local network access check.

This confirms what I suspected... that a local http server would bypass the browser issues.

What about a remote server that supports https? I tried https://clay.pebble.com.s3-website-us-west-2.amazonaws.com/# but it didn't load, it just sat there spinning. I tried my own website, which supports https and was able to serve the clay.html just fine, but alas, something on it didn't like the URL, so it gave me a 403.

I'm not really sure where to go from here. I haven't been able to confirm that a remote https site bypasses the browser check (though the linked documentation suggests it would at least show a prompt, something a http site cannot even do). Somehow using a local http server seems like something clay itself can't do. Maybe pebble-tool could? But that creates a weird dependency between clay and pebble-tool (and only for the emu-app-config case, presumably when actually loading config on a real watch, the phone app is hitting that AWS URL?)

[deosrc]

Also experiencing this on Firefox. I tried with https too and experienced the same where the page loading goes on so long that it times out.