Good testing catch.

For the malformed url, proper error message is displayed to the user. Please check the attached screenshots.

Riddhi Jagdish Patil Can you try entering: https://bitbucket/lorainelab/merge-annotation-operator/downloads/merge-annotation-operator-9.1.0.jar

Sameer Shanbhag, The above url throws "Internal Server error" instead of error message. This is the case when domain name is incorrect and cannot be reached even after max retries. I will handle this scenario. Thanks for highlighting it.

Issue:
Handle Malformed URL on Submit App Page

Solution:
In case of incorrect domain name for URL while submitting the app, display a proper error message to the user.

Files changed:
submit_app/processjar.py
https://bitbucket.org/rpatil14/appstore_riddhi/branch/IGBF-2025#diff

Testing steps:
Code changes deployed to https://dev-appstore-6.bioviz.org

• Scenario 1:

• Click on Submit your App button on AppStore home page.
• In Upload from URL just enter jar name without proper url path. ex. "fake-app.jar"
• Proper error message will be displayed on the UI. Refer scenario-1.png

• Scenario 2:

• Click on Submit your App button on AppStore home page.
• In Upload from URL enter incorrect url path to the jar
• Proper error message will be displayed on the UI. Refer scenario-2.png

• Scenario 3:

• Click on Submit your App button on AppStore home page.
• In Upload from URL enter incorrect domain name for the path to the jar
• Proper error message will be displayed on the UI. Refer scenario-3.png

Testing results:
Attached testing results to the ticket

Riddhi Jagdish Patil Can you please fix the Trash Icon as a part of this ticket? or should I make a new one?

Issue:
Trash Icon for URL is not activated when the field has some content.

We need to provide more user-friendly error messages.

scenario 2:

• "The file you submitted [file name] cannot be read as a zip" file is a bit weird. The user needs to upload a "jar" (java archive) file. The tooling used behind the scenes works for jar files and for "zip" files more generally, so the error message is technically correct! However, the user might get confused by this error message and think we require the file to end with "zip" not "jar".

Let's write this instead:

• "There was a problem with the file you entered - [file name]. It does not appear to be a proper "jar" (java archive) file. Try uncompressing it on your local computer to check it."

Riddhi Jagdish Patil
Sameer Shanbhag

scenario 1:

The error message for malformed URL is also a bit confusing:

• The file you submitted "Invalid URL 'fake-app.jar'. No schema supplied. Perhaps you meant http://fake-app.jar?

The term "schema" may not make sense to some people. A developer not familiar with Web programming may not realize that "schema" refers the protocol being used to transfer the data, e.g., ftp, file, http, or https. (I'm not actually sure what "schema: means here!)

Anyway, let's come up with a better error message that uses plainer language.

How about:

• There is a problem with the Web address (URL) you entered: [fill in what they entered here]. Try checking it in a Web browser to make sure it is available on-line.

Usability issues/question regarding scenario1:

• It is not clear from the screen whether the App Store has uploaded the file and tried to parse it already. Can we preserve the user's previous entries so that they can recall what they tried to enter?

Edit: Regarding my question above. This request is out of scope for this ticket and should be addressed in a new ticket.

Regarding above usability concerns:

If these can be quickly fixed with a few quick and low-risk changes, please go for it.

Otherwise, I think we should do it later - we can address these usability concerns as part IGBF-2026 or other future related ticket.

Riddhi Jagdish Patil Sameer Shanbhag - it is your call since you are closest to the code.

Pull Request Updated: https://bitbucket.org/lorainelab/appstore/pull-requests/122/igbf-2025/diff

Merged but not yet deployed on dev-appstore-2 (master)

Deployed on dev-appstore-1 for testing.

For testing please Refer the Scenarios mentioned by Riddhi Jagdish Patil

The upload from URL functionality failing when trying to upload a new app using URL for the master branch code. It throws following error
"TypeError: a bytes-like object is required, not 'str'"

Pull Request Submitted:

https://bitbucket.org/lorainelab/appstore/pull-requests/124/igbf-2025-fix-type-handling-issue/diff

Issue Observed - Once delete button is clicked and again valid jar url is entered, the same error ( "Please upload a file or Enter a URL " ) occurs.

Steps to reproduce -
1. Enter a url
2. Delete the url using the trask icon
3.Enter a valid url
4. Click on Next

Fixed and Pull Request Raised:

https://bitbucket.org/lorainelab/appstore/pull-requests/130/igbf-2025-1/diff

Merged to master. Deployed to https://dev-appstore-2.bioviz.org

Successfully tested following scenarios:
1) In Upload from URL just enter jar name without proper url path. ex. "fake-app.jar"
2) In Upload from URL enter incorrect url path to the jar ex. https://bitbucket.org/super-simple-igb-app-0.0.3.jar
3) In Upload from URL enter incorrect domain name for the path to the jar ex. https://fakebucket.org/lorainelab/super-simple-igb-app/downloads/super-simple-igb-app-0.0.3.jar
4) In Upload from URL enter incorrect, click Next, delete url using thrash icon, enter valid url and click Next

Marking this ticket done
cc. [~aloraine]