Posted on 04-12-2021 08:37 AM
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!
Solved! Go to Solution.
Posted on 04-14-2021 01:57 PM
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.
Posted on 04-14-2021 01:57 PM
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.
Posted on 08-18-2021 10:15 AM
Thank you!
Posted on 02-01-2022 12:16 AM
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!
Posted on 06-29-2022 01:34 PM
And another 6 months later with 10.39 it is still a 'thing'.
The fix works perfectly, thanks.
Posted on 05-02-2022 03:47 PM
Many Thanks 😊
Posted on 05-26-2022 04:56 AM
Late reply but thank you! I've been beating my head against a Stata 17 package build for days. Finally got it!
Posted on 04-03-2023 09:55 PM
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!
Posted on 09-20-2022 08:40 AM
thank you that helped me a lot!!!
Posted on 10-26-2022 06:07 PM
Thank you for this. Fixed my issue with 10.42.0 as well.
Posted on 03-26-2024 09:33 AM
Oh.my.goodness, you guyss!! Thanks so much for this solution @Reiven I was having issues packaging JASP and it kept failing (hasn't happened before) and couldn't figure out what the issue was, searched for the error code and came across this thread. This fixed it! Grateful for this community. Thank you!
Posted on 04-16-2021 04:31 AM
Many thanks @reiven
That worked. Looks like the auto detect isn't detecting intel and universal binaries properly.
Posted on 05-10-2021 08:51 AM
@Reiven You save my day... Thanks a lot Buddy
Posted on 05-15-2021 01:27 PM
@Reiven this worked for us thanks so much!
Posted on 06-03-2021 11:11 AM
got the same error and just made the same change in Composer and now it looks to be processing and just completed.
Posted on 06-11-2021 10:23 AM
Ditto. Thanks-a-lot!!!
Posted on 06-25-2021 02:06 AM
Thumbs up - thanks!
Posted on 07-08-2021 01:52 PM
Thanks! We are digging into M1s now and that was literally a 60 second fix for our issue!
Posted on 07-20-2021 08:38 PM
Thanks!
Posted on 02-01-2022 04:33 AM
Thanks, resolved my problem with Composer
Posted on 06-15-2022 12:08 PM
Yes! thank you spent a day trying to figure it out thinking it was my pacakge contents.
Posted on 08-31-2022 09:05 AM
Thank you for this. Still seems to be the fix in 2022 with Composer v.10.40.0
Posted on 10-28-2022 09:30 AM
@Reiven you saved my day. Cheers mate!
11-10-2022 11:20 AM - edited 11-10-2022 11:20 AM
Still an issue on 10.41 and this is still the fix. Thank you!!
Posted on 12-08-2022 06:00 PM
Glad I found this post. Still an issue on 10.42.1 and on a Ventura client. lol
Posted on 03-08-2023 08:07 AM
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.
Posted on 08-03-2023 01:55 PM
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
Posted on 08-18-2023 08:11 AM
On composer 10.49.0. This is still an issue, and the fix still works.
Posted on 10-19-2023 09:26 AM
This worked for me as well!
Posted on 10-24-2023 11:37 AM
Thank you! Weird how this hasn't been patched yet.
Posted on 11-29-2023 01:49 AM
Thank you very much.You`ve been very helpful.
Posted on 12-04-2023 07:32 AM
Thank you so much, you've been a great help
Posted on 01-30-2024 11:59 PM
Thanks a lot! It fixed my problem with gimp 2.10.36 (apple chips).
Posted on 06-04-2024 08:57 AM
This is still an issue in composer 11, thanks for the solution.
Posted on 06-15-2024 01:07 PM
Thank you for the solution