Can i open a patch that i built to standalon application if max isn't installed?
sorry for the lack of orgainization in the topic, i tried to fit all the key words.
Also, sorry if this is an obvious answer, but i coudlnt find it that is true or not.
basically, i have a patch in Max 7 that i programmed, and i went in the menu to Build Collective / Application, and exported it as an Application (not as a max collective).
file size is about 300mb, and works well on my Macbook Pro where Max 7 is installed.
but i want other pepole to use my patch, or use it as a standalone - but when i tried to open on a diffrent mac, i got an error that the file is damaged and cannot be opened.
so you guys are experts, please tell me if it's possiable to run standalone patches on a machine without Max installed, and if it is, what am i doing wrong?
Thank You.
if you just have a patch, you can use that on other machnes with the max runtime, if you have built an app, this app should work on other machiens, too.
except you or cycling has made something really really wrong. :)
(i mean, beside the fact that apps are 300 mb long, which some people already would call really really wrong.)
Your basic plan is correct: the whole point of a Standalone is to be able to run a patch on a machine that does not have Max installed. One of the reason Standalone files are so damn' big is because a complete copy of the Max Runtime is embedded (on Mac OS you can verify this by choosing "Show Package Contents" from the context-sensitive menu on your Standalone).
The "corrupt file" error message is just that: a notification that the file was somehow corrupted when you copied it from one machine to another.
So, how did you attempt to copy the file?
If you're moving Mac files using Unix- or Windows-based servers, it may help to ZIP the file before copying and decompress on the target machine.
Also note that a Standalone built on a Mac cannot run on Windows, and vice versa. But you said you're copying from one Mac to another, so that shouldn't be the problem.
ROM,
We ran into the same thing and it turned out to be Apple's security settings causing the issue.
See this article below:
http://www.tech-recipes.com/rx/45404/mac-downloaded-app-is-damaged-and-cant-be-opened-error-solved/
The Mac OS system message is totally wrong- its not a corrupt file just because its from an unidentified developer. Hopefully Apple will change this to a more descriptive message in the future. In the meantime there is a workaround as described in the article.
Regards,
Ryan
Hi guys,
So I had the same problem : when I send an application I made to someone, this message appears. It's really annoying to say to people to go to the security preferences to change all that.... Especially when you wanna be a little "pro" with it.
Is anyone knows a way to deal with it ?
I know that this is a really old thread, but even though the app appears to be damaged, it is just a signing issue. If you haven't signed the app as an identified apple developer, and the target computer doesn't have the privacy settings set to open apps from "everywhere" the app will be considered damaged.
Easy fix: https://www.imore.com/how-open-apps-unidentified-developers-mac
Signing the app: https://cycling74.com/forums/max-standalone-in-the-mac-app-store-2018