Post not yet marked as solved
Click to stop watching this thread.
You have stopped watching this post. Click to start watching again.
contentPostList.repliesup-voted.tooltip
No, I have removed the --deep parameter but still get the same result. Notarisation complains about the Signature of the included JRE.Command used to ckeck the DMGs signature: codesign -vvv --strict ***.dmgxxx.dmg: valid on diskxxx.dmg: satisfies its Designated RequirementPart of the content of CodeResources file<key>jre/Contents/Home/bin/java</key><dict><key>hash</key><data>5BjtH+ZNNYHVRnm4n8ILT2Gp8R8=</data><key>hash2</key><data>NXhhFRQOUk58ttqAHMmkttxkc+4hvHjolDfS7ffxSyQ=</data></dict>Part of the notarisation log:{ "severity": "error", "code": null,"path": "***.dmg/***.app/Contents/jre/Contents/Home/bin/java","message": "The binary is not signed.","docUrl": null,"architecture": "x86_64"},{"severity": "error","code": null,"path": "***.dmg/***.app/Contents/jre/Contents/Home/bin/java","message": "The signature does not include a secure timestamp.","docUrl": null,"architecture": "x86_64"},{"severity": "error","code": null,"path": "***.dmg/***.app/Contents/jre/Contents/Home/bin/java","message": "The executable does not have the hardened runtime enabled.","docUrl": null, "architecture": "x86_64" },