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.
Related
Not sure what details I should be providing to be completely honest, other than I googled and searched for this solution and I deleted everything and retried and didnt work out, I downloaded all the files needed, I added application settings and it added an error for me telling me that I need to install or update Microsoft.WindowsDesktop.App, version 3.1.0, which I have installed and already existed anyway
I tried going to application event logs on Azure portal, there was 3 errors first this one which some people suggested going to web.config and changing it to Module not v2, and I dont see any web.config file in my mvc project
2nd error which I already talked about but its just not working, so I assume somehow its not seeing it??
3rd error Also this I am not quite sure what to do with it.
Lastly, as I said I am not sure what information I should provide, I dont have much time and I was asked to publish it on azure there was no problems and seemed easy but errors popped up and nothing on the internet fixed my issues, you can comment and I will add any required data to fix this.
Thanks in advance
I installed each and every package in the dotnet folder to make sure everything is right and everytime it recognized there is a file already and asked me if I want to repair I said yes but that didnt help
I checked my .json file if it had any errors like some people suggested
checked if Azure portal specified that I am using ASP.NET 3.1core which it did
~~I used search for "stdoutLogFile" to check if I can find it anywhere on my solution since I cant find my web.config but I there was no result~~
I found out that I can add the web.config and make changes to it, and I did so but there was no result for it, still same error (yes I change the publish profile and republish to make sure it took the changes)
[enter image description here][1]
[1]: https://i.stack.imgur.com/rgiVi.png I got these errors when I opened the profile.arm.json folder under the server dependency folder
I just attempted to update the site map provider from 3.3.6.0 to 4.0.14. I followed the instruction on the wiki however my SiteMapPath now renders empty. I made no changes to the mvc.sitemap file other than updating the schema to 4.0. When I debug into the SiteMapPathHelperModel I find that the model has no nodes defined. I am using the internal DI container (I would like to get this working before switching over to the application container).
When I check the sitemap.xml file it is well populated which makes me think that the mvc.sitemap is being read.
I'm out of ideas on this one and would be happy to provide any additional information which may be useful. I'm not even sure where I can hook into debug this problem. Literally the only thing I changed between a working 3.3.6.0 and a not working 4.0.14 was what was prescribed on the wiki.
Ok, since your /sitemap.xml endpoint appears to be working, you are correct the sitemap is being populated and loaded correctly.
There are a couple of things I know of that can cause this to happen:
If you are using Dynamic Node Providers, they must be added to a node that is not otherwise part of the sitemap. See my question here - I am trying to figure out why this is the case as well.
Your routes don't match your nodes - please read Routing Basics and/or post your routes and Mvc.sitemap XML.
If you check the above and everything appears to be correct, please make a small demo project showing a sample of your configuration and open an issue on GitHub, as it is highly likely your specific configuration has something to do with the problem.
BTW - You can debug by cloning the current repo on your system or downloading the solution as a zip, enabling NuGet package restore on your solution (right click the solution > Enable NuGet Package restore), add the MvcSiteMapProvider project to your solution, and then in your project remove the reference to MvcSiteMapProvider and add the reference to the newly added MvcSiteMapProvider project from your MVC project. Then you can add breakpoints and step through the code. I suggest making a backup of your solution (or ensure you can roll back another way) before doing this, and reverting back to your current state when done.
I have documented the whole procedure here: http://www.shiningtreasures.com/post/2013/08/21/debugging-an-mvcsitemapprovider-configuration
I have an ASP.NET MVC 4 app that I'm trying to deploy as an Azure Web Site. My app works fine in my local environment. When I publish the site to azure though, I receive the following error:
Multiple types were found that match the controller named 'Root'. This can happen if the route that services this request ('') does not specify namespaces to search for a controller that matches the request. If this is the case, register this route by calling an overload of the 'MapRoute' method that takes a 'namespaces' parameter.
The request for 'Views' has found the following matching controllers:
MyApp.HD.Web.Controllers.RootController
MyApp.Web.Controllers.RootController
Why would I get this error on Azure but not locally? I can't figure out how to get around it.
Thank you
I've had this problem before. Let me explain why it happened.
We added a new project to our solution, let's call it NewProject. This project had been set up incorrectly so we recreated it as NewProject2. Once the project was setup and working, we renamed it to NewProject. This is when the problem started. Under certain build configurations we were getting the same error as you. It was complaining about ambiguous controllers with namespaces NewProject and NewProject2. Doing a find-in-files returned no matches for NewProject2. The was thoroughly frustrating. Given that this was only occuring under certain build configurations was a big sign that the problem was with left-over references in the bin folder(s). Doing a clean didn't seem to fix the problem. The ultimate fix was to do a complete code purge. DLLs typically do not get committed to source control. I backed up and deleted all code and got it back from source control. The issue no longer occurs.
It's worth mentioning that this issue was not global. It only occurred on certain developer machines. I figure the ones that were affect were the ones that had gotten latest from source control during the process of create1/create2/rename2/delete1.
Try doing a clean and rebuild in the affected build config.
Try manually removing your bin and obj folders.
Try a complete code purge
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.
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.