Accept incoming network connections?

I have a package which is signed and notarized.

Do you mean an installer package? And thus the FieryAppsCloudConnector app from your second screen shot is installed by that installer package?

Oh, and what version of macOS are you testing this on?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi Quinn,

Package is a dmg, which contains different .pkg files. dmg is notarized. One of the pkg has installed FieryAppsCloudConnector app. This happens on macOS 12, 13, 14 and 15 beta as well.

Regards

Prema Kumar

Are you testing this an a ‘clean’ machine? If not, please try that and let me know what you see.

I often see problems like this when folks test their final product on their development machine. It’s best to test on a separate machine, one that’s never seen your software before. I usually run tests like this using a VM, restoring the machine from a ‘clean’ snapshot between each test. For an example of that process, see my Testing a Notarised Product.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi Quinn,

I have tried the installation of my package on a fresh macOS 14.5 VM. Downloaded the package, disconnected the network. I could install and launch the application without any issue. I did not observe the firewall popup as well. I have tried following command on the app and bundle as well. These commands executed successfully.

spctl -a -t exec -vvv

codesign -vvvv -R="notarized" --check-notarization

On other machines, I could see the firewall popup for the same .

Regards

Prema

Hi @Quinn,

Any help?

Regards

Prema Kumar

Hi Quinn,

Raising a DTS request will help? This is affecting our software releases to customers because this is a behaviour change.

Regards

Prema Kumar

Hi @DTS Engineer ,

I could identify the root cause. We have changed the developer certificate recently with a new company name. When the older applications were installed, corresponding firewall entries were added to exception list. When new version of the same application with new certificates gets installed, the firewall entries were not modified for the new applications. Hence the popup was coming. When I have removed the older firewall entries, and reinstalled the applications, the issues got resolved.

Regards

Premak

We have changed the developer certificate

Yeah, that’d do it. Thanks for closing the loop here.

Oh, and sorry for not responding earlier. I missed your previous replies for some reason )-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"