Stricter time-stamp validation on macOS 10.14
Today we released an install4j emergency release for macOS 10.14 that fixes a problem with code signing. Previous versions of install4j used time stamp validation during code-signing in such a way that it's no longer recognized by macOS 10.14.
Whenever code signatures are invalid, macOS does not report any specific errors, but just informs the user that the
archive is damaged and suggests to move it to the trash, like this:
If you use install4j for deploying to macOS, you probably do use code-signing, so we highly recommend to update to
install4j 7.0.6 to avoid problems for users on macOS 10.14.
As an added benefit, the new release can scale splash screens under fractional HiDPI on Windows, so they no longer appear to be to small.