Hi.
We have an app whose current version has a component that is not code signed, which in turn shows up in the login items as coming from an unidentified developer.
We did the required changes and, when doing a fresh install, said component does not show up anymore (yay!).
The problem is when doing an upgrade, from the version that has the unsigned component to the newer one, as Ventura still shows the same component with the same description even though checking the signature shows that it is code signed. Is there some extra step we need to do so that the OS updates the state and the component is not there anymore?
darioa
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
productbuild.crash
While doing the final .pkg file calling the tool:
productbuild --distribution "$DIS_FILE" --resources "$RES_DIR" --package-path "$PKGS" --version "$VERSION" "$PKG_NAME"
And the crash stack is:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libxar.1.dylib 0x00007fff2ae2c00c xar_file_new_from_parent + 190
1 libxar.1.dylib 0x00007fff2ae29d59 xar_add_frombuffer + 63
2 com.apple.PackageKit 0x00007fff3ba79a2f -[PKMutableXARArchive setData:forPath:compressed:] + 246
3 com.apple.PackageKit 0x00007fff3babb38e -[PKArchiveDistributionContainer setResourceData:forKey:forLocalization:] + 284
4 com.apple.PackageKit 0x00007fff3bab9fef -[PKMutableDistributionContainer storeResourcesAtPath:forLocalization:] + 922
5 com.apple.PackageKit 0x00007fff3baa5590 -[PKArchiveProduct(ForMutableSubclassers) addResourceDataAtPath:] + 324
6 productbuild 0x000000010efdc8a8 0x10efd8000 + 18600
7 productbuild 0x000000010efdba6e 0x10efd8000 + 14958
8 libdyld.dylib 0x00007fff204c0f3d start + 1
While using macOS 11.6.7, xcode 12.3, and CLT 11.1