Interesting! But I’ve only had partial success with correcting the name of the assets folder. Indeed, I again tried the same project for which I had sent you a copy, and using “Assets” it failed as earlier described. Changing the name to “assets” did indeed fix the problem! . . . for this project.
However, I had another project with the same “Assets” folder name. Failed as expected. Changed the folder name to “assets” - still failed the same way! Note that this project was much larger - 65 mockups, 37 assets, 1 symbol library. An interesting side-note - with the folder named “Assets” Mockups reported only 25 assets (not 37). I also tried another larger project (43 mockups) with the same failed results - this project had always had the folder named “assets” so renaming was not an issue.
So, it seems the name of the asset folder may be part of the issue, but not everything. Regardless, saving an empty project name before importing the .bmml files solves the problem as you suggested originally - this might be the best work-around.
Another interesting observation - on the larger projects, when I do pre-save the empty project before importing the .bmml files, I have observed the directory into which the project has been saved, using File Explorer (Windows 7). During the “drawing” phase of the import, I noticed that a temp file “[projectName]-journal” (where [projectName] is my project’s specified .bmpr file name) being created and removed from the destination folder multiple times. I can see it come and go (create/delete) several times during the import’s drawing phase, and it is always 4 KB in size. It is deleted if the import is successful. However, if the project file is not saved before the importing the .bmml files, I do not see this journal file creation/deletion process. But exiting Mockups after the failed import (if the project is not pre-saved) does create a 4 KB journal file after the exit (and usually leaves it in the folder with the bad .bmpr file). Perhaps there is a problem with this journal file process if the project is not saved before importing?
Anyway, thanks for the quick response and looking at this problem! At least there is a simple and logical work-around. Thanks again for a great product!