Skip to main content
Inspiring
November 9, 2012
Answered

com.apple.launchd.peruser Exited with code: 4

  • November 9, 2012
  • 1 reply
  • 1292 views

We have build a game to run on the mac desktop.

The game was built using Flash Builder 4.6 on the pc, using Air 3.5 (was using Air 3.4 until a few days ago)

I create the swf on the pc, and then copy it over to the mac mini - (which was running OSX 10.7 - updated yesterday to 10.8 in case that was the problem)

Once on the mac mini - I use the Air 3.5 SDK for mac to build the .app using ADT

/Users/macmini2/Documents/AdobeAIRSDK/bin/adt -package -keystore MM2.p12 -storepass PASSWORD -storetype pkcs12 -target bundle "../release/Megaplex2.app" Main-app.xml Main.swf AppIconsForPublish Data

When I run the final app file on the mac mini, it runs without any problems. (OSX 10.7 and 10.8)
I have also tested this app on a macbook pro without any problems (OSX 10.7)

The problem results when we send the app to our distribution partner. They are reporting that the app is failing to launch:

On my Mac Mini (10.6) it would never appear. On two of our Mac tester’s iMacs, the app icon appeared in the dock momentarily, before then closing again (no window appeared).

The only clue to this so far is a console log where it output this:

11/8/12 5:12:00.800 PM com.apple.launchd.peruser.243932923[132]: ([0x0-0x3f33f3].Megaplex2[3114]) Exited with code: 4

11/8/12 5:12:04.907 PM com.apple.launchd.peruser.243932923[132]: ([0x0-0x3f43f4].Megaplex2[3118]) Exited with code: 4

11/8/12 5:12:06.240 PM com.apple.launchd.peruser.243932923[132]: ([0x0-0x3f53f5].Megaplex2[3120]) Exited with code: 4

11/8/12 5:12:35.596 PM com.apple.launchd.peruser.243932923[132]: ([0x0-0x3f83f8].Megaplex2[3127]) Exited with code: 4

11/8/12 5:12:37.040 PM com.apple.launchd.peruser.243932923[132]: ([0x0-0x3f93f9].Megaplex2[3130]) Exited with code: 4


I installed the air runtime on the build machine to Air 3.5 and it made no difference.

Anyone have any idea what could be causing this?

This topic has been closed for replies.
Correct answer DaveGallant

Ok, looks like we found the problem.

When I was zipping the app to send to them, I was zipping it on the PC.
Turns out, this is cause.

if  I zip it on the mac using it's "compress" function and send them THAT zip, it seemed to run ok.

/me shakes head.

1 reply

DaveGallantAuthorCorrect answer
Inspiring
November 9, 2012

Ok, looks like we found the problem.

When I was zipping the app to send to them, I was zipping it on the PC.
Turns out, this is cause.

if  I zip it on the mac using it's "compress" function and send them THAT zip, it seemed to run ok.

/me shakes head.