'convert to source" issue with Composer on Sequoia

[RaniPM]

Hello,

We are experiencing an issue with creating a pkg using Composer from a Sequoia machine. We don't have this behavior when generating a pkg from a Sonoma machine.

When we create a pkg containing a .app, for example, without anything else, no scripts, once the package is created, we can no longer open it with Composer because it gets stuck at 30% during the "converting xxx.pkg to source" phase.

We have verified that Composer has full disk access in the macOS system settings. We tried deleting the /Library/Application Support/JAMF/Composer folder, but the same problem persists.

We are using the Flat Package option and "automatically detect executable types" in Composer.

There are no problems with dmg files.

Have you encountered this type of problem before?

Thank you for your help.

[karthikeyan_mac]

Hi @RaniPM ,

We are using Composer 11.12.1 in macOS 15.2 and it works. I am able to create the package and also convert the packages to source. 

Quit Composer and then delete the com.jamfsoftware.Composer.plist from ~/Library/Preferences and give a try. 

Did you check on different Mac? 

Thanks

[RaniPM]

Thank you for your response.

I have already tried deleting the preference, but without success.

We tried on 3 different Sequoia computers (2 Intel iMacs and a Silicon MacBook Pro). 😥

[RaniPM]

When I create a pkg from a Sonoma computer, I can open it in Composer on both Sonoma and Sequoia. If I create a pkg from a Sequoia (15.2) computer, it gets stuck at 30% during the "convert to source" phase on both Sonoma and Sequoia.

So, the problem seems to occur when creating a pkg from a Sequoia computer.

I hope I'm not the only one experiencing this behavior 😥

[agungsujiwo]

Hi @RaniPM 

Have you tried re-downloading the Composer app and then installing it?

[RaniPM]

Hi @agungsujiwo 

yes, I deleted Composer and preference then re-installed with last version available in my Jamf Account but same issue.