Login to Express Embed not working on Safari

Report · Feb 28, 2025

We've just heard from another customer that login to Express Embed is not working on Safari on Mac, but is working on Chrome.

In Safari in Express Embed, it loops back to the login screen after logging in with a valid account. We've tested on different Macs for us here. See screen recording here that my colleague just recorded.
https://www.loom.com/share/f59cf896943f41dabf19553c726bc6a8

But in full page Express, it is fine with the same account.

We are on SDK v3. Perhaps it's that?

I'm worried that something's changed in Safari.

Please could you test at your end and see if it's the same for you for your own test Express Embed instance?

This may be related to the other thread that I just posted about students not being able to log in - we're asking about their browsers.

Attached is the Safari console log during the failure to login. I've run this past GPT, and it says:

Observed Errors from Safari Console log:

Identity Authentication Failures
- IMSProfileNameMissingError: User profile is missing the name field.
- Identity cookie not found, suggesting authentication issues.
- No identity was set on response, preventing login.
Network Access and API Failures
- Multiple Fetch API failures when loading resources from cctypekit.adobe.io, due to access control (CORS) restrictions.
- Token Error indicating an OFFLINE initialization issue.
- Failed requests to hz-telemetry.adobe.io/v1/traces, also blocked by access control.
Event Handling Issues
- EventQueue Overflow Warnings, possibly dropping log events.
- Unhandled Promise Rejection in alloy [DataCollector] preventing tracking and event logging.

Impact:

Users are unable to log in to Adobe Express Embed.
Essential authentication and API calls are failing.
Possible CORS misconfiguration blocking necessary Adobe services.

Suggested Next Steps for Adobe:

Verify IMS Authentication Flow: Ensure identity cookies and mandatory profile fields are correctly set.
Check API Access Controls: Investigate CORS restrictions blocking API requests.
Review Token Initialization Issues: Address the OFFLINE initialization error.
Resolve EventQueue Overflows: Optimize event logging to prevent dropped events.

Report · Mar 03, 2025

I can confirm we are seeing the exact same issue, both on v3 & v4 of the SDK!

Report · Mar 03, 2025

Thanks @freked, and hi from interactive video world 👋🏼

Report · Mar 03, 2025

@Ru Howe, Stornaway.io Hello, right back! 🙂

Report · Apr 04, 2025

Hello Express Embed support team,

Our team are worried not to have received a reply to this since February 28. This is an extremely urgent bug with Express Embed.

Overall, Safari makes up 10% all desktop browser use. Which is significant.

But in creative and media industries, the vast majority of users use Mac, and the majority of those use Safari.

In other words, the majority of our users use Safari and so cannot use Express Embed because of this bug.

So for people using our creative application (and for most other companies using Express Embed), it is a giant problem that you cannot login to Express Embed on Safari at the moment.

The fact that you haven't acknowledged or replied to the post (upvoted by Freked) makes me think that you haven't appreciated how much of a problem this is, or possibly haven't even registered it as an urgent bug?

If this is not a problem seen by you and others, that would be good to know asap. We are using v3 - Freked reports seeing it on v3 and on v4.

Any confirmation or update or advice would be hugely appreciated.

Thanks,

Ru

Report · Apr 09, 2025

I checked and there's a bug about slow/infitite loading in Safari in v.3 and v.4 that's being fixed currently, CCXSDK-6179 (for any Adobe employees reading this) but I'm not sure if this is related 🤔

Report · Apr 09, 2025

Thanks Erin. That sounds related. When was it logged, and how long has it been being fixed for, and do the engineering team have any idea how difficult it is and so how long it might take? I'm trying to get a sense of how to manage people's expectations here.

Report · May 07, 2025

Hi @ErinF and team,

Following up on this. We have regular customers complaining to us that our Express Embed won't log in -- because they are using Safari.

Is there work in process to fix Express Embed not working at all on Safari? And if so, how is it going and do you have an estimated time for a fix?

I know I've said it before here, but it's the browser used by the majority of Mac users, and it's not usable at all by them, so it's a huge bug.

Here is a video of what happens when Express Embed opens in Safari - it loops. Below that is the Safari dev tools console log. This user is logged into their Express account in another tab, and is able to do this fine in Chrome.

Safari Dev Tools errors when Express Embed fails on Safari.png

It would be good to know if there's a fix on the way, otherwise we're going to have to add a panel to inform all our users saying that Adobe Express doesn't work in Safari.
Ru

Report · Jun 12, 2025

Hi - we have an answer to the problem of Express Embed not working in Safari. I reported this on February 28, 3 and a half months ago. In April @ErinF said that "there's a bug about slow/infitite loading in Safari in v.3 and v.4 that's being fixed currently, CCXSDK-6179"
But it's still not fixed, so I'm guessing the engineering team haven't got to the bottom of what's causing it.
We have found the issue. The problem is with the default Apple setting "Prevent cross-site tracking" in Safari > Settings > Privacy.
If you turn off "Prevent cross-site tracking", then you are able to log in to Express Embed in Safari.

We have had to include a warning to users on our Express Embed UI saying "You are using Safari – we recommend using Chrome. To log into Adobe Express here using Safari you may need to turn off "Prevent cross-site tracking" in Safari > Settings > Privacy."

I see from the recent Developer emails that you have been working with Miro on Express Embed @Marichae5CDF (hi!) and so I would expect this affects their users too, just as it affects other users here using both v3 and v4.

Turning off "Prevent cross-site tracking" will enable login on Safari, so hopefully that gives the engineering team something to work with to solve this issue without asking users to do this.

I suspect that this is related to how the upfront authentication or delayed authentication works - as it used to work OK in Safari when we first started using Express Embed almost 2 years ago. Delayed login is the only major change I'm aware of to this part of the app since then - although I couldn't see when it was introduced in the Changelog.

Please could you check it out and let us know that you see the same thing, and keep us informed of work on fixing it? It's been a long time that it's affecting a really large proporition of our creative users, who tend to prefer Mac and Safari.

Thanks,

Ru

Report · Jun 24, 2025

Two weeks, no reply