AB Testing Beta
Incident #19002
Firebase Remote Config Experiments with A/B Testing not getting experimental variants
Incident began at 2019-12-13 10:00 and ended at 2019-12-13 13:42 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Dec 13, 2019 | 13:44 | The issue with Firebase Remote Config Experiments with A/B Testing has been resolved for all affected users as of Friday, 2019-12-13 13:42 US/Pacific. We thank you for your patience while we've worked on resolving the issue. |
|
| Dec 13, 2019 | 13:29 | We believe the issue with Firebase Remote Config Experiments with A/B Testing has been partially resolved by the rollback. Our engineering team is continuing to monitor the rollback and system metrics to ensure the service returns to normal operation We will provide an update by Friday, 2019-12-13 14:30 US/Pacific with current details. |
|
| Dec 13, 2019 | 13:13 | We are experiencing an issue with Firebase A/B Testing’s integration with Firebase Remote Config, beginning at Friday, 2019-12-13 10:00 US/Pacific. As a result, there might be an extended delay in the propagation of experiments to devices. Our engineering team has a rollback in progress which we believe will mitigate this issue. We will provide an update by Friday, 2019-12-13 14:00 US/Pacific with current details. Self-Diagnosis: Firebase Remote Config that use A/B testing only get default parameter, no experiment data being collected. Workaround: none at this time. |