standalone error

[tyarmsteadBUSuSfT]

I recently upgraded LC and waned to run a quick app for testing and when I created the standalone I received this error:
There was an error while saving the standalone application could not
copy splash 'Applications/LiveCode 6.1.2app/contents/tools/Runtime/iOS/Device-6_1/
default4inchsplash.png
This is he first app under the upgrade.
Thank you for your help

[Mark]

Hi,

Look at 'Applications/LiveCode 6.1.2app/contents/tools/Runtime/iOS/Device-6_1/
default4inchsplash.png and see if the file actually exists. If not, someone at RunRev forgot to include it. If you have a 6.1.1 install, you could copy the picture from there.

I notice that you wrote LiveCode 6.1.2app instead of LiveCode 6.1.2.app. If you wrote it correctly, exactly as it appeared in the error message, then it is an IDE bug and you'll have to wait for it to get fixed or add the dot yourself in an IDE script somewhere.

Kind regards,

Mark

[ccrraaiigg]

Hi, I'm having this problem too, with LiveCode 6.5 RC4. The PNG file question does exist. Perhaps the problem is that the intended destination directory doesn't exist? How do I find out where LiveCode is attempting to copy the file?

thanks,
Craig

I would include my contact information, but this inept forums system won't let me. I doubt I will notice any responses here, so I guess I've just wasted everyone's time. So far, I'm thoroughly unimpressed with RunRev and its products.

[Mark]

Hi Craig,

From the information I have so far, I must conclude that it is a bug in an IDE script.

If you're unhappy about RunRev, write to support@runrev.com

Kind regards,

Mark

[jacque]

Hi, I'm having this problem too, with LiveCode 6.5 RC4. The PNG file question does exist. Perhaps the problem is that the intended destination directory doesn't exist? How do I find out where LiveCode is attempting to copy the file?

The standalone builder will try to copy the file into the folder that contains the standalone (i.e., the built mainstack) and that folder will exist because LiveCode creates it. Try re-selecting the image in Standalone Settings just to be sure the file path is correct, since that's most likely reason for a failure. Double-check the file path in standalone settings with the actual location on disk. If that isn't it, check the permissions on the image file. That's probably not the problem, but it can't hurt.

I haven't built a standalone yet with 6.5 but I'd be surprised if this were a bug since the behavior has been around for years. It is a pre-release version though so it's possible. If everything above checks out, it would be worth a bug report.

[Mark]

Craig,

Could you post the exact text of the error? Don't type it but copy the error message and paste it here.

Kind regards,

Mark