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

App Store showing version installed that really isn't

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Noted in https://jira.transvar.org/browse/REL-40 by Shamika Gajanan Kulkarni:

      See REL-40 for screen shot.

      "6) After releasing 3.0.0 version of this app which is compatible with IGB 10.0.0 and not with IGB 9.1.0, I could still see an option of installing the app when IGB 9.1.0 was running. After clicking on 'Install this App' the version 2.0.0 which is compatible with IGB 9.1.0 got installed. The button also changed to 'Installed' on Appstore, though a higher version of App was released on Appstore. Basically, on Appstore, it showed Installed even when the higher version was not compatible with IGB 9.1.0 and the higher version was not actually installed."

      Loraine comment:

      When App Store javascript hits the localhost IGB App Store endpoint, it should check Bundle-Version of the App and ensure that the button displays "Installed" only if that particular version of the App (shown in App Store) is installed.

        Attachments

          Issue Links

            Activity

            Hide
            aloraine Ann Loraine added a comment -

            Riddhi Jagdish Patil - can you look at this one next? (Downloads issue is less important.)

            Show
            aloraine Ann Loraine added a comment - Riddhi Jagdish Patil - can you look at this one next? (Downloads issue is less important.)
            Hide
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment - - edited

            Code changes present in branch :
            https://bitbucket.org/rpatil14/appstore_riddhi/branch/IGBF-2167-

            Testing scenario:
            Scenario 1:
            1) Submit an app compatible to IGB-9.1.0.
            2) Start IGB-9.1.0
            Output - Install App button should be displayed

            Scenario 2:
            1) Submit an app compatible to IGB -10.0
            2) Start IGB-9.1.0
            Output - Button Get Latest IGB should be displayed

            Scenario 3:
            1) Submit an app compatible to IGB -10.0
            2) Start IGB-10.0.0
            Output - Install App button should be displayed

            cc.Ann Loraine

            Show
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment - - edited Code changes present in branch : https://bitbucket.org/rpatil14/appstore_riddhi/branch/IGBF-2167- Testing scenario: Scenario 1: 1) Submit an app compatible to IGB-9.1.0. 2) Start IGB-9.1.0 Output - Install App button should be displayed Scenario 2: 1) Submit an app compatible to IGB -10.0 2) Start IGB-9.1.0 Output - Button Get Latest IGB should be displayed Scenario 3: 1) Submit an app compatible to IGB -10.0 2) Start IGB-10 .0.0 Output - Install App button should be displayed cc. Ann Loraine
            Hide
            aloraine Ann Loraine added a comment -

            Please see comment on your branch. I have some concerns about how the platform_compatibility string is being used. It is editable by the submitter and should not be used to dictate button behavior and appearance. However, it is very possible I misunderstand the code!

            Let's talk about it first thing tomorrow.

            cc: Riddhi Jagdish Patil

            Show
            aloraine Ann Loraine added a comment - Please see comment on your branch. I have some concerns about how the platform_compatibility string is being used. It is editable by the submitter and should not be used to dictate button behavior and appearance. However, it is very possible I misunderstand the code! Let's talk about it first thing tomorrow. cc: Riddhi Jagdish Patil
            Hide
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment -

            Yes, platform_compatibility is the string which is editable by user. But there is no other way in App Store other than platform_compatibility to identify the App compatibility with IGB.
            Allowing user to edit that field can introduce error and can impact installation of the app.

            We can have different solutions to prevent human errors to platform_compatibility:
            1) Not allow user to change the platform_compatibility string. If user identifies any error in the string, he can email AppStore admin to change to the required platform_compatibility string. (Less efforts required for development)
            2) Pre-populate the drop-down with available IGB versions and allow user to select one or many from the list (This option as discussed will need constant update to app store whenever a new igb version is added. Can be done using some REST service)
            3) Add validation checks in AppStore to make sure the platform_compatibility string entered by user is correct.

            cc. Ann Loraine, Sameer Shanbhag

            Show
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment - Yes, platform_compatibility is the string which is editable by user. But there is no other way in App Store other than platform_compatibility to identify the App compatibility with IGB. Allowing user to edit that field can introduce error and can impact installation of the app. We can have different solutions to prevent human errors to platform_compatibility: 1) Not allow user to change the platform_compatibility string. If user identifies any error in the string, he can email AppStore admin to change to the required platform_compatibility string. (Less efforts required for development) 2) Pre-populate the drop-down with available IGB versions and allow user to select one or many from the list (This option as discussed will need constant update to app store whenever a new igb version is added. Can be done using some REST service) 3) Add validation checks in AppStore to make sure the platform_compatibility string entered by user is correct. cc. Ann Loraine , Sameer Shanbhag
            Show
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment - Code changes are present in branch: https://bitbucket.org/rpatil14/appstore_riddhi/branch/IGBF-2167-#diff cc. Ann Loraine
            Hide
            aloraine Ann Loraine added a comment -

            Submit PR please.

            Show
            aloraine Ann Loraine added a comment - Submit PR please.
            Show
            rpatil14 Riddhi Jagdish Patil (Inactive) added a comment - Pull request submitted: https://bitbucket.org/lorainelab/appstore/pull-requests/182/igbf-2167/diff cc. Ann Loraine
            Hide
            aloraine Ann Loraine added a comment -

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

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

            Tested the ticket successfully as per the steps mentioned by Riddhi Jagdish Patil and the steps I had followed earlier. Working as expected. Moving to closed.

            Show
            shamika Shamika Gajanan Kulkarni (Inactive) added a comment - Tested the ticket successfully as per the steps mentioned by Riddhi Jagdish Patil and the steps I had followed earlier. Working as expected. Moving to closed.

              People

              • Assignee:
                rpatil14 Riddhi Jagdish Patil (Inactive)
                Reporter:
                aloraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: