Alert: Support for IE11 deprecating on September 8, 2020 for Authorization screens

Editor’s note: This article was updated with new information on Aug. 6, 2020. The new deprecation date is September 8, 2020.

An important change is coming to browsers when you use OAuth2 for authorizing the QuickBooks Online and/or QuickBooks Payments companies.

This is an extension of the details that were shared on the below blogs previously:

What is happening?

Due to security requirements, starting Sept. 8, 2020, only Chromium-based embedded browsers will be supported for QuickBooks Online Connection Authorization screens. In particular, Internet Explorer 11-based embedded browsers will no longer work.

For non-embedded browser workflows, Intuit’s policy is to support the previous two versions of Google Chrome, Mozilla Firefox, Microsoft Edge, and Safari (11+).

Why is this happening?

IE 11 and older versions do not support the latest features that other browsers provide. As we continue to increase the number of online applications available to QuickBooks customers, we want to make sure we continue to provide the latest browser features for our developers. This allows you, as a developer, to have access to the latest UI experiences, and creates a better experience for our mutual customers.

What will happen if I continue to use an unsupported browser?

You’ll see a message that lets you know you are using an unsupported browser.

Why is this happening now?

We are upgrading our stack to support the latest browsers so as to use their latest features and improve performance. At this time, IE11 does not support these features, so we are dropping the support for IE11.

NOTE: In the previous version of this blog, we had mentioned the possibility of moving to Edge as a way to quickly respond to this. However, subsequently some developers reported issues with Edge as well. So, officially we will support only Chromium based embedded browsers.

Do you need to change your code?

Yes. If you have an app that opens an IE11 browser instance, then you need to make a code change to use another browser.

If you are using an embedded browser control from within a desktop application (for example, the .NET Windows Form Web Browser Control – system.windows.forms.webbrowser), Java SWT Browser View, or any browser component using IE rendering engine, then you’ll need to update your code to use the Chromium instead. This code will need to be deployed to your customers prior to the Sept. 8, 2020 deadline so they are using the updated code on Sept. 8, 2020. Be sure to verify that your code is using the supported browser enabled on the machine on which your code is deployed or change your code to use any other browser implementation, and validate against the supported list of browsers shared above.

Need help with updating your embedded browser controls?

Get help on the issue on our developer support forums.

Thank you for helping us to ensure our platform is providing the best experience for all of our customers.