I’m encountering a frustrating issue while trying to run a custom Spotify app. When I navigate to spotify:app:mytutorial, it displays a metadata error, indicating that the app is not found.
I’ve already enabled the developer menu in Spotify. My app’s directory is set up at ~/Spotify/mytutorial like it should be. I’ve attempted to restart Spotify and even reinstall it, but the error persists.
I’m starting to wonder if this could be an issue related to my recent upgrade to macOS Mountain Lion (10.8). Is there anyone else out there who is using this OS version without facing similar problems?
Additionally, my development setup includes dnsmasq and apache with custom TLDs (.build and .dev) configured in my /etc/resolvers. Could this setup be causing the issue? Does Spotify run a local web server when testing apps?
I would prefer to avoid making big changes to my development environment if it’s not necessary. Any suggestions on what might be causing this error?
The Mountain Lion upgrade probably changed Spotify’s manifest format requirements. Check if your manifest.json has all the fields newer Spotify versions need. I hit the same issue after an OS update - my manifest was missing the “vendor” field that became mandatory. Also, Spotify’s app framework is picky about case sensitivity, so make sure your folder name matches exactly what you’re using in the spotify:app URL. Still getting metadata errors? Try moving your apache config aside temporarily to see if there’s a port conflict. Spotify runs internal services that can clash with existing web servers on standard ports.
I encountered a similar issue previously, and it was related to folder permissions instead of the OS upgrade. Verify that your ~/Spotify directory has the appropriate read permissions for the Spotify application. Sometimes, major system updates can inadvertently alter these permissions. Your dnsmasq configuration with custom TLDs shouldn’t be affecting anything, as Spotify utilizes the spotify:app protocol internally. However, if Spotify is attempting to make localhost connections and your DNS setup is intercepting those, it could potentially lead to complications. As a troubleshooting step, consider creating a new test app in a different directory to determine if there is a problem with your mytutorial app or if it’s a broader system issue. Additionally, examine the Spotify console logs when loading the app; they often provide more detailed error information than what is displayed in the user interface.
same issue on Mountain Lion. check if spotify’s looking in the right directory - upgrades sometimes mess up user paths. run ls -la ~/Spotify/ to make sure the app folder’s there and readable. also wipe spotify’s cache folder completely before restarting, don’t just reinstall.