Composer failing on .pkg files

mconners
Valued Contributor

I have been fighting composer for a couple of days and what's odd, composer works with .dmg files. I can create .dmg files, but if I choose to create a .pkg file, it fails. Further, if I try and take an existing, working .pkg file into composer and attempt to convert it to source, it fails to convert. I have uninstalled and removed all preference files. I have tried this on a VM, my Mac and another Mac. We have tried three different versions of composer. They are all doing this. This makes me believe an OS update could have borked composer. Anyone else having troubles lately?

15 REPLIES 15

andrew_scherf
New Contributor

Having the same issue here and I've been already frustrated enough trying to deploy AnyConnect with only specific modules, and the OrgInfo.json file for Umbrella. Tried using the ACTransforms.xml file, but Cisco documentation is terrible.

jhalvorson
Valued Contributor

What OS and platform (Apple Silicon / Intel) are using with Composer?
Have you verified within System Preferences >> Security & Privacy >> Privacy that Composer has been granted Full Disk Access?

andrew_scherf
New Contributor

It's been on Intel only and happening across Mojave, Catalina and Big Sur. Tried latest versions of Composer and older ones. Full Disk Access has been granted when needed. I just stopped starting with .pkg's and trying to make a source of that, and using the .dmg. No issue since then.

vaksai
New Contributor II

Same issue here, Composer 10.29.2 fails on "Creating Directory Structure" on both Intel and Apple Silicon Big Sur 11.4.

user-jXpFVAbPRc
New Contributor

Same problem here with composer 10.30.3 on Big Sur (Intel based machine).

Ke_ReM
New Contributor III

experiencing this error in Composer now on BigSur, m1 macbook air using both 10.34.2 and 10.35 versions.

”converting to source failed”

zerocounts
New Contributor II

we are also experiencing the same error "converting to source failed": macOS 12.2.1, Composer 10.33, M1 Max 

santoroj
New Contributor III

Does/has anyone found a solution for this. Can't really go back to an older version as I dont have one.  I am running Monterey on Intel with Rosetta added for some other apps to function.  This issue has been going on for a long time.  Can't really resort to a DMG when the vendor is only offering PKG's.  

MasterNovice
Contributor

Adding to the list. I am seeing this with 10.37 on Intel 12.3.1

scottb
Honored Contributor

Has anyone tried to move the following folder out to see if that helps?

/Library/Application Support/Jamf/Composer

I don't say delete it as it keeps your projects in there and I for one don't like losing the contents.  

I had trouble years back, and that seemed to help, but I'm not seeing this issue at the moment...

santoroj
New Contributor III

I have done this and sometimes it works and sometimes not, but the bigger problem is for something that has been going on for so long, why is there still no permanent fix? 

vaksai
New Contributor II

Go into Composer Preferences and change "Executable Types in PKGs" from "Automatically detect executable types" to "One or more executables require Rosetta"

scp
New Contributor

Perfect !

It's working now :)

jsnyc
New Contributor II

I just came across this issue.  I am trying to convert a package to a source I I get "Converting to Source Failed" I am using Composer 10.41.0, on M1 Mac.  I tried changing  "Executable Types in PKGs" from "Automatically detect executable types" to "One or more executables require Rosetta" but that doesn't seem to work for me.  Also I made sure the application has full disk access via Security and Privacy.   Not sure what else to try.  Any help would be appreciated.

scottb
Honored Contributor

I'm still not seeing this issue, but when I've had issues with Composer in the past, I have moved (moved, not nuked as you lose other good things in Composer) the folder:

/Library/Application Support/JAMF/Composer

 To the desktop or other place.  Quit Composer first, move, then re-launch Composer.  See if that helps...

You'll notice that the items in the left column are gone - which is why I say don't delete it yet.

If it works now, you'll know there was something corrupted in that folder...worth a shot.