LiveCloud standalone issues...

[mark_talluto]

In the end i think i narrowed the problem down to the folder i was trying to include in the 'copy files' section. This folder contains the CanelaDB folder and the mainstack that is launched from the splash stack; the idea is that these are copied to the user's Documents folder on first run as a writeable location.

That is a good design. LCM and other apps we have made use of this model. Distributed apps for Mac will need to factor this in going forward. 

I discovered if i removed this folder and *only* added the canelaDB folder the standalone would build as expected; and I added the mainstack to the 'stacks' screen (just needed an extra line of code to make sure these both end up in the same place in the user's Documents folder). I also had to disable messages while building to prevent the mainstack from being launched during the build...

There was a change in the build process that now fires preOpenStack, openStack, and closeStack messages when using the standalone builder. 
If you are project is affected by this, you could add code like the following to help.

on closeStack
if the mode of stack "revStandaloneProgress" > 0 then
exit closesStack
end if
end closeStack

With regards to the checksum issue, I'll see if i can replicate the issue again on the target Windows system; keep in mind that LCM will not run on that system (there is something in the firewall that is I think blocking some function of spiceKit, as per a previous support email - missing it's launcher). Will the log file from my mac be any help?

For the time being, you can export the toolKit from the system that can run LCM. The target operating systems should be able to use the output from the building process just fine.

I would need the log to the system that is failing. It might give us some insight. If the firewall is blocking interaction with our servers, you can typically reverse any block from the Firewall UI of Windows. I had accidentally blocked apps before and had to go in there and adjust the inbound and outbound rules. 

--- EDIT --- 
I also forgot to mention that adding the files manually seemed to work OK when running it off my system. But when uploading the file and then re-downloading, MacOS would completely stop this from running stating that the app had been tampered with (which it had )  so i was very keen i could build this directly without having to manually add. Probably something that can be fixed when notarising etc, but easier not to have that issue!

Manually is my favorite method. You can build your Mac app before code signing and notarizing it. You should be able to make any adjustments you want before the codesigning process.

As always, we want you to be successful. Let us know how it all goes.

-Mark