Hi am new to Ruby On Rails. I got an email from intercom regarding depricating API keys. Am using Intercom-rails but i didnt see any updation changes in git can any one help me thanks in advance.
I found that Intercom ruby needs to be updated to access token hence i replaced my api key with access token it works fine for me. I am using api for create event and current user manager.
Related
I am working on an Angular 7 application that uses GraphAPI. I am trying to create an online meeting from this application.
Each time I send a POST request I get 'Forbidden' as response. I have used apis's with Delegated permission before and it works.
Since online meeting requires 'Application Permission' I am not sure where to specify it. Could anyone help me with this?
You specify the permissions in App Registration > your app > settings.
You have a problem with the way you are trying to access the token. I used to get the same error however, got resolved by passing userName and Password as well in the auth request and using grant_type as password.
Few months back I prepared a demo on Fitbit oauth2 public APIs in which I used to log in with a particular user and get his activities. It was working fine. But recently, I opened the demo and tried to log in with the same user but it is not getting logged in and repeatedly giving me this error.
I tried to change the client secret key of this demo app which I registered on Fitbit but nothing happened. I am stuck here.
There is problem with the format of Callback URL. I think Fitbit has recently changed it.
Earlier, the format of Callback URL was "demoapp://" but now
it will be "demoapp://something"
Please refer to my answer on other question.
Setting up Fitbit api in xcode Swift
In a recent version of Firebase, getTokenForcingRefresh was deprecated. I'm using it because auth tokens expire and I need to be able to refresh the token and retry a rest command when it fails. What is the right replacement for this API?
Looks like you need to use getIDTokenForcingRefresh:completion API instead of deprecated one.
Please take a look at FIRUser class documentation here:
https://github.com/firebase/firebase-ios-sdk/blob/master/Firebase/Auth/Source/Public/FIRUser.h#L307
I'm using Parse to login users with Facebook (on ios, using the Facebook and Parse ios SDKs).
I always assumed that the Facebook SDK was using the latest version of the API by default, meaning that Parse would probably do the same.
However, if I check the Facebook tokens stored by Parse in the authData field using the Facebook Access Token Debugger (https://developers.facebook.com/tools/debug/accesstoken), it seems that my tokens are generated by a call to API v1.0.
In the User ID field, it says 'User last installed this app via API v1.0'.
Also, the Scopes field contains permissions that I didn't request (like basic_info, user_location, user_friends)
Anyone knows why ? Is this normal ? Any chances that my app will break on april 30 ?
Thanks !
Update : This actually seems to be random. Some tokens have the User ID field that says 'User last installed this app via API v1.0', and some others have 'User last installed this app via API v2.x'. And they are all users who signed up today, with the latest version of my app !
Using Parse with Facebook login for iOS and Android won't require any changes, and your app won't break on 4/30. We're upgrading our side of things and will be using v2.3 shortly.
I want to edit my bundle id that was registered in Google APIs Console for Google+ login.
Answer on this question tells me how to do that but I don't see Client id and secret under API Access as he is saying. May be because Google APIs Console has changed.
Does anyone know how to edit currently registered bundle id for Google+ integration in Google APIs Console?
Edit : I could not see client id and secret because that was somehow got deleted. I created a new one. Replaced client id with existing. But still same error.
In My case I added wrong bundle Identifier.
Follow following steps to get secret and client id
1) Open API Access in google API console. Then click on create a client ID.
like...
2) Fill Following form.
3) you will get client id
I solved my problem by creating a new client id. Make sure that Google+ API is enabled in google console.