Hi!
We released this patch to production this morning and have actually seen a big uptick in this exception in our logs after deploying the patch. Is there any information that we can send to you to help you guys debug the issue further?
Search found 3 matches
- Mon Mar 10, 2014 11:01 am
- Forum: ScientiaMobile WURFL Cloud Service
- Topic: .NET: String was not recognized as a valid DateTime
- Replies: 6
- Views: 10524
- Tue Feb 25, 2014 10:16 am
- Forum: ScientiaMobile WURFL Cloud Service
- Topic: .NET: KeyNotFoundException (in EnsureUserAgent)
- Replies: 7
- Views: 10107
.NET: KeyNotFoundException (in EnsureUserAgent)
Hello, We're using the .NET API. Sometimes, when we hit CloudClientManager.GetDeviceInfo(HttpContext), we get this exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at ScientiaMobile.WurflCloud.Http.CloudClient.EnsureUserAgent(String userAge...
- Tue Feb 25, 2014 10:14 am
- Forum: ScientiaMobile WURFL Cloud Service
- Topic: .NET: String was not recognized as a valid DateTime
- Replies: 6
- Views: 10524
.NET: String was not recognized as a valid DateTime
Hello, We're using the .NET API. Sometimes, when we hit CloudClientManager.GetDeviceInfo(HttpContext), we get this exception: System.FormatException: String was not recognized as a valid DateTime at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles) at ScientiaMobil...