Dear Chris2,
Sadly none of those options dealt with the icon in the dock nor the menu bar showing 'Java' logo. I wished they did but those options only dealt with if a dialog appeared separate from the App etc not the docking or menu bar at the top of the screen.
Dear Erel,
Thanks for responding, if anyone can find a solution I know you can. I will endeavour to explain the issue as clear as I can for your analysis.
The App issue is stated here:
The first two conflicts is easily resolved via the store metadata. The 3rd and 4th issues is the one's I'm highlighting for your kind brain storming.
In summary when we use the B4JPackager11 it works well and creates the stand alone file structure and executable. This executable works well and we have to package together as an .App and I chose to use platypus. This works nicely. I will show below what happens in each instance when you execute either the command.run right out of B4Japckager11 or the program.app via platypus.
Now the next image will show the issue stated by apple where the program bundle name on the app store differs with the name in the menu bar as well as the logo of course.
The next image shows the app launched as a program.app after platypus.
The MenuBar and Dock icon are correct but the java doc and menu bar still remains in addition to same and apple see's this as a conflict in the naming and presence. When I researched it online that's when I saw the issue being resolved to hide the Java Dock presence and also the Java Menu Bar item. The command to be used and executed just prior or that start of the javafx are:
System.setProperty("apple.awt.UIElement", "true");
System.setProperty("apple.awt.headless", "true")
System.setProperty("java.awt.headless", "true")
These if executed in the main.java at the start of the javafx routine or just in calling same they said will do the trick to achieve dockless presnce fo javax icon in the dock and menu bar.
My humble thoughts is if we can include a new header block in B4J IDE showing the main.java top block code (you may represent said block with variable names to reflect the dynamic elements of the code to maintain the high standard set by you and your team) where we can insert said code we can test the theory and if it works and I'm sure it would with your guidance we would have finally reached the status of B4j as a tool to submit to Mac Store successfully. For this major exception as all other submission issues are not dependent on B4J as B4J is compliant in all other aspects of their submission process.