Access Denied trace error when running snippet #13
Comments
@giorgio79 Can you confirm whether this error occurs on all snippets or just this one? FYI - I've updated the sample to point at the correct CDN. |
@MIchaelMainer Thx for coming back. Yes. On all. Here is a new trace with the new location. I am using a local Win 10 network folder I just shared.
|
Possibly related issue that I encountered when trying to get the Word demo going OfficeDev/office-js-docs#23 |
@giorgio79 I haven't tried using a local network share before. There may be some issue with that (and I don't know what settings to change to make it work at this point). I suggest at this point that you host the application using some http server. Off the top of my head, I'd suggest that you install node package manager (npm), install http-server, run the server at the root of the application, and then point the manifest SourceLocation element at http://127.0.0.1:8080/#/add-in/word. |
I'll take a look at this issue and your other issues a bit later. |
Thx will look at the localhost option (I use xampp :) It may not be possible, as the Trusted Addin Catalog only seem to accept https locations. Hoping onedrive or sg else can be used for hosting the addon if http fails. PS: The TrustCenter did accept localhost http, checking it now. |
Not sure if you did sg, but the snippet explorer started working from the local network share, so all fine and dandy. |
Very good to hear! |
Error (I am using a local network share folder)
The text was updated successfully, but these errors were encountered: