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?
Related
My goal is to develop a VS Code extension with speech recognition, ideally via google's API.
When attempting to import and use #google-cloud/speech, the following error is thrown at runtime:
Error: #grpc/grpc-js only works on Node ^8.13.0 || >=10.10.0
VS Code (as of 6/20/2019) is running electron 3.18 and node.js 10.2.0. Does this mean there is no way to work around this issue?
I'm following this tutorial: https://cloud.google.com/speech-to-text/docs/streaming-recognize
Sounds like it should work starting with the next release then. From the preliminary 1.36 release notes:
The Electron version that VS Code runs on has been updated and brings with it an update to Node.js from 10.2.0 to 10.11.0. All extensions will now run on this newer version of Node.js.
To make sure, you can try an Insider's build.
Generally speaking though, there's no way to control what Node version VSCode extension run on (see here), so I guess you got lucky here. :)
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.
(this is probably a stupid question, but here goes..)
I've been trying for some days now at having a go at creating a integrated cast that works with react-native, but can't get it working.
Is there any easy way of integrating the cast library with react-native, any go-to examples like the CastHelloText-Android for example?
You may check this react-native-google-cast library that unifies both android and iOS chromecast sdk.
For iOS
This library requires Cocoapods to manage Chromecast SDK.
Add pod google-cast-sdk to your Podfile. This is the easier way to have the SDK up to date.
For Android
This library requires Google Play Services, Media Router and Google Cast dependencies to manage Chromecast SDK.
You need to add compile 'com.google.android.gms:play-services-cast:9.4.0' and compile 'com.android.support:mediarouter-v7:23.0.1' into your your app's build.gradle dependencies. mediarouterversion must match with your appcompat version.
Refer to the example folder to find an implementation of this project. Use pod install and react-native link react-native-google-cast to try it.
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/
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.