Skip to main content

Hi, all.

I'm having two huge problems with Composer (Version 11.4.1 running on an M2 MacBook Air w/ macOS 14.4.1).

  1. When I create a source, I can't see files at all to interact with them. They appear to be there (see screenshot), and I can sort of kind of navigate the filesystem inside there with the arrow keys, but I see nothing. This makes it impossible to work with Composer atm, and it's a crucial part of my Jamf workflow. Anyone here seen this or know how to fix it? I've already tried uninstalling, ripping out the Composer prefs, and reinstalling. No joy.



  2. When I try to create a source from an existing file, I'm able to do it from a .dmg, but not a .pkg. Those always fail.

Anyway, HELP! Is there maybe a beta I can try? I dunno…

This is a bug in 11.4.1 of Composer. If you install 11.4.0, it should work for you. In a ticket I submitted for this, I was told Jamf created a product issue PI117847 around this.


@SonyaLynnTwist we're seeing the same issue. @dennisnardi that fixed it, thanks! #kudosgiven


This is a bug in 11.4.1 of Composer. If you install 11.4.0, it should work for you. In a ticket I submitted for this, I was told Jamf created a product issue PI117847 around this.


You are a scholar and a gentleman. Bless you and all of your works.

That did the trick.  😀


Seeing the same issue, went back to Composer 11.4.0 and the older version is working fine.


Ran into this as well. Reverted back to 11.32.


If you don't want to revert, I found guess clicking works. So if you click around where the folders might be and land correctly, the bottom permissions is ungrayed and you can make changes.


We are also affected - back on v11.4.0 and all's fine.


Had the same issue here, went back to v11.4.0 to resolve this. Came to Jamf Nation, because we can't find anything about this in the Known Issues for Jamf Pro 11.4.1.


It looks like this is still an issue with Composer v11.4.2 as well. Have had to revert back again to v11.4.0.


It looks like this is still an issue with Composer v11.4.2 as well. Have had to revert back again to v11.4.0.


Same issue as 11.4.1

 


Issue persists with version 11.4.2


The issue is persistent in 11.5.0 as well. 


I'm starting to get a bit annoyed as Jamf is constantly introducing new bugs and not fixing them in a reasonable amount of time anymore.


I just filed a support ticket (CS1170605) …


So frustrated with this issue. Yet again I'm having to revert back to v11.4.0 of Composer due to the problem still not being fixed in v11.5.0.


The issue is persistent in 11.5.1 as well. 


I have the same issue in 11.5.1 :(


I'm starting to get a bit annoyed as Jamf is constantly introducing new bugs and not fixing them in a reasonable amount of time anymore.


I just filed a support ticket (CS1170605) …


In the reply to my support ticket, I received the following feedback, among other things:


This is a Product Issue that we are aware of (PI117847). As a workaround, we suggest admins revert to previous version of Composer restores all files and data view. It will be resolved in 11.6.0.


Recon discontinued, Admin discontinued, Composer broken for multiple versions in a row (despite updating the version # as if to lead you to believe it may be fixed).  At this rate, I wouldn't be shocked if Composer gets the axe.  Probably cheaper for them to do rather than QA.


I had a problem with Composer creating DMG files larger than about 2GB.  It was caused by Defender getting in the way.  If you have anything on the machine that intercepts file operations, see if that is the cause of your problems.


Fixed in 11.6.0!


nope unfortunately just got the error on 11.6.0

 


nope unfortunately just got the error on 11.6.0

 


Thank you

 


Reply