@apizz, @kevinmcox, I think this needs another look. The key is documented as a dictionary and changing it to array is incorrect (@DigiYann ran tests yesterday to confirm).

The previous manifest allowed entering one printer, and in the profile this was represented by a dictionary where the configured printer appeared under the key Printer. In reality this key was more akin to an identifier than to a preference key because it could be anything, and Printer was just an example provided by the manifest. Adding more printers was possible in a text editor provided that each also had its own key.

The conventional way to represent this in the manifest is by changing the example key name from Printer to {{key}}, but that would do us no good at all because such a structure is so rare that neither iMazing Profile Editor nor ProfileCreator support it right now.

I've considered suggesting that we relax the pfm_unique restriction so that users could add multiple printers by adding multiple payloads but testing showed this approach to fail as well.

Perhaps you guys have other ideas to try, but otherwise I recommend that we revert this PR and keep the issue open.

My apologies for the last comment. I wasn't clear on what you were saying, but I can see now that I made an error and that in fact the UserPrinterList dictionary contains not just other dictionaries which define printers but also a KEY for these. So the implementation "fixed" the visual issue, but subsequently has changed the format of the output payload such that this won't actually work.

Will need to make changes here to get this working again.

@apizz is anyone working on this?