My development account for Spotify has been enabled and I am trying to walk through their simple tutorial app (http://developer.spotify.com/download/spotify-apps-api/tutorial/). I should note here that I am on a Win 7 workstation.
When I try to load the local app by typing 'spotify:app:Tutorial' in the search field I get the following msg/error: "Sorry, I could find this app. metadatafailed URI: spotify:app:Tutorial Error: appNotFound."
I have tried adding the app files to the following directories and still getting the error:
C:\Users\Me\Documents\Spotify\Tutorial (note this dir did not exist I created it)
C:\Users\Me\AppData\Local\Spotify
C:\Users\Me\AppData\Local\Spotify\Users\me-user
C:\Users\Me\AppData\Roaming\Spotify
C:\Users\Me\AppData\Roaming\Spotify\Users\me-user
So where exactly are you suppose to add the files so that Spotify will load local apps?
Thanks!
Your first guess is correct (C:\Users\Me\Documents\Spotify\Tutorial). However you need to be running the latest preview release (https://www.spotify.com/uk/download/previews/). And on my PC I had to completely un-install and reinstall the application before the developer options became enabled.
Not sure whether it helps in your case, but try naming the folder tutorial with lowercase t. See Spotify Tutorial example app is blank
I can't leave a comment, but I was having the same issues and had to do a combination of what Niklas and akakjs did. I had to completely uninstall the spotify app, download/install the preview version, create a Spotify directory in My Documents, then create the folder Tutorial. Then, in the Spotify search bar I had to type "spotify:app:tutorial" with the lowercase t. I hope this helps!
Had the exact same problem. I had to run Spotify as administrator, worked right away.
And the path i used were: C:\Users\me\Documents\Spotify
I had the same problem: Spotify could not find my app directory even though the proper folder had been created in my Documents folder.
I Fixed it by running Spotify as an Administrator.
Related
I have an app on the google play store that's getting around 3k downloads a day. Recently I tried sharing my files through google drive and they all got screwed up and won't work in Android Studio when I open them. Is it possible for me to start from scratch and submit that update to the listing I already have? All I'd like to do is place some ads into the app
I still have the key for the file I believe.
Thanks for any help in advance!
You can still sign a new version of the app so long as you have the original key and passcode (if you used one).
Submitting successfully will also require you to have the same package name and a version number higher than your last release.
Was able to find the answer! Turns out I can create a new android studio project with the same package names and sign with the old key.
I am publishing my node js site to azure using this tutorial - http://blogs.technet.com/b/sams_blog/archive/2014/11/14/azure-websites-deploy-node-js-website-using-visual-studio.aspx
I get the following error, as mentioned in one of the comments on the blog, any idea what this error is about and how do I fix this ? I am able to run my app locally no issues with that.
Error: InvalidParameter
Parameter name: index
P.s : the site is like a very basic "Hello world" kind of site, this is the first time I am using and deploying to azure too.
I created a new project as a "Blank Azure Node.js web application", and replaced the resulting package.json and .js files with what I had before, and it publishes fine now
All was working fine for and suddenly got the error! I pretty sure it something in the project as it's now happening on vs2013 and vs2015 on different computers.
Its something to do with Templates after a lot of searching. For me Azure TFS CI got things working again if possible for you?
I had this issue with some projects but not with others, all created in a similar way. So I went thought every change and every setting I could until eventually i worked it out. I didn't want to give up and just remake them.
Basically its file paths, the first thing you notice is that it errors very quickly compared to a usual publish, the first thing that is triggered is a build but unlike heavy framework languages there not really much to actually build.
Like all builds for VS it pops out a bin folder take not of where this appears. This is the key, you want this to appear in the root of your deployment usually at the same level as the publish profile.
Before I moved my projects to VS, TFS and Azure, I used to use git and used the azure push and deployment as part of git, so I instinctively structured my folders in the similar fashion with src folder and all the extra VS baggage in the a directory higher.
This is where I noticed bin folder, so re-structured my solution and made changes to .njsproj (notepad) and moved to be inline with source code and re-added it yo my solution.
Technically speaking this a bug within VS as it allows to create the project and specify different locations which is all fine unless you want to build and publish locally.
Once you get your head around what is going on you should be able to solve this problem easily and not make the same mistake in the future. If anyone is still confused comment and ill grab some screen shots.
I've searched everywhere but I couldn't find this question with an answer that helped with my problem.
I'm trying to make my first spotify app, but i can't get the first step to work.
I've downloaded the api tutorial (https://github.com/spotify/apps-tutorial), made a Spotify folder in My documents, enabled my developer account but still if I want to try the app by going to spotify:app:api-tutorial, I get the message: Failed to load application api-tutorial.
Can anybody help me with this?
If you're on the 1.0 branch of the apps-tutorial project, the bundle identifier is actually 'tutorial', so you should type 'spotify:app:tutorial' into the search field.
If you haven't, restart the Spotify client after you've moved or cloned the apps-tutorial project into the Spotify folder. Double check that it's in the correct folder.
Update: The 1.0 branch has been removed, and its contents has been placed on the master branch. The 0.x versions of the API is now placed in the 0.x branch.
I have looked extensively through SO, but have yet to find any help with this question, despite trying almost every recommendation.
https://github.com/danwaz/powerhour
trying to install this app on Spotify. I do have a developer account, and have created the necessary dir in ~/documents/Spotify
For whatever reason, I am shown a loading bar when I attempt to load the app according to how the manifest details the bundle. I do get a "metadata started" message, but nothing loads...it just sits there spinning its' wheels.
Any recommendations from anyone?
What platform are you on?
If you're on a Mac or Linux, the folder should be ~/Spotify, where ~ is your home directory.
If you're on Windows, it should be in the Spotify directory of your My Documents folder.
I have recently upgraded to the new Azure SDK (September 2011 v 1.5).
Ever since I have not been able to start the compute emulator. Consequently I can't debug the services on my local machine.
I have seen a suggestion that the problem lies with the fact that my user account has a space in it, so I renamed my account but that didn't make any difference. It may be that the problem is that my user profile path has a space in it. Changing the account name has no effect no the profile path.
On the msdn forums it was suggested that I remove *:808 binding in IIS Manager for Default Website. See MSDN Forums
Anyone have any other ideas?
Another option:
So, given the "rename your user account/regedit doesn't work for you, you may want to look at this MSDN article, which suggests you can just set an environment variable and run the emulator without mucking with the registry... not sure if setting the environment variable globally would let you run automatically within VS.NET without manually starting up the emulator the first time, but it is certainly easier.
Yes, the space(s) in your profile path are the issue, and this appears to be a regression for a bug that was found in a previous version of the emulator (the only reason I even thought to try logging in with a different account in the first place). I was literally just putting together a quick blog post here describing the same issue. You'll need to do some registry editing to fix all the references to your old profile path if you want to fix it, or just create a new user if you can deal with re-installing software (I love the Web Platform Installer, but I found out during this exercise that it doesn't do a good job installing for "all users").