• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
LiveCloud standalone issues...
#8
Hi Stam,

You did everything correctly. The process of code-signing and notarizing is complicated. I can see that you navigated it well.

You can solve the problem you are experiencing by doing the following:
  1. 1. On the first run, copy the relevant parts of your project (everything after the starter stack) over to a safe and writeable place.
  1. 2. Run the code from the writeable locationa. 
  1.   a. Macs: specialFolderPath("asup")
  1.   b. Windows: specialFolderPath(26)
  1. 3. Have your pathing point to that location when the environment <> "development"
Yep, developing for Apple has become more complex. All of our shipping apps use this method. LCM (Win version) is designed to be a portable app and thus does not use specialFolderPath(26). It instead writes to files and folders next to the .exe.

Should you decide to codesign your Windows apps, then SFP(26) will be useful. Our 2020 Vision product uses that location.

I hope this helps

-Mark
  Reply


Messages In This Thread
LiveCloud standalone issues... - by stamatis - 07-26-2021, 12:17 PM
RE: LiveCloud standalone issues... - by stamatis - 07-27-2021, 11:11 AM
RE: LiveCloud standalone issues... - by stamatis - 07-29-2021, 10:07 AM
RE: LiveCloud standalone issues... - by stamatis - 07-30-2021, 06:04 PM
RE: LiveCloud standalone issues... - by mark_talluto - 07-30-2021, 11:19 PM
RE: LiveCloud standalone issues... - by stamatis - 07-31-2021, 10:56 AM
RE: LiveCloud standalone issues... - by stamatis - 08-01-2021, 02:12 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)