I’m wondering about the changes to Spotify app URLs after the latest update. I used to be able to navigate within the app using simple URL schemes, but now it seems like I need to include bundle version information.
Does anyone know if this bundle version parameter is now mandatory for all app navigation calls? I’m concerned about how this affects existing scripts and whether there’s a way to make it work without hardcoding version numbers. Any insights on the new URL structure would be helpful.
Hit this same problem last month with a client integration. Spotify made the bundle version mandatory after their v1.2.0 update, but they didn’t document it well at first. You don’t need to hardcode version numbers like v1.2.3 though. Just use ‘spotify:app:myapp:*:homepage’ with a wildcard - it’ll grab the latest version of your app. Works consistently across different client versions in my testing. Another trick: query Spotify’s API first to get the current app version, then build the URL programmatically. Saves you from breaking changes when versions auto-update.
Bundle versioning is required since March, but there’s a cleaner way than what others mentioned. After lots of trial and error, I found you can skip the version completely if you register app URLs through the new manifest system instead of legacy URL schemes. The manifest handles version resolution automatically - no wildcards or API calls needed. For existing setups, I’ve had luck with spotify:app:myapp::homepage (empty version field) as a fallback on most clients, though it’s not officially supported. Been running this in production for two months with zero issues, but I’d migrate to the manifest system soon since Spotify’s killing the old URL structure by year end.