怎么每次prevent穗乱舞用户活动的新版本是被推到应用程序商店

问题描述

我们目前正在使用我们的iOS应用分析乱舞。我们已经发现了一个经常性的现象，每次我们提出我们的应用程序的新版本的应用程序商店..时间，每当我们做到这一点，我们看到了一个尖峰的用户活动乱舞上图：

WE currently use flurry for our iOS app analytics.. we've discovered a recurrent phenomenon every time we submit a new version of our app to the app store.. whenever we do that, we see a spike in the user activity graph on Flurry:

我们必须使我们的构建配置，这样就没有发展过测试，使其在乱舞督促程序（我们创建一个用于测试的开发版本）..这就是我们在我们的 - （BOOL ）应用：（*的UIApplication）的应用didFinishLaunchingWithOptions：（可为空的NSDictionary *）launchOptions 方法：

We have our build configurations made so that no development testing ever make it to the prod app on flurry (we created a dev version for testing).. this is what we have in our - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(nullable NSDictionary *)launchOptions method:

#ifdef RELEASE
    NSLog(@"launching app in RELEASE
    [Flurry startSession:@"RELEASE-APP-KEY"];
#else
    NSLog(@"launching app in NON-RELEASE mode");
    [Flurry startSession:@"NON-RELEASE-APP-KEY"];
#endif

和我们的测试确保在非释放模式推出的应用程序显示出来时，他们正在做测试X code'S控制台上。

and our tests ensure that launching app in NON-RELEASE mode shows up on Xcode's console whenever they're doing testing..

进一步..只要应用程序启动。我们也有 didFinishLaunchingWithOptions 方法内到我们的服务器调用，检查应用程序的版本（即 /应用/ IOS / version_state ）..过程中乱舞穗期间将在我们所有的日志..我们找不到与版本乱舞单个请求是表示秒杀..

further.. as soon as the app launches.. we also have inside the didFinishLaunchingWithOptions method a call to our server that checks the app version (ie /app/ios/version_state).. going over all our logs during the spike period in flurry.. we couldn't find a single request with the version flurry is showing the spike in..

任何想法，这可能是怎么回事？

Any idea what this may be all about?

会不会是乱舞正在做一些奇怪的缓存行为，或者每当被上传到苹果商店的苹果..运行，检查是否启动应用在所有的一些自动测试？

could it be that flurry is doing some weird caching behavior or that whenever an is uploaded to apple store.. apple runs some automatic tests that checks if the app launches at all?

推荐答案

我的乱舞集成团队工作。我会检查，如果你有 setBackgroundSessionEnabled 。

I work with the Flurry Integration team. I would check if you have background sessions on setBackgroundSessionEnabled.

什么可能发生的是，当所有用户自动更新，后台会话正在拉开序幕，导致你在新版本中看到秒杀。

What might be happening is that as all of your users auto-update, a background session is being kicked off, causing the spike you're seeing on the new version.

这篇关于怎么每次prevent穗乱舞用户活动的新版本是被推到应用程序商店的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！