Share via

Edge for Android

Anonymous
2024-04-23T10:51:25+00:00

Strangest thing is happening.
We assign Edge (Stabile version) to our dedicated android devices with Azure AD.
Yesterday version 124.0.2478.50 (247805005) of Edge AI Browser was starting to install on our devices and we ran in to a problem instantly. The app shows a screen saying "Sign in to sync" and Add account. Normally edge should just automatically sign in to the signed in users account (SSO). Pressing the "Add account" button results in that the app is just "thinking" spinning blue circle and nothing more happens.

The most strange thing is that the official version according to Google Play and Microsofts release notes is 123.0.2420.102 (242010205). And if you Google "124.0.2478.50 (247805005)" you get information about Edge BETA, which we dont have assigned to our devices.
How can ver 124.0.2478.50 (247805005) be installed on our devices in the first place?
Testing the exact same thing in our QA tenant, we just see ver 123.0.2420.102 (242010205)

Clearing app cache does not help by the way

Anyone experiencing this? Any ideas why?

Microsoft Edge | Profile, sync, and sign in | MacOS

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

10 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-04-29T21:32:17+00:00

    We are having this same issue and it is breaking our setup. Currently getting version 124.0.2478.62, and SSO is broken from managed home screen and users can't sign into sync either. Need this sorted ASAP as its causing big issues on our managed devices.

    EDIT: I have raised a support request about this, also mentioned that the save passwords stopped working too, https://www.reddit.com/r/MicrosoftEdge/comments/1bxhh7l/edge\_beta\_on\_android\_cant\_tap\_on\_saved\_passwords/

    EDIT 2: Still seems to be broken in 124.0.2478.71

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-05-01T06:56:14+00:00

    Any updates on the situation?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-04-29T11:44:41+00:00

    We, and our customers, are experiencing the same issues atm, please give us an update @Microsoft.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-04-29T10:52:03+00:00

    Chapter 2
    A day later we realized that Edge was updated again, and the version was back to 123.0.2420.102 and SSO was working. We quickly uninstalled Edge on all our devices and reinstalled it again, problem solved... temporary.

    Chapter 3. Tonight Edge was updated again (on Google Play) to version 124.0.2478.62 and now the SSO issue is back!!!

    THIS IS A VERY SERIOUS ISSUE CAUSING SEVERE ISSUES!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-04-23T12:27:31+00:00

    The version (Stable) 123.0.2420.102 (242010205) auto signs in the user into Edge when using Sessions on Azure AD Shared Devices. However we got the Beta? 124.0.2478.50 (247805005) instead of the stable version as Niklas says so it will break the feature auto sign in the user into Edge when using Sessions on Azure AD Shared Devices with Microsoft MHS

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments