Collapsed analytics with Windows Phone 7

Question

I included Flurry (http://www.flurry.com/) in the application for the phone 7. The only necessary code is the line when the application starts

FlurryWP7SDK.Api.StartSession(ApiKeyValue); 

However, as soon as this line gets in, the application crashes with a KeyNotFoundException. The stack trace is shown below. It looks like it is requesting isolated storage settings and does not work when the key does not exist.

Does anyone have experience with this error or even successfully integrate flurry into Phone 7 app?

 at System.ThrowHelper.ThrowKeyNotFoundException() at System.Collections.Generic.Dictionary`2.get_Item(String key) at System.IO.IsolatedStorage.IsolatedStorageSettings.get_Item(String key) at A.ca98fb38190f0d5cad84c67a779d17229.c204dba68825403c905efd7bfd067b17b(String ce0360de492f1f363775feaf6d6a8ced5, Object c8d4be677f7ee63f6756e13f285072523) at A.c3f1105d518a239d73e2236200494de25.set_cfca54db015a16ab23de44b4d5c65e9a3(String c8d4be677f7ee63f6756e13f285072523) at FlurryWP7SDK.Api.StartSession(String apiKey) at AppName.App.Application_Launching(Object sender, LaunchingEventArgs e) at Microsoft.Phone.Shell.PhoneApplicationService.FireLaunching() at Microsoft.Phone.Execution.NativeEmInterop.FireOnLaunching() 

---

Edit

After discussions with Flurry support, it turns out that KeyNotFoundException is caught by Flurry code. However, if your debugger settings are broken when an exception is thrown, you will enter the debugger independently. Ongoing execution will work because the exception is caught and handled by Flurry.

I cannot verify that this is a solution because I no longer have access to the dev environment, which indicates an error, but it seems to be a likely solution.

Answer 1

I work for Flurry. We have many successful deployments on the Windows 7 platform. You and Buju may have a new problem that previously did not find our attention. Please email [e-mail] , as the diagnosis may include a discussion of specific account information. Once we identify the root cause, we can return to this topic so that the community has the advantage of our investigation. Thanks for working with Flurry.

Edit

I just wanted to keep track of Mac comments, since KeyNotFoundException can occur in two ways during debugging. As the Mac noted that we are making a key exception, KeyNotFoundException, however, the debugger first sees the exception before we can handle it in our library. The behavior of the debugger is dictated by the setting in Debug> Exceptions.

If the checkboxes under the throw are selected, the program will be stopped and the stack trace above will be displayed. If the checkboxes under the throw are not selected, the output will generate an error similar to the following:

The first exception of type "System.Collections.Generic.KeyNotFoundException" has appeared in mscorlib.dll (this message was received by Bug)

The program will continue to follow this message because it simply serves as a notification that an exception occurred somewhere inside the program. More information about the first cases of exclusion can be found in the following articles:

What is the exception for the first case - http://blogs.msdn.com/b/davidklinems/archive/2005/07/12/438061.aspx

How to process (disable) the first random reporting - http://www.helixoft.com/blog/archives/24