Is there any workaround for using the new version (V2) of Dialogflow API in Unity? There used to be a SDK for the previous version but apparently it will be discontinued next year...
Since there is no official Dialogflow-Unity-SDK, you can use the Google.Api.Dialogflow.v2 library.
Details at
Authenticating Request with Google.Apis.DialogFlow.V2
Note: Remember that you can't use your token anymore. You need to create a credential file: Details at: https://medium.com/#tzahi/how-to-setup-dialogflow-v2-authentication-programmatically-with-node-js-b37fa4815d89
Related
I have a flutter app that uses microsoft authentication and I want to use the ms graph api. Flutterfire didn't have support for microsoft and other OAuth providers so I used firebase_auth_oauth. Now with a new update flutterfire supports microsoft authentication and I followed the docs to use it. The problem is that firebase_auth_oauth gave me back a OAuthCredential (using its signInOAuth method) with an access token and flutterfires signInWithAuthProvider method gives me back a UserCredential. So my question is how can you get an access token after signing in?
Note: the firebase_auth_oauth plugin doesn't work anymore and I think it has to do with the update to flutterfire. And I don't think the firebase_auth_oauth plugin will be updated.
Recently the hockey moved to app center and i want to download the latest version of android and iOS version on the fly using the API.
What I tried ?
checked the official swagger api-specs
1. #GET("/v0.1/apps/{owner_name}/{app_name}/recent_releases")
2. #GET("/v0.1/apps/{owner_name}/{app_name}/builds/{build_id}/downloads/{download_type}")
but the download url provided by the second url has a different host and it doesn't work.
This API:
#GET("/v0.1/apps/{owner_name}/{app_name}/builds/{build_id}/downloads/{download_type}")
is to download builds if you use the Build service from App Center. If you only use Distribute service, try one of these APIs to get the release details, which includes the download url:
https://openapi.appcenter.ms/#/distribute/releases_getLatestByUser
https://openapi.appcenter.ms/#/distribute/releases_getLatestByDistributionGroup
UPDATED
The api's has been changed, and the new api we can use is
#GET("/v0.1/public/sdk/apps/{app_secret}/releases/latest")
fun latestRelease(#Header("X-API-Token") apiToken: String, #Path("app_secret") secret: String): Call<JsonObject>
offical swagger api
app_secret you can list your app secret using app list, use this command line.
apiToken you can generate a token following these instructions
The API's changed, and /v0.1/public/sdk/apps/{app_secret}/releases/latest is no longer supported.
you can use instead
https://api.appcenter.ms/v0.1/sdk/apps/{app_secret}/releases/latest
Another better option then you can easily get any version is to use
https://api.appcenter.ms/v0.1/apps/{owner_name}/{app_name}/releases/{release_id}
Get a release with id release_id or 'latest' to get the latest release that was distributed to the current user (from all the distribution groups).
Swagger
I've been using the NuGets from Outercurve Foundation (Facebook and Facebook.Client) and I've just updated to the latest stable version for both of them since Facebook API 2.0 and 2.1 will be depricated on the 7th August 2016 and they are forcing us to use the later verstions of their API.
Here is the thing... the website facebooksdk.net which had documentation and such was down for some time and now it redirects to hackerapp.com which has no documentation whatsoever...
Does any one know the version of Facebook API that the NuGet Facebook 7.0.6 and Facebook.Client 1.0.4 are using?
I think that the facebook button (from Facebook.client) is using the 2.1 version of the API. because I saw it in the query when it opens the browser just before the login prompt.
Does any one know which version is used? and if there is another way to login using the 2.5 or 2.6 API version?
I believe the client does not enforce any API version, so it will make unversioned calls. And in this case, it will use the default API version that is set on your Facebook App...
You can check the default API version for your app in your app's dashboard in https://developers.facebook.com
Mine is currently v2.0 (I don't know yet how to change manually that version. Facebook will certainly upgrade it when v2.0 expires)
I am using an even older version of the nuget package (6.4.2) and was able to override the version simply setting it in the endpoint being called:
Exmaple:
var client = new FacebookClient(accessToken);
dynamic facebookUser = client.Get("me"); //this will use v2.0 currently (default API version)
dynamic facebookUser = client.Get("v2.6/me"); //this will use v2.6
PS: version 2.0 will expire 7th August 2016... version 2.1 will expire only in 30 October 2016 (2 years after 2.2 was launched)
For those wanting to use Facebook.Client with Facebook API v2.5 you can use this one https://github.com/rickrvo/facebook-winclient-sdk
it's just the same as the version 1.0.4 but changed all hardcoded calls using v2.1 to use v2.5
I'm wondering if the Azure Notification Hubs REST API documentation is still correct and up-to-date or if there is already a newer API version than "2013-08" that can be used.
All the single pages show "Updated: February 26, 2015", but I guess it was just a meta data update of all the pages, since the API version didn't change, it's still "2013-08".
Here (and here) is an example for the REST API usage from Elio Damaggio which uses "2013-10" as the api version.
I tried all possible api version values in the format "yyyy-mm" from "2013-10" to "2015-03" and the following were working: "2013-10", "2014-01", "2014-05", "2014-08", "2014-09", "2015-01".
Does anyone use a newer API version than "2013-08" or does anyone know anything about a newer API version or documentation? Specifically, does anyone know if there is a documentation for a newer API version, e.g. "2015-01", or at least a changelog?
Got an answer on MSDN forums:
The latest version is 2015-01. All or most of features works with
starting version 2013-08.
Version in documentation indicates that minimum version required for
working that feature. Hence, all documentation is pointing to 2013-08.
...
Yes, you can use version 2015-01 instead of 2013-08. There won’t be
any difference because we didn’t do any breaking changes from 2013-08.
All the features works from version 2013-08.
Moreover, the source code for the Java REST wrapper for Windows Azure Notification Hubs on github seems to be a good reference. It is using api version "2014-09", not "2015-01" right now, but at least it includes the registration code for Amazon Device Messaging and Baidu Cloud Push which are currently missing in the REST API documentation.
We have been using the Grails Facebook-graph plugin for a while now - it has been working perfectly until earlier this month when FB apparently turned off their old authentication scheme, and indirectly forced everybody to use oauth2 instead.
This post from FB https://developers.facebook.com/blog/post/525/ describes the changes, and the issue in the Grails plugin seems to be that it does not comply with the new standard.
The main issue appears to be in the way the active user data is being maintained in the plugin. This is currently based on the FB provided cookie "fbs", which contains all the necessary session data related to the active user. Unfortunately, this is no longer provided by FB (apparently replaced by a "fbsr" cookie instead).
I have searched the FB documentation, and in various forums for details on how to upgrade the plugin, but unfortunately without luck.
Can anyone help with a hint or two on what steps should be performed in order to get the plugin updated?
EDIT: I think the updated version of the plugin (0.14) has been pushed the public repository. You should try grabbing that one first before reading the rest of my answer.
It looks like the plugin maintainer, Jesus Lanchas, made some updates over the last few days to enable oauth2 support. It has not been pushed to the plugin repository yet, but I was able to get it working with my project. Here's what I did:
#Install a local copy of the plugin WITHIN my project
mkdir plugins-local
cd plugins-local
git clone git://github.com/chechu/grails-facebook-graph.git
mv grails-facebook-graph facebook-graph
Update BuildConfig.groovy and tell grails where to load the plugin from. I put this line before grails.project.dependency.resolution
grails.plugin.location.'facebook-graph' = "plugins-local/facebook-graph"
Uninstall the existing facebook-graph plugin from my project
grails uninstall-plugin facebook graph
This is a temporary solution for me until the offical update hits the repo, but it allows me to make sure I'm using the same new code everywhere.
EDIT: we released our Facebook Grails SDK on GitHub :
https://github.com/benorama/facebook-grails-sdk.
Currently only tested on Grails 2.0…
Any feedback is welcome before we release it officially to Grails.org.
Indeed, it looks like Grails Facebook-graph plugin does not support OAuth2 Facebook authentication (which is required since October 1st 2011).
We have already ported the official PHP SDK V3.1.1 to ColdFusion 9 (https://github.com/affinitiz/facebook-cf-sdk).
Last month, we started to implement it as a plugin in Grails 2.0.
It is currently at an alpha stage so we have not released it yet, but it is working on our prototype.
To connect to the Facebook Graph API, it uses RestFB internally.
If you want to give it a try and give us some feedbacks, let me know, I'll sent it to you by email.