As with every new release of software, things change. And, like we all expected, there wasn't an exception to that rule when Microsoft introduced Internet Explorer 10 into the mix.
Everyone coding for the web had the normal things to worry about, of course, like design formatting, speed, and support, but one of our clients experienced something that would have taken a long time to catch if they hadn't been using Exceptionless' real-time error reporting.
Who Adopts New Versions of IE Right Away, Anyway? #
Like many, the client's web team doesn't necessarily adopt the latest version of IE right away, much less use it as their main browser. Unfortunately, that leads to little immediate exposure to potential bugs.
Lets explore how this came back to bite them, and how Exceptionless helped them treat the wound quickly.
A nasty customer-facing error #
Users of the client's eCommerce platform that were already using IE10 were able to view and use the website fine, until they logged in. At that point, everything broke. They couldn't checkout, browse, or submit contact forms.
Because the team wasn't using IE10 regularly yet for testing actual logged-in user transactions, they were clueless!
Luckily, Exceptionless reported the customers' errors and the team was able to take notice of the recurring bug within days, rather than weeks or months.
Turns out... the problem was server-side! #
After the error was reported in the Exceptionless Dashboard, the team was able to use the attached details to trace the root of the issue back to the server's definitions of which browsers support modern cookie encryption.
All the server needed was a routine update that had not been performed! Bam - fixed.
Another bug bites the dust #
We love to hear stories like this. Something so simple, yet so easy to overlook and cause serious customer-facing problems!
Errors like this happen every day to hundreds, if not thousands, of small, medium, and large software teams across the world. We just want to help squash as many of them as we can!