Skip to main content
Participant
March 6, 2017
Answered

Animate CC2017.1 runtime embedded publishing not working

  • March 6, 2017
  • 2 replies
  • 433 views

Short story: trying to publish "Application with runtime embedded" - does not create folder or app and does not generate an error.

Using Animate CC2017, AIR 24.0.0.177 (tried 24.0.0.180 as well). Windows 10.

My process: AIR Settings->Output as "Application with runtime embedded", clicked "publish" - I can see that Animate is creating a temp folder and appears to be compiling it - but when it appears to be finishing, it deletes the temp folder and doesn't create the myapplication.app folder. This happens on several projects, but not all of my projects.

A couple of times, clicking "publish" in the Publish Settings actually worked, but not consistently. I've tried using different SDKs - including beta SDKs. I've tried renaming the project and moving the project to another drive.

Creating the AIR package and Windows Installer both work, but I really need the Application with Runtime Embedded for my client's needs.

Not sure what else to try. I'm hoping to avoid re-installing Windows and Creative Cloud.

FWIW, this project is compiled for a number of platforms (IOS/Android/Windows) - and I frequently switch the output.

    This topic has been closed for replies.
    Correct answer wigginsray

    I think I figured it out - it appears if I have other Creative Cloud applications running  - it doesn't create the folder. Weird.

    2 replies

    Participant
    April 4, 2017

    Well not really. it's doing it again. Not sure what to do. Is there another way to compile the runtime embedded?

    Colin Holgate
    Inspiring
    April 4, 2017

    Did you update to 2017.2? There were file saving issues fixed in that update, though I don't know if that would solve your case.

    One thing for you to check is the path that the SWF is published to. If that is incorrect it could lead to a similar symptom.

    wigginsrayAuthorCorrect answer
    Participant
    March 30, 2017

    I think I figured it out - it appears if I have other Creative Cloud applications running  - it doesn't create the folder. Weird.