Forum Discussion
Corrupt ZIP file when publish to LMS
I recently had issues with a file, here's what i was told by Articulate.
When working with syncing applications like OneDrive, Dropbox, or Google Drive, these apps can sometimes stall while trying to sync your project to their cloud storage. This can cause erratic behavior in Storyline, such as errors during publishing, saving, or even corruption of files.
To avoid such issues, we recommend ensuring that your project files are saved to a local folder that is not being automatically synced to any cloud storage service. If needed, here’s an external guide on how to stop syncing to OneDrive.
They recommended all files be stored on your hard drive. In our world today i don't see how this is possible working with Teams to produce content.
I would see if you can make a copy on your hard drive to see if it fixes the issues. You may try creating a new blank project and import all the slides from the old project into the new project. Here’s how: https://community.articulate.com/kb/user-guides/storyline-360-importing-slides-from-other-storyline-projects/1140094
Good luck
- OlleSchlin3 days agoCommunity Member
Thanks for your reply, but I´m not sure if your issue relates to mine. To my knowledge (correct me if I´m wrong), the imsmanifest file is generated by Articulate when publishing something towards LMS. At least it is like that for me; imsmanifest files only exist in outputs I have generated towards LMS.
- OlleSchlin3 days agoCommunity Member
Could it be like that the imsmanifest.xml is removed when you extract the zip file? I have never heard about that, but it happens from time to time that Winzip (or similar program) delete what they consider to be suspected files. But I have no idea why the imsmanifest should be considered as suspected
Related Content
- 10 months ago