Latest update: Template images breaking and showing "The image cannot be displayed" red X

I am experiencing the same issue.

Same error on my end. Trying to copy and paste an image from another file is giving the same red X icon with the error message. 

Hi ramoncrespo-154​,

Sorry to hear that a recent Storyline update is breaking media from your template.

Thanks for sharing your file. I see the same red X / “The image can’t be displayed” behavior for the affected images. I also did a few additional tests:

• I copied the affected images to a new slide within your project, and they remained broken.
• I copied them into a completely new Storyline project, and they remained broken there as well.
• I checked the states of the affected objects. The object/state structure is still present, but the images themselves remain broken.
• The project as a whole opens normally, and other graphics on the slide continue to display correctly, so this appears to be isolated to the affected image assets rather than the entire project.

Since the .story file contains the affected images in their broken state, we can't fully determine from this file alone whether the issue was introduced when the project was created from your template after updating Storyline. Do you mind sharing one of the original template files that you used to create this affected project? It would be helpful to have a copy of a template that worked correctly before the Storyline update, and hasn't been modified or resaved since.

That would allow us to test the template directly and see whether the images display correctly in the source but become broken when a new project is created from it.

Feel free to upload the additional file here in the discussion or through a support case.

I had a dig inside ramoncrespo-154​ sample .story using my Media Ledger tool and found some detail that might help narrow this down.

The broken pictures haven't lost their image data. They've lost the reference to it. Four picture objects in the slide have imgSet="true" but no assetG attribute at all, and a fifth points at an all-zeros GUID. The asset list only declares seven assets (the six numbered JPGs plus tick.png), all intact with matching checksums, which is why the rest of the slide still displays fine.

One more oddity, story/media contains six files of 212 to 303 bytes each that are actually 30-pixel-wide PNGs saved with .jpg extensions. They're listed in the slide's rels but nothing in the slide XML uses them, and they're not in any asset list. So whatever happens at template import is stripping asset references from some objects and writing junk fragments where the real assets should be.

I have this now as well. This is a hot mess when I need to get a translated course out. I'm just going back to the old version until Articulate fixes this issue. 

Reverting does not solve the problem, but I will not return to the newest version until this problem is solved. I have to redo all the affected images, and that is too big a risk for other courses to take. Not to self, wait a few weeks before updating in the future. 

I have this same issue now when copying bitmaps from one Storyline file to another -- in the file being copied to, a blank outline appears of the correct size, but with the message, "This image can't be displayed".  My solution has been to, in the original file, Export Picture / Export Original Image, and then in the new file, import that Picture.  Playing with it right now, I see that if I copy and paste the bitmaps into another program first, like PowerPoint, then I can copy them from PowerPoint over to the new Storyline, no problem...