jpackage OS/X --app-image signing

[Michael Hall]

> On Sep 6, 2022, at 4:52 PM, Michael Hall <mik3hall at gmail.com> wrote:
> 
> 
> 
>> On Sep 6, 2022, at 4:48 PM, Alexander Matveev <alexander.matveev at oracle.com> wrote:
>> 
>> Hi Michael,
>> 
>> Did you generate application image with same JDK version (19+36-2238)? With latest JDK version .jpackage.xml file should be present. We do not support signing of application images generate by another versions of JDK. It should be same JDK.
>> 
>> Thanks,
>> Alexander
>> 
> 
> Alexander,
> 
> Should of been. I installed the jdk, deleted the app and recreated, then tried to sign.
> 
> I’ll repeat to make sure I didn’t mix it up somehow.
> 

My mistake. I usually always have the jpackage build script set to use the current installed jpackage but I had changed this one to use a built GitHub version which was a jdk 20.

However, there do seem to still be remaining issues. 

The codesign verify still seems to indicate an error.

codesign -v --verbose=4 "/Volumes/BlackJack Blastoff_Unsigned/BlackJack Blastoff_Unsigned.app"
/Volumes/BlackJack Blastoff_Unsigned/BlackJack Blastoff_Unsigned.app: a sealed resource is missing or invalid
file added: /Volumes/BlackJack Blastoff_Unsigned/BlackJack Blastoff_Unsigned.app/Contents/app/.package


Also I didn’t seem to get the expected small icon for the application. I put a screenshot of the window at http://mikehall.pairserver.com/ScreenShot.png <http://mikehall.pairserver.com/ScreenShot.png>
It seems to be correct in the dmg.

And I still don’t see where I have the .jpackage.xml in the current directory.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/core-libs-dev/attachments/20220906/25b18db2/attachment.htm>