1.1.9 Will not open existing mockups
Hi,
I've just installed the new version (1.1.9) of the desktop product (on OS X) but when it opens it says "not a valid mockup file' and that''s it. I can't open any of my mockups. Ideas?
I've just installed the new version (1.1.9) of the desktop product (on OS X) but when it opens it says "not a valid mockup file' and that''s it. I can't open any of my mockups. Ideas?
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
Ok, I got it. It was a stupid one-liner. The new build 1.1.12, already live, fixes the problem. Chris, if you'd like a refund let me know, I feel really bad about causing you anxiety.
I’m disappointed with myself
The company and 1 other person say
this solves the problem
-
Inappropriate?Chris, I'm on it, I'll report back ASAP.
-
Inappropriate?Chris, I posted build 1.1.10 which has a small fix which might help. Unfortunately I am unable to reproduce your bug, could you please give me some information on how to reproduce it? First question: did you by any chance move or delete the last mockup file you were editing before upgrading?
Also, if you remember what that file was, could you email me the XML or the file itself at peldi@balsamiq.com? The file format for mockups has not changed since 1.0, but you never know.
I'll keep digging. So sorry about this. -
Inappropriate?In the meantime, here's a workaround. Quit Mockups if it's open, then go to your user folder, then Library, then Preferences, then delete any folder that starts with BalsamiqMockups. Empty your trash and re-launch mockups.
This should get you back, it will just clear your preferences (if you like to see the UI library or not, if you like to see the Notebook or not, that sort of thing). It will also clear the value of your last open file, which is what's causing the problem. -
Inappropriate?Ok, I got it. It was a stupid one-liner. The new build 1.1.12, already live, fixes the problem. Chris, if you'd like a refund let me know, I feel really bad about causing you anxiety.
I’m disappointed with myself
The company and 1 other person say
this solves the problem
-
Crikey, I nip off for dinner and you identify the problem, publish a workaround and create an extra 3 builds. How could I possibly ask for a refund with that sort of service. When I said I was anxious, it was only the tiniest of anxieties. -
Inappropriate?marking as solved
1 person says
this solves the problem
Loading Profile...



