Uploaded image for project: 'AdMaxLocal'
  1. AdMaxLocal
  2. AML-1240

Client cache not clearing on 2.0.1 to 2.0.2 upgrade

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Major
          • Resolution: Fixed
          • Affects Version/s: 2.0.2
          • Fix Version/s: 2.0.2
          • Component/s: None
          • Labels:
            None
          • Environment:

            QA 2.0.2 Environment:
            Sapi build 38
            UI Build 34

          • Sprint:
            Sprint 3 - 2.0.2

            Description

            If a user has been working in AML v 2.0.1, their client UI version is AML v2.0.1.

            Upon system upgrade to 2.0.2, if that user logs in to the new system, they will be trying to access it with a cached v2.0.1 UI. This causes problems on the system since there was reseller and merchant refactoring in 2.0.2 that the 2.0.1 UI cannot handle. See AML-1234 .

            I would expect the UI to pull and cache the new UI version (2.0.2 in this case) when I log in to the upgraded system.

              Attachments

                Activity

                  People

                  • Assignee:
                    mholly Mike Holly
                    Reporter:
                    jeff.brown Jeff Brown (Inactive)
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: