UPDATE: Pinterest support got back to me and confirmed that the Ver. 1 API is broken. Instead of fixing it they have offered to expedite my new app approval. I heard back from them quickly, but it's been almost a week now from submitting the materials they requested for the new app. I submitted them the same day they asked for them.
I'm having essentially the same problem that this user was:
Pinterest Authorization failed
This is an app that has been approved and working for years and we have started getting this error just in the last week when sending a GET request to https://api.pinterest.com/v1/me/boards:
{"status":"failure","code":3,"data":null,"message":"Authorization failed.","endpoint_name":"get_own_boards"}
In the header I of course have the access token, which I had just received from Pinterest successfully:
"Authorization: Bearer Ah-ObYMmQFc-(REDACTED)"
The other strange wrinkle is that when I try the same request but with the access token from the Pinterest user that owns our app on Pinterest it works as expected.
I know that this has been an issue previously, but I didn't see anyone reporting it currently. The other thing is that this endpoints are being deprecated, but the new ones are only in Beta. I have an application in for the new API, which I would love to switch to, but I don't know how long that will take. Can anyone please help with this?
I went through the approval process for V2 but they denied it. They are very strict. I don't think that a App gets approval if it's not from a known brand or company. So, say goodbye as a single dev to use the Pinterest API anymore.
I'm getting the same thing with one of my apps, it seems that they shut down version 1 before opening up version 2. I've had an app that has been working flawless a while now and stopped working a couple weeks ago.
As of right now, i had to create a new app in the version 2 of their system and waiting for approval. It's been about 2 weeks and of trying to get approval but still waiting.
Create a new app and reach out to support is my best bet, haven't found any documentation for their new API or any blogs related to it being deprecated.
Pinterest support got back to me and confirmed that the Ver. 1 API is broken. Instead of fixing it they have offered to expedite my new app approval. I heard back from them quickly, but it's been almost a week now from submitting the materials they requested for the new app. I submitted them the same day they asked for them.
Related
Can anybody tell me that is it necessary that tiktok webapp should be approved for getting access token cuz my app is under reviewed and when I go to authentication page for callback authorization after login it is showing error
I followed all the instructions that were given in there documentation but i am stucked at the call back authorization
The status of your app should be Live in production. They usually give you feedback if there are any issues and in case it's declined. You have to make fixes accordingly to get the API functionality to work.
The reviewal process shouldn't take longer than 3 working days.
Last year I developed a chatbot with Microsoft Bot Framework that I integrated in the Facebook Messenger of a page. Everything worked fine until 16th of December (last successful log). The page is not used by a lot of people therefore the application might have worked also longer than that.
Today I tried to use the chatbot again and I did not get any response. In the Logs I just found the error message "Operation returned an invalid status code 'Forbidden`".
After a bit of Debugging I found out that the problem is sending messages back to the Facebook Messenger.
context.SendActivityAsync(...)
I did not change any configuration within my Azure Bot Channel registration recently. I am aware of the privacy changes within the Facebook API, but as I already struggle with sending a simple text response like "Hi" I assume that cannot be the problem. Also the permission scheme has changed for Facebook apps. I have the permission for "pages_messaging". Do I need another permission now? Or did I miss another change in the Facebook API?
Technical Details:
Facebook API Version v6 (tried also v9 but no change in behavior)
Chatbot based on .Net Core 2.1
Bot Builder SDK v 4.11
Any hints what I did wrong or where I can look for further information is much appreciated.
Edit: I tried to add a new page to my Facebook App and get following message:
There is a hint that a permission is missing, but I cannot find out which one I require. As I only send responses to FAQ's and if required handover to the customer service inbox I just requested the "pages_messaging" permission. Do I require any other permission now?
I found the problem. For everyone that might have the same problem:
In our case the administrator that added the Facebook pages to the application was removed from the admin permission list of the pages. After re-adding the admin permissions for the pages the bot started working again.
I am developer and maintainer of an Angular web app which uses Google OAuth. This works normally.
Last week the app users (me including) started receiving standard Security alert emails from Google (no-reply#accounts.google.com) on a daily basis. The Email says "Appname was granted access to your Google account". This is of course bad signal to the users.
When clicked on "Check Activity" in the Email it always says:
Unrecognised device
X hours ago
Unknown (location)
This is the case for all users tested on many different devices and IPs.
Recently I have upgraded from Angular 5 to Angular 7 if that might help.
Also recently I noticed absolutely the same behaviour when I sign-in to Dropbox using a Gmail. The application I am responsible for is not storing session data for privacy reasons so the users are asked to Sign-in with Google every time they want to use the app. I noticed this behaviour just a week ago (devices and locations not recognised) by Google.
The google group (https://groups.google.com/forum/#!forum/oauth2-dev) redirected me to Stackoverflow. Any help is much appreciated! :)
We are sending notifications to users when they approve certain scopes. That list is expanding and more apps will see the notification.
Thanks for the feedback. Looks like the unrecognized device was an issue and we have rolled back that experiment.
Ideally an app should see the notification only once and for non basic scopes (basic scopes being email, profile etc).
A client is using Coschedule to push updates to LinkedIn via their employees' profiles. They noticed recently that Coschedule is giving error messages when they try to push updates to employee pages. The Coschedule technical team did some digging and determined it's an issue with LinkedIn's API, which they believe may have been updated recently (?).
Errors started occurring a couple weeks ago, the app was previously running fine.
They are hoping for more information on LinkedIn's API / how to resolve this as soon as possible as it's generating multiple error message and error emails per employee per day.
Thanks!
Tia
The outage we saw a few weeks ago was due to LinkedIn depricating the version of OAuth we used to connect LinkedIn profiles/company pages to Calendars. We've since switched to OAuth2, and if your client or your team is still having issues and seeing authentication errors when trying to send out messages, we recommend doing a hard reset of those LinkedIn profiles: https://help.coschedule.com/hc/en-us/articles/216529237-Hard-Reauthentication-for-Social-Profiles-When-Auth-Token-Keeps-Failing#LinkedIn
Best practice is to use an incognito browser window as well.
If you're still getting stuck, reach out to our support channel (support#coschedule.com)and we would be happy to take a closer look!
I was able to connect to the LinkedIn API for about two months and everything was correct. Was wondering if there has been any change to the API lately to block my app like so?
The app was in development stage and mostly 5 hits a day against their API.
It's not you, it's LinkedIn. See others complaining about the same issue: https://twitter.com/search?q=linkedin%20oauth