Flurry 4.2.2 SDK does not send session data in iOS

Question

I know that there is a delay in the Flurry reports, but the next day we do not see the results of the Flurry report.

[Flurry setDebugLogEnabled:YES]; [Flurry setLogLevel:FlurryLogLevelDebug]; [Flurry startSession:_appSettings.flurryAppId]; [Flurry setSessionReportsOnCloseEnabled:YES]; [Flurry setSessionReportsOnPauseEnabled:YES]; [Flurry setEventLoggingEnabled:YES]; UIDevice *device = [UIDevice currentDevice]; [Flurry logEvent:@"SESSION_START" withParameters:[NSDictionary dictionaryWithObjectsAndKeys:[device systemVersion], @"OS", nil] timed:YES]; 

Our logs display individual Flurry log calls that are part of the application. What we do is NOT , see Anything suggesting that the information be sent to Flurry.

Both setSessionReportsOnPauseEnabled: and setSessionReportsOnCloseEnabled: set to YES , but there is no connection to Flurry session data when the application is paused or closed. When I restart the application, Flurry tries to send session data, unfortunately, it leads to:

 FlurrySession: Add crashed former session 

As indicated, we started the Flurry session at:

 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions method of your AppDelegate 

According to the Flurry website, we do not track any Events .

We use the Flurry 4.2.2 SDK

Answer 1

A problem that seems unique to Flurry SDK 4.2.2:

In 4.2.2, a new method appeared:

 + (void)setBackgroundSessionEnabled:(BOOL)setBackgroundSessionEnabled; 

It is automatically installed on YES if there is UIBackgroundModes for your application. Our app uses GPS in the background. Therefore, Flurry will never send session data when going to the background.

When I click [Flurry setBackgroundSessionEnabled:NO]; , then it sends the session data when you click the Home button, and the application goes to the background.

I'm not sure how this could work otherwise. We don’t need to use Flurry to update GPS locations so that now it can work for us.

Hope this helps others deal with this issue.

Update: 6/17/2014:

I found more about this in the Flurry FAQ