Closed Bug 1158775 Opened 9 years ago Closed 8 years ago

An app needs to be approved two times before it is displayed in the consumer pages

Categories

(Marketplace Graveyard :: Reviewer Tools, defect, P4)

Avenir
defect

Tracking

(Not tracked)

RESOLVED WONTFIX
2015-04-28

People

(Reporter: madalin.cotetiu, Unassigned)

References

()

Details

(Whiteboard: [marketplace-transition])

Steps to reproduce:
1. Open developer hub and submit a new app.
2. Open reviewer tools and approve that app.
3. Open it's detail page in another session (another browser while being log out, or with another account that has no special permission or is not the owner/developer of the app submitted in step 1).

Expected results:
After approving, the app is available in the consumer pages.

Actual results:
After approving, the app is not available. If the user is logged in with a reviewer account the app can be approved again. After the second approval the app is displayed in the consumer pages.

Notes/Issues:
Verified in FF40(Win7) in marketplace.allizom.org
Screencast for this issue: http://screencast.com/t/kbRrAjdZ
Link for an app approved but not available in consumer pages:  https://marketplace.allizom.org/app/test-app-26ea0522/
That app is available on consumer pages for me (while not logged in).  Caching?  Maybe its not getting invalidated quick enough
At this moment that app is available for me too. 
You can see here an app that was approved 2 times: https://marketplace.allizom.org/reviewers/app/test-app-25b79ae6/
Can we confirm that this isn't solved by just waiting a few minutes? (To confirm/deny eviljeff's theory)
Flags: needinfo?(madalin.cotetiu)
Priority: -- → P4
I have tried again and after approving an app it takes aprox 10 min before the app is really approved. Until than the app has the approve/reject button available. 

Until this release the approving was almost instant.
Flags: needinfo?(madalin.cotetiu)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Whiteboard: [marketplace-transition]
You need to log in before you can comment on or make changes to this bug.