Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2026

Improve submit app confirmation page to better inform user what is happening

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Story Points:
      2
    • Sprint:
      Fall 4 : 30 Sep to 11 Oct, Fall 5 : 14 Oct to 25 Oct, Fall 6 : 28 Oct to 8 Nov

      Description

      When developers upload an App, App Store must perform first-level automated review of the App to make sure it follows basic specifications. For example:

      • Jar file must contain OBR index file called "repository.xml" at the top level of the jar
      • Jar file MANIFEST must contain OSGi headers of Bundle-SymbolicName, Bundle-Version, and Bundle-Name (note that Bundle-Description is optional)
      • An uploaded jar file can have the same Bundle-SymbolicName and same Bundle-Version as a currently "pending" App, but not a released App
      • An uploaded jar file can have the same Bundle-SymbolicName as a released App but its Bundle-Version should be different

      All the various combinations of what a developer can do are kind of complicated, and our current submit app feedback page does not do a great job of explaining what's happening when a developer submits an App jar. For example, we are telling the developer whether the uploaded jar file is a "new app," but there are several ways that an App can be new!

      Let's change the feedback page as follows:

      Instead of displaying the line: "Is the is a new App" and then showing either "Yes" or "No", let's instead display a different line: "App Summary" and provide some text explaining what we think the developer is doing. If the developer reads this text, they will be able to decide whether to proceed with the next step of either canceling the submission or proceeding with submission.

      For the new design, please see this PowerPoint:

      https://www.dropbox.com/s/xe1v2jo17fg23th/SubmitApp-JarUpload.pptx?dl=0

      (This is the same PPT as for IGBF-1995, but with new slides added.)

        Attachments

          Issue Links

            Activity

            Hide
            ann.loraine Ann Loraine added a comment -

            Deployed on https://dev-appstore-2.bioviz.org and ready for testing.

            Show
            ann.loraine Ann Loraine added a comment - Deployed on https://dev-appstore-2.bioviz.org and ready for testing.
            Hide
            shamika Shamika Gajanan Kulkarni (Inactive) added a comment -

            Tested the different scenarios as mentioned above. My observations are as follows:
            The scenarios 1,2 and 3 are working perfectly fine. For scenarios 4 and 5, the message being displayed is "all-new app" message. The scenarios are as follows.
            Scenario 4:
            Submit an app and do not release it. Submit the same app with same Bundle_Name and Bundle_Version.
            Excepted output - The summary page should display "jar replacement" message

            Scenario 5:
            Submit an app and release it. Submit an app with same Bundle_Name but different Bundle_version
            Excepted output - The summary page should display "not yet released app" message

            Moving the ticket to To-Do. Kindly check the issue.

            Show
            shamika Shamika Gajanan Kulkarni (Inactive) added a comment - Tested the different scenarios as mentioned above. My observations are as follows: The scenarios 1,2 and 3 are working perfectly fine. For scenarios 4 and 5, the message being displayed is "all-new app" message. The scenarios are as follows. Scenario 4: Submit an app and do not release it. Submit the same app with same Bundle_Name and Bundle_Version. Excepted output - The summary page should display "jar replacement" message Scenario 5: Submit an app and release it. Submit an app with same Bundle_Name but different Bundle_version Excepted output - The summary page should display "not yet released app" message Moving the ticket to To-Do. Kindly check the issue.
            Hide
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment -

            Scenario 5 was working as expected. Fixed scenario 4
            Fixed bug in below branch:
            https://bitbucket.org/rpatil14/appstore_riddhi/branch/IGBF-2026-BugFix#diff

            cc. [~aloraine], Shamika Gajanan Kulkarni

            Show
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment - Scenario 5 was working as expected. Fixed scenario 4 Fixed bug in below branch: https://bitbucket.org/rpatil14/appstore_riddhi/branch/IGBF-2026-BugFix#diff cc. [~aloraine] , Shamika Gajanan Kulkarni
            Show
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment - Pull request submitted: https://bitbucket.org/lorainelab/appstore/pull-requests/150/igbf-2026-bug-fix-to-display-replacement/diff
            Hide
            noor91zahara Noor Zahara (Inactive) added a comment -

            Working as expected.

            Show
            noor91zahara Noor Zahara (Inactive) added a comment - Working as expected.

              People

              • Assignee:
                rpatil14 Riddhi Jagdish Patil (Inactive)
                Reporter:
                ann.loraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: