How to fix Salesforce after the latest Edge update

Sinziana Mihalache
by Sinziana Mihalache
Author
0 Comments
Download PDF

  • Several users have noticed recently that they can't use Salesforce in the latest Edge version.
  • The solutions are pretty simple and can be applied by any user, as shown below.
  • Check out the latest news about Microsoft's browser in the Edge Hub.
  • Our recommendations in the Business Software Hub might come in handy if you're planning such an investment now.
Salesforce won't work after Edge update

A lot of trouble seems to have emerged after Edge rolled out the latest stable version last week (v86).

As shown recently, the changes implemented in the downloading process generated some discontent.

Similarly, users have taken to the forums to point out that Salesforce has become unusable for the past few days.

When I click on an url, a new tab is opening in a visual force page. It looks like the app lay-out is not supported or something like that.

Another user is offering more details:

I am working in the version:  86.0.622.38. It looks like the apps in Salesforce are no longer supported in the latest version of Microsoft Edge.

Quick tip:

Whenever an app proves faulty in a specific browser, the easiest solution is to test it in a different one

On this note, we’re pretty sure that Salesforce is perfectly functional in Opera.

Not only it is faster, and considerably lighter compared to Edge, but it comes with multiple exclusive features such as ad blocker, built-in messenger apps, customizable speed dials,  separate workspaces, or visual bookmarks.

The built-in free and unlimited VPN is also one of the main perks of the free, user-friendly browser.

Opera

Opera

Use Salesforce in Opera to improve your workflow and take advantage of all the exclusive features this browser offers.

How do the changes in Edge affect Salesforce users?

How do the changes in Edge affect Salesforce users?

More specifically, with the release of Edge 86, SamesSite cookies are set as SameSite=Lax by default. (Until the Edge 86 release, the default was SameSite=None; Secure. )

This means that any website using non-secure access (HTTP) is blocked and also that custom Salesforce integrations relying on cookies can’t be accessed anymore.

Salesforce has notified its users about the upcoming changes while also mentioning that all editions of Lightning Experience and Salesforce Classic are impacted.

What should I do to make Salesforce work in Edge?

fix salesforce not working on edge 86

1.Revert the changes

According to Salesforce, developers can opt in to explicitly use setting SameSite=None; Secure. However, this might affect the security of the used apps.

2. Switch to HTTPS connection

First, one can check the connection type used in their org. From Setup, in the Quick Find box, enter Session Settings, then select Session Settings.

If some sites or portals are still using HTTP connection (although the secure one should have been enabled by default), you can request the changes as follows:

  1. From Setup, in the Quick Find box, enter Sites, then select Sites.
  2. Click the site you want to edit, and ensure that the Require Secure Connections (HTTPS) checkbox is selected.

One can also run some tests in a sandbox as suggested in this Trailblazer Community article.

Note that resetting the Edge settings or clearing the browser cookies and cache will not solve the issue.

We hope that the problem is clarified now. If you have any comments on this topic, please use the dedicated section below.

We’ve also covered a similar topic with Salesforce not working in Chrome, so you might want to check that out as well.