Forum Discussion

HotCakeX's avatar
Mar 24, 2020

[Solved] Google is blocking Edge from using google drive

 

Microsoft Edge Version 82.0.459.1 (Official build) canary (64-bit)

 

 

  • HotCakeX 

     

    User Agents are getting deprecated, they can't be completely removed considering the amount of problems it will cause for older legacy websites.

     

    Freezing them will prevent the browser version from updating, similar to this:

     

    Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3764.0 Safari/537.36 Edg/75.0.131.0

     

    They will only be used to distinguish between mobile and desktop devices.

  • I used an extension to change user-agent to chrome or Firefox, then I could access google drive again.

    didn't have to update anything after all

  • HotCakeX can you tell me exactly how you go to that error message? When I go to drive.google.com it works as expected with no warning signs.

     

    -John

     

    • HotCakeX's avatar
      HotCakeX
      MVP

      johnjansen 


      johnjansen wrote:

      HotCakeX can you tell me exactly how you go to that error message? When I go to drive.google.com it works as expected with no warning signs.

       

      -John

       


       

      I can make a video but i believe it's not necessary (unless you want to). but I go here: https://drive.google.com

      and then I get that message.

      Microsoft Edge Version 82.0.459.1 (Official build) canary (64-bit)

       

      I'm not doing anything special. it happens also if I type "google drive" in Bing and go from there.

    • HotCakeX's avatar
      HotCakeX
      MVP

      johnjansen 

      By the way it also happens in InPrivate mode. first it asks me to enter my email and pass, then 2step verification and then shows me that message.

      • johnjansen's avatar
        johnjansen
        Icon for Microsoft rankMicrosoft

        HotCakeX I have not been able to repro this, and it's really frustrating. Typically, what we see is that google will change a library somewhere internally that has a hard-coded string for UA string checking; when we find we are being blocked, we ping someone over there and they fix it.  

  • obermd's avatar
    obermd
    Copper Contributor

    HotCakeX 

     

    I see a possible pattern here.  A couple of weeks ago Google announced that Chromium based Edge isn't secure.  But that would also imply that Chrome isn't secure since they share a lot of the codebase.

Resources