[Experiment][iOS] The Sponsored and Non Sponsored results are not triggered when the client is enrolled in the Treatment B branch of the experiment - Githubissues

mozilla-mobile / firefox-ios

Firefox for iOS

Mozilla Public License 2.0

12.21k stars 2.93k forks source link

[Experiment][iOS] The Sponsored and Non Sponsored results are not triggered when the client is enrolled in the Treatment B branch of the experiment #21506

Open data-sync-user opened 2 months ago

data-sync-user commented 2 months ago

[Affected versions]:

Firefox Release 129.0 (build 44146) - build downloaded from TestFlight.

[Affected Platforms]:

iOS 17.5.1 - iPhone SE.
iOS 17.4.1 - IPhone Mini

[Prerequisites]:

Have the Firefox app installed on the device.
Be connected to a wi-fi network.
Have the device plugged in a charger.

[Steps to reproduce]:

Open the Safari app and paste the link from +here+ to enroll in the Treatment B of the “Enhanced Cross-Platform Suggest [iOS] - Re run 129” experiment.
Wait for a few minutes until the suggestions are ingested.
Focus the urlbar and type any sponsored keyword (e.g.: michael kors, kindle unlimited, etc).
Observe the behavior.

[Expected result]:

The Sponsored result is successfully triggered in the Firefox Suggest section.

[Actual result]:

The Sponsored result isn’t triggered in the Firefox Suggest section.

[Notes]:

We’ve tried to trigger the Sponsored results for about 5 hours by having the device plugged to a charger and with a stable wi-fi connection with no success. However, by using the “Ingest new suggestions now” option from the Secret Menu we’ve been able to successfully trigger the Sponsored results.

┆Issue is synchronized with this Jira Bug

data-sync-user commented 2 months ago

➤ Alice Varro commented:

We managed to trigger the sponsored and non sponsored results by enrolling in the experiment and leaving the app in the background for several hours or days (in some cases) while the device was connected to the charger and to a stable internet connection. After a conversation with the engineering team we’ve come to the conclusion that the OS schedules when to start the ingestion task and not the app itself. That being said, I’m marking this issue as Closed. Thank you!