| Issue |
Description / Workaround |
| 2492: Testing different versions of the same applications may result in an already installed error. |
Description: Create a paid application. Buy it, install it, and launch it in the Store Preview. Create a new version of the same application and try to buy, install and launch it again. An already installed error message is displayed.
Workaround: Clear the Java cache or use the Preview option instead of Buy. |
|
| 2464: The preview of a new version of an application still shows the graphics of the previous version. |
Description: If you created new a version of your application including new graphics, the graphics might not be displayed in the Store Preview. The new version of your application, including the updated graphics, will be available in the Java Store client once the new version of the application has been published.
Workaround: None |
|
| 2460: Comment isn't saved without using the Save for Later option. |
Description: If an application is resubmitted without a comment, the user receives an error, "Errors prevent submission. Correct the indicated errors before resubmitting".
Workaround: Enter a comment before clicking Submit, otherwise choose Save for Later, re-enter the comment and click Submit. |
|
| 2443: Developers cannot run more than one Store Preview at once. |
Description: If a developer tries to run a second Store Preview without first closing the original instance, the second Store Preview will fail.
Workaround: Run one preview at a time. Close the previous preview instance before running the next one. |
|
| 2140: Skipping image entry fields, when entering images during application submission, results in the wrong images being shown in the client. |
Description: Screenshots entered out of order (e.g. screenshot 1 and screenshot 5 only) during the submission of an application, the correct images may not be visible in the Java Store client.
Workaround: Submit screenshots in order (e.g. screenshot 1, screenshot 2 and screenshot 3). |
|
| 1971: The email sent to a developer whose membership fees were waived contains text requesting payment of membership fees. |
Description: The email notifying a developer of his approval to submit applications to the Java Warehouse requests that the membership fee be paid, whether or not the fees were waived.
Workaround: None. |
|
| 1948: The short description text may be partially obscured, in the developer portal, if the text exceeds the 90 character limit. |
Description: If the short description entered for an application exceeds the 90 character limit, the text of the description may be partially obscured when viewed in the Developer Dashboard. The text will be displayed correctly in the Java Store client.
Workaround: None. |
|
| 1678: Newly published applications are not displayed in the Java Store under its assigned category. |
Description: Newly published applications are not quickly displayed in the Java Store under its assigned categories after it has been published.
Workaround: The applications are listed under the assigned categories approximately 1 hour after they have been published. |
|
| 1001: The Submit for Review button becomes active on the Notes page before comments are added. |
Description: When including comments with your initial application submission, clicking Submit for Review before sending the comments will submit your application without submitting the comments that you have entered.
Workaround: Click Comments before clicking Submit for Review to include your comment with the submission. |
|
| 980: The Make Changes option withdraws the application from the Review state. |
Description: Clicking the Make Changes option for an application removes it from the Submitted for Review state with no notification, in some browsers, and your application will not be reviewed.
Workaround: If you click Make Changes, click Submit for Review again when your changes are complete. |
