Skip to content

Missing code signatures in builds newer than 25.0.3-b496.62 for macOS cause notarization failure #613

Description

@derreisende77

Working: JBR 25.0.3-b496.62
• Failing: all newer JBR 25.0.3 builds
• Notarization issue:

jre.bundle/Contents/MacOS/libjli.dylib The signature of the binary is invalid.

Apple Notarization rejects app binaries built with install4j when jre.bundle/Contents/Home was only signed with a valid developer id. This worked without problems with all JBR 25 releases before and including 25.0.3-b496.62.

Observation: Newer unpacked JDKs lack code signatures that the working b496.62 build contains.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions