Please provide your feedback in this short Flings' survey.
Oct 28, 2022

Oddly enough, I was having the crashing issue the first day I tried this app, then a few days later it just started working for me... for the most part.

My issue is that any profile I upload using this tool that includes privacy preferences settings fails to install to the Macs. In the Troubleshooting tab for the failed devices, I see the "Install profile failed" event with the Error Code "22 In the payload (UUID: 682ca3b3-6caf-4f43-ae05-0d3d2dd87f2a), the key 'CodeRequirement' has an invalid value.".

The Bundle ID and Code Requirement in the generated WS1AA profiles are the exact same settings I get when looking them up manually using codesign and such, but if I manually create a new profile with these identical settings, the profile installs to the Macs without any errors, but the privacy preferences do absolutely nothing. I've copied the Code Requirement text from the generated profile and also copied the terminal output and pasted them into various text editors and I cannot find any differences or issues, and all of the quotation marks appear to be correct.

Another profile that I generated with WS1AA that didn't include any changes to privacy preferences installs to the Macs without issue.

Mar 04, 2022

Hi all!

I think the same crash behavior that was occurring with BigSur (before v1.2.1) is occurring with macOS Monterrey. I try to run the app, click Initial Analysis, it shows fastly some terminal windows, and crash, asking me if I want to re-open.

There is some workaround that we can apply until new version of app is not released ?

Regards

Jun 15, 2021

When trying to run the app I click on initial analysis and it opens a terminal window then crashes

Mar 16, 2021

After installing apps and approving kernel extensions and Privacy preferences I hit Final Analysis and the app just keeps crashing on Mac OS Big Sur. Has anyone experienced this and know how to fix.

Mar 22, 2021

Sixto - I believe i was able to identify this issue and (hopefully!) resolve it. Can you download the 1.2.1 version and see if that helps?

Mar 22, 2021

That Worked! thank you very much for your hard work and diligence on this!