本文介绍了Firebase AB测试有0个用户的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我们已经开始使用Firebase远程配置进行AB测试.已经过去了24个小时,当应该为每个变体分配成千上万的DAU时,它会显示"Total Users:0".
We've started an AB test using Firebase remote config. It's been over 24 hours, and it's showing "Total Users: 0" when there should have been tens of thousands of DAUs assigned to each variant.
- 数据输入需要多长时间?
- 有什么方法可以判断它是否正在运行?
- 如果它保持为零,潜在的根本原因是什么?为什么没有将人员分配给测试变体?
推荐答案
找到了解决方案.有一些愚蠢的错误,但很容易错过,因为远程配置无需修复就可以正常工作.
Found the solution. A few dumb mistakes, but they are easy to miss because the remote config works fine without fixing them.
- 确保将Firebase SDK/pod升级到4.5或更高版本.早期版本具有相同的API,但不会提供AB测试值(仅远程配置值)
- 确保在调用
FIRApp配置
之后调用fetchWithExpirationDuration - 在运送至应用商店之前,请先验证AB测试草案是否有效.这样做的一些技巧:
- 在调试模式下,
- 传递0使其在
fetchWithExpirationDuration
中失效,因此每次被强制获取新值(默认情况下将缓存). - 以调试模式设置远程配置(以下代码)
- Google关于如何验证的说明: https://firebase.google.com/docs/remote-config/abtest-config#validate_your_experiment_on_a_test_device
- Ensure you upgrade Firebase SDK/pod to 4.5 or later. Earlier versions have an identical API but won't serve AB tests values (only remote config values)
- Ensure you call fetchWithExpirationDuration AFTER you call
FIRApp configure
- Verify a draft AB test is working before shipping to app store. Some tips for doing this:
- Pass 0 for expiration in
fetchWithExpirationDuration
when in debug mode so it's forced to fetch new values every time (it will cache by default). - Setup remote config in debug mode (code below)
- Instructions from Google on how to verify: https://firebase.google.com/docs/remote-config/abtest-config#validate_your_experiment_on_a_test_device
#ifdef DEBUG FIRRemoteConfigSettings* remoteConfigSettings = [[FIRRemoteConfigSettings alloc] initWithDeveloperModeEnabled:YES]; [FIRRemoteConfig remoteConfig].configSettings = remoteConfigSettings; #endif
这篇关于Firebase AB测试有0个用户的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!
- Pass 0 for expiration in
- 传递0使其在