Livecode 7.0.3 commercial edition.
Stack compiles and runs as standalone app on the development iMac. Copy it to a MacBook Pro and it can't open the app see attached image.
Compiling the stack on the MacBook Pro it runs ok but when copied to the iMac same issue.
Copy the standalone from the iMac to a mac mini and it runs.
Copy the standalone from the MacBook Pro to the mac mini and get the error message.
All machines allow apps to run downloaded from anywhere.
All macs are running 10.10.x.
Any thoughts?
Mark
The application xxx cannot be opened.
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: The application xxx cannot be opened.
Hi Mark,
This is an interesting one.
How are you transferring your app from computer to computer? Have you tried zipping up your app before transferring as it may somehow become corrupt during this process.
Kind Regards,
Neil Roger
--
LiveCode Support Team ~ http://www.livecode.com
-
This is an interesting one.
How are you transferring your app from computer to computer? Have you tried zipping up your app before transferring as it may somehow become corrupt during this process.
Kind Regards,
Neil Roger
--
LiveCode Support Team ~ http://www.livecode.com
-
-
- VIP Livecode Opensource Backer
- Posts: 9837
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: The application xxx cannot be opened.
If the app is transferred via thumb drive, where NTFS or FAT32 are commonly used, the file system will have no execution bit for the standalone file, and will exhibit the symptom described. Niel's suggestion of zipping the app bundle first should preserve the execution bit.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: The application xxx cannot be opened.
Neil/Richard,
Thanks for your responses which have led me to a solution.
All our development files are kept on Google drive and replicated locally via Google drive.
Following up on your comments it does seem that this is causing the problem. Locally produced images work from Google Drive but images posted from other machines don't.
To get the image to run I have to go to Google Drive in the browser and download it from there (which it does via a zip file) and all is ok.
Strange problem!
Thanks again.
Mark
Thanks for your responses which have led me to a solution.
All our development files are kept on Google drive and replicated locally via Google drive.
Following up on your comments it does seem that this is causing the problem. Locally produced images work from Google Drive but images posted from other machines don't.
To get the image to run I have to go to Google Drive in the browser and download it from there (which it does via a zip file) and all is ok.
Strange problem!
Thanks again.
Mark