cpkuo

Results 6 comments of cpkuo

I'm getting the same issue, somewhat random. Aside from restarting the process, how can I avoid getting this error? Once its in a corrupt state, it seems only a restart...

In the meantime I've just implemented a cache check with concurrent dictionary before making a call to DeviceDetectorNET

Sure, there is still the possibility that DeviceDetector will write to it's internal cache collection on concurrent requests but this seems to have helped me in a high load environment....

So I went into the source code to match up with the stack trace for this exception and realized I was using a dotnet core version package of DeviceDetector.NET that...

I'm also getting this error. How do we work around this? Thanks!

Follow up. I upgraded to version 3.0.4 from 2.3.4 and it seems to work now. @Fashdey, what version are you on?