Hi Michael, Did you modified app image after it was signed and before DMG was created? If yes, it is expected behavior and we will not sign app image when generating DMG.
Can you provide all steps you did to get to issue below? Thanks, Alexander > On Jun 22, 2022, at 1:51 PM, Michael Hall <[email protected]> wrote: > > Alexander, > > Sorry yet again. I really should have totally completed. While the > application verified on disk immediately after signing. The dmg version does > not appear to verify. > > codesign -v --verbose=4 /Applications/BlackJack\ Blastoff_Unsigned.app > /Applications/BlackJack Blastoff_Unsigned.app: a sealed resource is missing > or invalid > file added: /Applications/BlackJack > Blastoff_Unsigned.app/Contents/app/.package > file modified: /Applications/BlackJack > Blastoff_Unsigned.app/Contents/runtime/Contents/Home/legal/java.management.rmi/LICENSE > … > A lot of those > … > file missing: /Applications/BlackJack > Blastoff_Unsigned.app/Contents/app/.jpackage.xml > > Same result checking while still in the mounted dmg or copied into > /Applications > > Should this be working? > > java --version > openjdk 19-ea 2022-09-20 > OpenJDK Runtime Environment (build 19-ea+27-2074) > OpenJDK 64-Bit Server VM (build 19-ea+27-2074, mixed mode, sharing) > > Or should I bug report? > > Mike > > (Fwiw I remember this same signing issue from an earlier release - I could > probably track down the bug report.) > > >
