Forums > MaxMSP

All standalone apps are damaged

Jul 15 2012 | 2:48 pm

Since a couple of months I can’t create any standalone application from Max 5 (5.1.9) for Mac (OSX 10.6.8). Even the simplest ones (e.g. summing two numbers): when the .app is created and I try to open it, it says "You can’t open the application …. because it may be damaged or incomplete.". The package seems ok to me, at a quick look, and I have the proper chmod permissions on the .app file.

I know there’re already some threads about this, like, but for some reason most of the replies appear blank (!), and they did not solve my issue.

Does anyone have a hint of why this could happen?

Jul 15 2012 | 6:23 pm

It is not easy to determine what is going wrong. I remember however similar issues with building apps (with version 5 I think, but don’t remember which one). What helped me then is to build to a different location, within the same user folder. Alternatively, you might try a clean install. This is quiet a shot in the dark however. You might provide a link to a broken app to download, so it would be possible to see.

Jul 16 2012 | 10:40 am

Changing the location did not solve the issue…
I’ve put here:
an example of non-working standalone. It only contained a simple [+] objects adding together two ints…
If you have any hint of what is going wrong, that would be really appreciated… Reinstalling is really a shot in the dark, but I’ll try that if needed…

Thanks a lot,

Jul 16 2012 | 12:39 pm

I can build 5.1.9 standalones under 10.6.8 without problem. But the Info.plist file included in looks like it’s built with Max 6.0.0 and looks totally inconsistent. With the attached file, it does work, but it doesn’t explain why your Max5 standalone looks like a bad Max6 standalone…


  1. Info.plist
Jul 16 2012 | 12:41 pm

BTW, I’d be curious to know what I wrote in the old thread.

Jul 17 2012 | 1:32 am

Thanks to your hint, I’ve checked, and found the reason. Max5 doesn’t like the fact that I put in the Max5 folder a copy of Max6 runtime (which I need there to avoid path complication in debugging some externals). As soon as I remove it, everything works fine. That, I must say, is very very weird though. I don’t see why Max5 should bother because a copy of Max6 runtime is inside its folder…

However, thanks Patrick! Mystery solved…

Viewing 6 posts - 1 through 6 (of 6 total)

Forums > MaxMSP