As in the API documentation, I have created a ~/Spotify/myapp/index.html (on a Mac) but when loading spotify:app:myapp from the search bar in Spotify (preview version that supports apps) I get a "Sorry, I could not find this app" message.
What am I missing (this should be all for a "Hello World" according to the docs, right? Is there a way I can debug this to better understand the problem?
It sounds like you did not apply for being a developer at Spotify. Do you have a menu item called Develop and have the ability to right-click inside given apps?
If not, you need to have developer capabilities activated by Spotify. You can do so on their Site. Your account will probably not be activated instantly.
I just made a video explaining how to solve this.
http://www.youtube.com/watch?v=paqq3h1UJhU
Basically you need to go to the Spotify.app -> Contents -> Resources -> cef_views ; and drop your stuff in there.
Something else to keep in mind! I was trying to create my app with an underscore in the name, and for some reason it choked up the application. As soon as I removed the underscore and kept it to just letters, it worked fine. shrug
So according to the docs you posted yourself, you need, in spotifys current form, to name your folder appstore.
Your application will appear in the sidebar in future builds - for now, please name the folder of your application “appstore” to have it appear in the sidebar. Please name your application accordingly in the manifest, and that very name will appear in the sidebar.
What I got wrong is that insite "Spotify" folder you have to create "Tutorial" folder, in my case all the files were on Spotify and not in Tutorial.
Related
I have an unlisted extension published through the Chrome web store which is already being used. I have a new version which I would like to release just to testers initially, before a full roll out to everyone. Can this be done?
The same thing has been asked here but it was almost 9 years ago, and the answers disagree on whether it's possible or not:
How to publish new version of Chrome Extension only to testers
The short answer is "No, it can't be done for a published extension".
According to Chrome Web Store visibility descriptions, you must unpublish an extension before it can be published to trusted testers. Users who already have it installed will get updated to the new version.
In your case, you have to create a new extension with the new code, and a different name like "MyApp Beta" and publish it privately to the list of trusted testers.
Maybe you already know this, but you can install a chrome extension manually.
Go to chrome://extensions/ and check the box for Developer mode in the top right.
Click "Load unpacked exention"
Select the folder where your unzipped extension resides in.
So, you can send a zip/rar to your testers, let them follow the procedure and test the extension. Might be that you have to give it another name so as to not conflict with your earlier eversion, or you could ask your testers to delete the existing extension to avoid conflicts.
Well, the simplest way is to pack a .crx file of the tester-only extension then link to it via some cloud-hosting service like Google Drive. There is no way to do this through the Web Store. You could release a different extension as a beta channel though.
Not strictly related to publishing a full extension, but ... you could use feature toggling to control the visibility of new functionality? So wrap the new functionality in toggle checks and only turn the feature on based on some criteria you can decide in a custom roll-out strategy. See enter link description here for an open-source implementation of a feature toggle control system.
If you have a developer account and want to publish it on the chrome web store privately to just testers this is what you have to do:
Go to the Pricing and Distribution page of the extension during the publishing process
Click "Private"
Go to your developer account settings, and in the "Management" section, you can add trusted tester accounts.
You can change the status to public whenever your extension is ready.
I've created a custom Masterpage, and one of my apps (an ask & discuss widget) does not work with it. All other widgets and apps work perfectly.
I tried checking if it was an issue with the coding in my master-page by removing my JavaScript and my CSS. Unfortunately this did not work. I noticed the app only works with the pre-installed seattle.html. I then duplicated seattle.html, seattle2.html and checked if the app works with it. Did not work.
What is going on?
Against my better judgement, I tried editing the original seattle.html by adding "Hello World" in the yellow div box that acts as a dynamic content placeholder. I saved it. The "Hello world" managed to cause the app stop working. I tried restoring to a previous version of seattle.html unfortunately, it didn't work.
This seems to be a custom Ask & Discuss web app that allows users to ask questions and then vote for their favorite answers (similar to Stack Exchange). It is still linked to a list, but the view is much more dynamic than your standard Out of Box Discussion Board available in SharePoint. I unfortunately cannot get support from the original installer.
The view I get
vs:
The view I should get
Can I get tips on what to look for in the code that may help me fix my issue?
I'm trying to add a support page right in the extension window but all that I can find is adding a link to another page. I've included some pictures, as I don't know how to really describe the feature.
that's what I have currently, and below is what I want to have-
This is a screenshot of what I have on the dev page, concerning the support feature-
I'm not sure what I need to change, so any help would be appreciated! (Directed here from this chrome forum thread)
Go to https://chrome.google.com/webstore/developer/dashboard
Click "Edit your User Feedback preferences"
Check the "Enable User Feedback for all my apps in Chrome Webstore." box.
Note that neither you nor your users will get notified of new posts made in the webstore support section, so you probably want to direct users to a third party support platform, such as issues on the project's Github repo.
I want to know if it's possible to launch windows applications from a website. If it is possible, how? Sort of like battlelog for battlefield, when a button is pushed it opens an application.
Edit: This is for personal use
Try this:
Make each button be a link to download a company template file for the given application. For example, the "Excel" button would download and the user should be prompted to open it with Excel.
For instance, try clicking one of the links here:
http://www.google.com/#sclient=psy&hl=en&q=template+filetype:xls
Linking to static files on the web server should be sufficient, so long as your server sends the correct MIME-Type or Content-Type.
HOPE it helps!
Take a look at this thread. it should point you in the right direction. In short you can do this in IE using ActiveX objects. But I must warn you that it is a very bad idea
I created my first Spotify app. I put my manifest.json, cafeplaylist.js, and index.html in users/tati/documents/cafeplaylist on my Windows machine. From Spotify (which knows I am a developer, proven by the fact I have a Develop tab), I type spotify:app:cafeplaylist. It cannot find my app!
I also tried this from my Mac, creating tatianabecker/Spotify/cafeplaylist with the same files. It also cannot find my app!
These 3 files can be found in the main file of https://github.com/realoptimal/socialmix
Bummed, as I can't even get going writing my first app if it can't be found. Someone suggested it is because I don't have Premium. Is that is, or something else?
Thanks,
Tatiana
PS I see others have asked similar questions, but their problems were cleared up by putting the files in the right folder... mine persists.
Your github link isnt working, but maybe you should check this question out: Spotify App Dead
You probably dont have a BundleIdentifier and a BundleVersion added to your Manifest file.
Check out my Manifest.json file, for a correct view!
Hope this helped you out ;)