<AWT Dev> Java 8 updates are causing "Apps that use non-public APIs will be rejected"
Dr. Michael Paus
mp at jugs.org
Tue Nov 17 18:50:19 UTC 2015
Just in order to better understand this issue and the fix. Does this
mean that the packager
will now ALWAYS delete the libjfxwebkit.dylib when building a DMG file?
That would mean
that I could not bundle and distribute any application anymore for the
Mac which uses
a WebView. Have you considered the fact that many people do bundle their
have their own distribution channels and do not upload the apps to the
There should at least be some switch to override this behavior.
Just my 2+1/2 cents.
Am 17.11.15 um 18:31 schrieb Kevin Rushforth:
> [taking awt-dev off of this thread]
> The fix that was put into 8u72-b02 is that the packager will no longer
> include libjfxwebkit.dylib in the packaged app. Is this not working
> -- Kevin
> Sergey Bylokhov wrote:
>> I think openjfx-dev at openjdk.java.net (cc) is correct place to ask
>> this question.
>> On 16.11.15 23:10, Ondřej Kvasnovský wrote:
>>> We are facing to an issue with latest Java updates when we try to
>>> release apps into Apple app store. I have described the issue here,
>>> all my findings:
>>> In short, the issue is that we are not able to release Java app into
>>> store since 1.8_60 because it uses private API (see the link above if
>>> you want to know how to verify that).
>>> I spoke about this issue with Martijn Verburg and he pointed me to
>>> two issues:
>>> https://bugs.openjdk.java.net/browse/JDK-8138650 - fixed for 8u72
>>> https://bugs.openjdk.java.net/browse/JDK-8138652 - permanent fix for 9
>>> (replace private libs with public ones)
>>> I have downloaded that jdk1.8.0_72 b05 JDK and run (downloaded from
>>> otool -L
>>> | grep icu
>>> /usr/lib/libicucore.A.dylib (compatibility version 1.0.0, current
>>> version 51.1.0)
>>> And it the issue is still there, Build b05 still references private
>>> I could even try to build and app and try to publish it for code review
>>> by Apple... but since there is this reference, I do not believe it is
>>> going to be successful.
>>> Since this issue https://bugs.openjdk.java.net/browse/JDK-8138650 is
>>> considered to be fixed, but it seems it is not, could someone help with
>>> Best wishes,
>>> Ondrej Kvasnovsky
More information about the openjfx-dev