Hi, Any help is really appreciated. regards Prema Kumar

Hi @roth-izo , You have to use productbuild command to create an archive which will bundle all the child packages inside and create a main archive. productbuild --synthesize --package pkg1 --package pkg2 path/distribution.dist Once the distribution.dist file is created, you can use following command to create the final package. productbuild --distribution path/distribution.dist --package-path <path to pkg1, pkg2> --identifier com.xxx.xxx --version xxxx --sign "xxxx --timestamp /Package.pkg In the distribution.dist you can put other restriction you need. Please refer https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.html regards Prema Kumar

Hi Quinn, Thank you for the support. I am not able to include the resources folder inside the archive using the --resources option of productbuild command. Following is the command I am trying. productbuild --distribution distribution.dist --package-path cont --resources /path/resource --identifier com.abcd --version 7.2.0.01 --sign "Developer ID Installer: xxx" --timestamp test.pkg There is no error in building. After the build, if I expand the .pkg file, Resources are not included. Could you please help on this? regards Prema Kumar

Hi Quinn, Thank you. I was planning to use productbuild command to create nested packages. Could you please help on how to call preinstall and postinstall scripts in the packages created using productbuild command? regards Prema Kumar

Hi @Quinn, Do you have any update on this issue? regards Prema Kumar

Hi, Thank you for the support. Yes your understanding is correct. it fails in both the ways. regards Prema Kumar

Hi, In the bug description, I have mentioned a link to download our package. Please let me if that is not part of the message. regards Prema Kumar

Hi, Installation was working on build version 25B5042K. regards Prema Kumar

Hi, Thank you for the reply. Yes, it is affecting the older version of the product which was released few months back. New and older version of the product works on macOS 26. Our software was working on beta version of the macOS 26.1 as well. Bug id is: FB20929578 Regards Prema Kumar

Hi, Thank you for the quick response. 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

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 @Quinn, Any help? Regards Prema Kumar

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, 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