1856994 - The user is prompted to start the analysis again after reopening the bottom sheet

Status: RESOLVED DUPLICATE of bug 1858018

(Fenix :: Shopping, defect, P1)

Description

[Delia Pop]

Attachment: Screenrecorder-2023-10-04-17-42-07-358.mp4

Preconditions

Make sure you have VPN connected to US.
Make sure you have developer's option enabled, and the "Shopping experience" toggle is ON.
Enroll in the Fakespot shopping experience.

Steps to reproduce

1. Open a PDP without quality reviews (without analysis) from amazon.com, bestbuy.com, or walmart.com.
2. Tap the price tag icon in the URL.
3. Tap the "Check review quality" button on the bottom sheet.
4. Once the analysis is complete, if the "No info available" error message is displayed, close the bottom sheet.
5. Tap the price tag icon in the URL again.
6. Observe the bottom sheet.

Expected behavior

When reopening the bottom sheet after previously analyzing the product, the "No info available" error message is displayed again.

Actual behavior

The user is prompted to start the analysis, after which the "No info available" error message is displayed. Closing the bottom sheet will trigger this loop again.

Device information

• Firefox version: Nightly 120.0a1 from 10/04
• Android device: any device

Any additional information?

This issue could be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1856797, however, the same behavior is present on older Nightly builds as well.

Comment 1

[Rahul Sainani [:rsainani]]

This should be fixed with Bug 1858018

Comment 2

[Chris Peterson [:cpeterson]]

QA, is this fixed in Beta 120?

Comment 3

[Delia Pop]

(In reply to Chris Peterson [:cpeterson] from comment #2)

QA, is this fixed in Beta 120?

Hi, Chris, unfortunately we cannot test the feature or verify bug fixes on Beta 120 due to issue 1861664 encountered by the Ecosystem QA team.
Our understanding is that the Fakespot feature would be enabled in Beta 120 using Nimbus and we would need to enroll in an experiment to be able to test the feature.
We are keeping an eye on this issue and we'll verify the issues fixed and uplifted to Beta 120 once the issue is fixed and the experiment is available.

Comment 4

[Chris Peterson [:cpeterson]]

I'll close this bug as a duplicate of bug 1858018. I think the issues are the same and that bug's fix was verified in Nightly 120, so I think we're good here.