Cannot publish site with new images.
See original GitHub issueDescribe the bug Image files become XML-files with errors after publish.
To Reproduce I follow the how to guide to create a new design. I upload new pictures, I leave the site running and run the npm run publish. This seems to pull image files from blob storage and store them in the website/content folder. The files become 1 kb large jpgs. I opened the jpgs in VS and saw that they are xml files, containing errors.
<?xml version="1.0" encoding="utf-8"?><Error><Code>ResourceNotFound</Code><Message>The specified resource does not exist. RequestId:c87ba921-701e-0036-1776-d259a6000000 Time:2019-03-04T10:39:08.2825033Z</Message></Error>
Expected behavior Files should be jpegs.
Screenshots I also have the run log from chrome showing som additional information from when I added a new image to the site:
Additional context Basically it seems it cannot get the file from blob storage when the publish script runs.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (3 by maintainers)
Top GitHub Comments
Ok. Finally got around to making a small video for you guys. I have shared it on my onedrive: https://enfo-my.sharepoint.com/✌️/g/personal/mikael_sand_enfo_se/EajZxKX5X5dAuC94fknZa6kBCiQEFD60Cb3DXRIY6ag2TQ?e=hFpOsJ
To answer questions above: This ONLY happens to fresh files. I enabled cors (I can see that the file is correctly referenced but it is an xml file). The image was not deleted prior to publishing the site. I have generated all new keys for everything today just to make sure. Everything else works, the names are correct and I can find references to them using APIm API.
Great! Thanks for confirming and for helping us nail it down, @mikaelsand.