Eclipse Community Forums: Eclipse JustJ » JustJ App Store signing issue

Home » Eclipse Projects » Eclipse JustJ » JustJ App Store signing issue(Unable to upload RCP app to App Store due to signing requirements.)

Show: Today's Messages :: Show Polls :: Message Navigator

JustJ App Store signing issue [message #1853651]

Tue, 12 July 2022 12:55

Ralph Bosson

Messages: 16
Registered: July 2009

Junior Member

Apples signing rules for Apple App Store require a unique Bundle Identifier in info.plist within an application. Uploading a signed, hardened, sandboxed RCP application that contains the JustJ feature presents a problem. A list of rejection errors is returned. The errors return all contain the following message "The Info.plist CFBundleIdentifier value 'net.java.openjdk.cmd' of 'jaotc' is already in use by another application." Only the 'file name' is changed 'jar', 'jarsigner', 'java', 'javax'.... I have not been able to locate the "offending" info.plists. Any guidance one might have to how I might correct this issue would be greatly appreciated. Thanks for JustJ.

Be well,
Ralph

Report message to a moderator

Re: JustJ App Store signing issue [message #1853655 is a reply to message #1853651]

Tue, 12 July 2022 15:47

Ed Merks

Messages: 33218
Registered: July 2009

Senior Member

I don't have a mac nor any mac expertise. I do know that all the macos packages here contain JustJ and the *.dmg files are signed.

https://www.eclipse.org/downloads/packages/

Doesn't your build product a *.tar file that you can inspect the info.plist there?

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: JustJ App Store signing issue [message #1853656 is a reply to message #1853655]

Tue, 12 July 2022 16:56

Ralph Bosson

Messages: 16
Registered: July 2009

Junior Member

First I hope we have all let you know that you are appreciated.

Doesn't your build product a *.tar file that you can inspect the info.plist there?

The product is an RCP Application build using Maven/Tyco 2.3.0. The .app bundle eclipse/plugin folder includes both a jar file and an un-archived folder of the jar. Info.plist are apparently embedded within the jre/bin/.. files. At least the file naming in the error messages align with the file names within jre/bin/ directory.

org.eclipse.justj.openjdk.hotspot.jre.minimal_14.0.2.v20200815-0932.jar
org.eclipse.justj.openjdk.hotspot.jre.minimal.macosx.x86_64_14.0.2.v20200815-0932

Ralph

Report message to a moderator

Re: JustJ App Store signing issue [message #1853657 is a reply to message #1853656]

Tue, 12 July 2022 18:01

Ed Merks

Messages: 33218
Registered: July 2009

Senior Member

Yes, in 7zip I can see that the executables seem to have a __TEST__info_plist embedded in them. But we do sign and ultimately notarize the the Eclipse installer and all the EPP packages all with JustJ Java 17.0.3 so more likely your problem is a result of your own root info.plist...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: JustJ App Store signing issue [message #1853658 is a reply to message #1853657]

Tue, 12 July 2022 18:07

Ralph Bosson

Messages: 16
Registered: July 2009

Junior Member

To explain more fully. The .app signs, notarize and run's as a sandbox app without issue. It can be downloaded and run today. The problem occurs when trying to make it acceptable for sale on the App Store. The applications entitlements and plist pass signing and notarization processes without error.

Report message to a moderator

Re: JustJ App Store signing issue [message #1853661 is a reply to message #1853658]

Wed, 13 July 2022 05:26

Ed Merks

Messages: 33218
Registered: July 2009

Senior Member

Sorry, I misunderstood. So it seems that somehow it's not happy that you are redistributing executables from the JRE, perhaps because those are also directly available in the store or are embedded in something else already in the store... These embedded executables come purely from the source and there is a property in the p2 metadata with the exact source URL form which the JRE was built (using jlink). E.g.,

org.eclipse.justj.url.source = https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.3+7/OpenJDK17U-jdk_x64_mac_hotspot_17.0.3_7.tar.gz

This must be a general problem anyone trying to redistribute the JRE in their application would face, so perhaps the Adoptium folks will have more experience with such a problem. Maybe opening an issue here would be good:

https://github.com/adoptium/adoptium-support/issues

Or maybe this for asking a question:

https://github.com/adoptium/adoptium-support/discussions

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator