Hi Steve
The best success I have had is to upload the generated file to a website and access it from your phone from there.
Not sure I understand what you mean by that.
Restating I'm in no way a HTML guru so the following is little more than stabs in the dark
Using FF with web developer tools active (Ctrl+Shift+i) I can see Network activity. Doing nothing, each time I run the page I would either get the CORS error or it would seem all good with the return info available under "Response". No rhyme nor reason for it to error or not, totally random. Irrespective of having a response available or not, the Fetch Macro never gets called.
There is a lot of misleading, confusing and contradictory information on CORS available on the web. One very reliable source we probably all use stated you cannot send a Fetch request to a server having CORS headers. Instead you need to use GET.
So, in the component I went to advanced and switch off "CORS". A couple of tweaks later and I could connect every time, getting my 200 OK, but unfortunately I was not getting any response at all.
At one point I did get the macro to trigger but there was no data returned.
Eventually I gave up and looked at implementing what most info states, to modify the server header. Now this is where I really get confused. As the page is just a PHP file hosted on a server, that only runs a couple of PHP commands that don't access any other files on the server or elsewhere, I don't really understand why I am getting CORS at all. I'd be grateful if someone could explain that.
Reading the much confusing guidance, for security it suggests not to use the "*" wildcard in CORS header, but your own domain. This didn't do any good and I was now getting different CORS errors. As per above I am not accessing any other sites or files so...... Other advice suggested that those citing security concerns regarding the "*" don't understand what is going on. So, using the "*" wildcard all the above problems resolved themselves.
Not sure I will keep the "*" as I was just playing around with Web Developer, and once the above was resolved my chart more or less worked as expected.
Downside is I'm just as confused about CORs as I was before, as I don't see why it would apply in my scenario.
Upside is I have learned a lot about FC Web Developer and how to use it<s>
I've always thought FC itself was very intuative and you could just stumble your way around and get something working, but not so much with WD. It may all be crystal clear if you watch a video, but I'm no fan of them. Admittedly, I just downloaded a couple of examples and tried to get the gist from them, which would probably have worked if I was talking to an embedded device rather than a server.
Regards
PS
Tested the chart OK on a PC running FF and Edge, then on an android running FF, Chrome and DuckDuck Go. No issues.