Skip to main content

Hi All,
I've never had a problem before using composer to package apps until version 10.28. When packaging a drag and drop app such as Krita or Blender, Composer has started displaying this error message during the 'Build as PKG' build process - Couldn't communicate with a helper application.



I've never seen this before, it's doing it on a clean install of Catalina 10.15.7 and on a different machine with an upgrade to Big Sur 11.2.3.



It will package VLC successfully but not Krita or Blender.
It will create DMGs ok for all three.



All three are given the same owner/group & permissions before creating a new PKG.
Root, Admin and 755.



Has anyone else encountered this issue and were you able to resolve it?
Thanks for any info!



I was having the same issue. I checked the online manual and found that they added a new Preference for executable type I found that to be causing the issue. I can only hazard a guess that it is not detecting the executable type correctly. I went into Preferences and changed "Executable Types in PKGs:" to "One or More executables require Rosetta" from "Automatically detect executable types" it fixed the error.

Many thanks @reiven
That worked. Looks like the auto detect isn't detecting intel and universal binaries properly.

@Reiven You save my day... Thanks a lot Buddy

@Reiven this worked for us thanks so much!

got the same error and just made the same change in Composer and now it looks to be processing and just completed.

Ditto. Thanks-a-lot!!!

Thumbs up - thanks!

Thanks! We are digging into M1s now and that was literally a 60 second fix for our issue!

Thanks!

I was having the same issue. I checked the online manual and found that they added a new Preference for executable type I found that to be causing the issue. I can only hazard a guess that it is not detecting the executable type correctly. I went into Preferences and changed "Executable Types in PKGs:" to "One or More executables require Rosetta" from "Automatically detect executable types" it fixed the error.



Thank you!

I was having the same issue. I checked the online manual and found that they added a new Preference for executable type I found that to be causing the issue. I can only hazard a guess that it is not detecting the executable type correctly. I went into Preferences and changed "Executable Types in PKGs:" to "One or More executables require Rosetta" from "Automatically detect executable types" it fixed the error.



it's now a year later, Jamf is up to 10.35 and this is still an issue. Thank you very much for this solution - worked a treat on my M1 Pro!

Thanks, resolved my problem with Composer

I was having the same issue. I checked the online manual and found that they added a new Preference for executable type I found that to be causing the issue. I can only hazard a guess that it is not detecting the executable type correctly. I went into Preferences and changed "Executable Types in PKGs:" to "One or More executables require Rosetta" from "Automatically detect executable types" it fixed the error.



Many Thanks 😊 

I was having the same issue. I checked the online manual and found that they added a new Preference for executable type I found that to be causing the issue. I can only hazard a guess that it is not detecting the executable type correctly. I went into Preferences and changed "Executable Types in PKGs:" to "One or More executables require Rosetta" from "Automatically detect executable types" it fixed the error.



Late reply but thank you! I've been beating my head against a Stata 17 package build for days. Finally got it!

Yes!  thank you spent a day trying to figure it out thinking it was my pacakge contents. 

it's now a year later, Jamf is up to 10.35 and this is still an issue. Thank you very much for this solution - worked a treat on my M1 Pro!


And another 6 months later with 10.39  it is still a 'thing'.

The fix works perfectly, thanks.

Yes!  thank you spent a day trying to figure it out thinking it was my pacakge contents. 


Thank you for this. Still seems to be the fix in 2022 with Composer v.10.40.0

I was having the same issue. I checked the online manual and found that they added a new Preference for executable type I found that to be causing the issue. I can only hazard a guess that it is not detecting the executable type correctly. I went into Preferences and changed "Executable Types in PKGs:" to "One or More executables require Rosetta" from "Automatically detect executable types" it fixed the error.



thank you that helped me a lot!!!

I was having the same issue. I checked the online manual and found that they added a new Preference for executable type I found that to be causing the issue. I can only hazard a guess that it is not detecting the executable type correctly. I went into Preferences and changed "Executable Types in PKGs:" to "One or More executables require Rosetta" from "Automatically detect executable types" it fixed the error.



Thank you for this. Fixed my issue with 10.42.0 as well.

@Reiven you saved my day. Cheers mate!

Still an issue on 10.41 and this is still the fix.  Thank you!!

Glad I found this post. Still an issue on 10.42.1 and on a Ventura client. lol 

Worked for me on 10.44.1 and Ventura client. Oddly, this didn't happen before when I tried to package the same stuff. Started today.

Late reply but thank you! I've been beating my head against a Stata 17 package build for days. Finally got it!


a bit late but how did you create the stata 17 and activation package in composer without it failing? i havent been able to figure it out!

This fix worked for me. I was experiencing this issue when packaging Krita today on an M2 Max-enabled MacBook pro. Using composer 10.48.1

Terms & ConditionsCookie settings