Links not working properly in Spotify embedded browser after latest update

[jackw]

I’m having trouble with my Spotify advertising campaign page after the recent app update to version 1.0.1.1060.gc75ebdfd.

Before this update, all my regular HTML links were opening correctly inside Spotify’s built-in browser. Now they keep redirecting to the external system browser instead of staying within the Spotify app.

I’ve tried adding target='_self' to my anchor tags but that didn’t help. As a workaround, I switched to using JavaScript with window.location.href in onClick handlers, which does work for basic navigation.

<button onclick="navigateToPage('/promotional-content')">View Campaign</button>

<script>
function navigateToPage(url) {
    window.location.href = url;
}
</script>

However, I’m stuck because I need to implement social media sharing for Facebook and Twitter. These sharing features only work with traditional anchor tags, not with my JavaScript solution.

Has anyone else encountered this issue with the recent Spotify update? Is there a way to force links to open in Spotify’s internal browser again?

[Laura219]

Yeah, spotify’s embedded browser is totally broken after that update. Try window.open() with specific parameters instead of regular links - sometimes fools the browser into staying internal. For social sharing, you could iframe the share buttons instead of direct links. It’s hacky but might work until they patch it.

[Ryan_Innovative]

Yeah, this is a known bug in version 1.0.1.1060.gc75ebdfd that breaks how the embedded browser handles links. I hit the same issue after updating - Spotify changed their browser security policies and now treats certain links as external by default.

For your social sharing problem, try a hybrid approach. Detect the link type before it executes using event.preventDefault() on anchor clicks, then either use your JavaScript navigation or let it handle social platforms normally.

What worked for me was creating a bridge function that checks if the target URL matches your domain versus external social domains. The internal browser still supports some iframe communication, so you could use message passing to handle social shares differently than internal navigation links.

[miar]

Had the same issue with embedded content in Spotify after that update. The browser changes have been a pain for developers. Here’s what worked for me: I kept the anchor tags for social sharing but added a custom data attribute to control behavior. Wrapped the social share links in a container and used event delegation to catch clicks before they bubble up. For Facebook and Twitter sharing, try using their official APIs through postMessage to the parent frame - sometimes bypasses the external redirect problem. Also worth testing rel="noopener" though results vary across Spotify client versions. The internal browser has stricter policies now, so there might not be a perfect fix until Spotify sorts out this regression.