We realized that in our development team we have inconsistent Spotify versions. One part has 0.8.8 whereas the other part is having the old version - 0.8.5. Spotify is not upgrading for the accounts with the old version. However, apparently there are changes to the Spotify API, so that our app runs on 0.8.5 but not on 0.8.8. How can the other developers update to 0.8.8 as well?
The current production Spotify API framework should be the latest, regardless of the client version.
Right now it's ver. 0.2.8.
Remember that you need to declare your framework dependencies inside your manifest file. You can read more about it here:
https://developer.spotify.com/technologies/apps/guidelines/integration/#frameworks
0.8.5 is still the current live client, while 0.8.8 is gradually rolling out to a few users.
There is a preview API which depends on the bridge changes made in 0.8.8, but it shouldn't be used for production yet.
https://developer.spotify.com/technologies/apps/preview/
Related
I have an azure mobile app that is consumed by a Cordova app - this azure mobile app is built in node.js and is responsible for managing the push notifications for this Cordova app.
In this node app, I use mobileservices-sqlserver to register in the database the devices that will receive the push notifications, and I am having problems with this module compilation in node version 6.1.9 - actually any version higher than 0.8x.
Can I pre-compile this mobileservices-sqlserver to a newer node version, maybe using node-gyp? I couldnt find any instructions on how to do that.
Sorry if that is silly question, but I'm really new to node.js.
I've seen some similar issue here, but I'm not sure if it's the same.
Is this an old Mobile Services service? If so, check out the Mobile Apps Compatibility NPM, which replaces mobileservices-sqlserver with the msnodesqlv8 and will allow your service to work with modern versions of Express and Node.js.
If this is already a more modern Mobile App service, see also the mssql NPM for SQL Server data access.
Meteor is typically behind in Node.js version because it is a framework that uses its own bundled version of Node.js, and its APIs and features are built to rely on that version of Node.js.
I'm sure that in many cases upgrading Node.js poses no problem.
As an example, Meteor 2.10 at time of writing ships with Node.js 14. But we're already on Node.js 19.
Is there a way to tell Meteor (f.e. with the meteor cli, or some meteor package) to use newer versions of Node.js (and npm)?
Meteor 1.4 now supports Node 4.4.7!
See release notes
To upgrade to Meteor 1.4:
Go to the root of your project's directory
meteor update
Meteor does not support NodeJS 4+ as of now. The discussion is available in https://github.com/meteor/meteor/issues/5124
The latest update to the thread on April 29 is:
Guys, relax. The difference between Node version 4, 5 and 6 are relatively minor, and so if Meteor can support one, it can and will support all others. Ben created PRs for every currently active and supported Node version, but the fundamental part of the work is about making Meteor work with any (recent, non-legacy) Node version, and from there basically everyone should be able to freely select whichever one fits their goals and intentions best (i.e. 4.x if you don't care for bleeding edge Node, 6.x if you do; 5.x is not going to stick around for very long as it's not an LTS version).
So come and check out and help with the PRs if you're interested and
you can, but if not, just rest assured this is being worked on and
prioritized appropriately and I'm pretty sure Ben (and/or others
working on this) will keep everyone posted on any meaningful progress.
I am currently using Firbase 1.2.3 provided with the Nest SDK for iOS. I have found that the Firebase Framework provided is so dated it cannot built with Bitcode enabled. This means I cannot build the whole project with Bitcode support. It appears from the documentation they are still pushing Firebase, however in practice they are not updating it. For example, I believe Firebase is currently up to version 2.3.4 (Bitcode Supported). When I use the later version the authorization process is unstable and can take a long time. Has anyone been successful and using a more recent Firebase Framework?
According to this article some support for older versions of Azure are going away:
https://azure.microsoft.com/en-us/blog/microsoft-azure-storage-service-version-removal/
We have a vs2008 application that is uploading files to Azure. {Using Azure 1.2 (for VS2008) - Microsoft.WindowsAzure.StorageClient v1.0.0 - Runtime v2.0.50727}.
We can't have this break since we are using this in production.
I need to know if there is a clear way to know if this is going to stop working.
I would really like to know if there is a way to upgrade the vs2008 project to use a compatible version of the StorageClient without migrating the project to vs2015.
Your version of the library should still be supported after the service removal. You can confirm which version of the service you are hitting by running requests through Fiddler and checking the x-ms-version. As you can see in the most recent post regarding our service deprecation, we are only removing version 2009-07-17 and older as of August 1, 2016.
Can you run version 0.2.3 and 1.0.0 of the Spotify apps api at the same time in the same app? This would be really really helpfull for me during the development process in order to migrate our current Spotify-app from 0.2.3 to the new 1.0.0 api.
I am sorry but that it's not possible. The API version that your app uses is defined in the Dependencies section of your manifest.json file.
You can create a copy of your app, changing its BundleIdentifier, and try to isolate the code that is depending on the Spotify API, modularize it and port it step by step.