How can I handle the accumulation of Flurries?

Question

I have an iPhone app that has relatively simple Flurry setup installed. I notice that Flurry files ("flurryResponseNNNNN ...") seem to accumulate and never be deleted (at least not returned within 3 weeks).

Now, at the end of the year, we will begin to expect some accumulation here in Minnesota, but I don't really want it before.

Is there any Flurry parameter that controls the number of files (or the total size or something else) that Flurry saves, or do I need to manage it directly in my application?

Added:

Files are in the Documents directory. They contain XML similar to:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>body</key> <data> </data> <key>headers</key> <dict> <key>Connection</key> <string>close</string> <key>Content-Length</key> <string>0</string> <key>Content-Type</key> <string>application/octet-stream</string> <key>Date</key> <string>Wed, 14 Sep 2011 19:41:25 GMT</string> <key>Server</key> <string>nginx</string> </dict> <key>statusCode</key> <integer>200</integer> </dict> </plist> 

Answer 1

I have to say that I found that these files are diagnostic logs that were turned on during setup when starting Flurry. (I forgot the specific setting and I don’t have the code here, but it’s pretty obvious when you look for it.) Disable this setting and they will disappear (or at least not be created anymore).

Answer 2

I used to use Flurry and never saw these files. Where are they stored; if it is in a folder with a cache or a temporary folder, then I will not worry about them.

Do you think flurry is working correctly when you go to your app website?

Can you tell us more about your confusion configuration? What analytics can you record?

NB Of course, I would not want to manually delete files from your application!

Answer 3

 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary*)launchOptions { [FlurryAPI startSession:@"YOUR APP KEY"]; [FlurryAPI logEvent:@"Application Started"]; [FlurryAPI setSessionReportsOnCloseEnabled:FALSE]; [FlurryAPI setSessionReportsOnPauseEnabled:FALSE]; }