Facebook API quit working. why? - api

I have an Facebook API that connects to Facebook, pulls the users name, and updates their status. Up until at least Monday afternoon, it was working properly, but as of Tuesday afternoon, it hasn't worked. I have tracked it down to the fql_query call in the api file, that is not returning the user info. When I do a login, I get the user key and the session key just fine, and save them to my DB. Has there been any API updates? I checked the forums and there were a handful of post asking why their api's had suddenly quit, but none of them have a reply or resolution.
Any ideas?

It is currently a Facebook Server issue. There is no estimated time on when it will be fixed. It maybe a while.

Related

How to get Delphi to read a logged-in webpage from the default browser - not twebbrowser

I am trying to read data from a webpage that requires a login. I could use twebbrowser and have the user login through that, however, the point is to not allow my app to handle any security credentials, even through twebbrowser. My hope is that the user would login on their default browser, and then my app would load the page as a logged-in user without any credentials going through my app. I swear there was a time, many moons ago, when I was able to do this. However I can't seem to get it to happen now. Is this possible? Or any other suggestions for connecting to a logged-in website without the credentials going through my app? Thanks in advance.
Additional info:
What I am trying to do is write an app that reads purchase history from a rapid-fire sale website (new item every few minutes) and keeps a running total in real time while also warning the user if something comes up for sale that they've already purchased (because the web site repeats things that didn't sell out). I prefer to keep my app as only a data aggregator, ie read-only, completely separated from logging in, purchasing, etc. I don't want people worrying about entering their password or credit card in my app.

Google one tap sign up/sign in approval request

I requested one tap signup/signin for website API as documented in https://developers.google.com/identity/one-tap/web/
However, there has been no update or hear an update from them for more than a week. Does anybody know how long it usually takes to get the request reviewed?
Thanks
I got mail back from them after around 3 weeks of submitting the form.
They said currently you won't be granted access to API. However, they are in the process of including some additional security from their side and it may take a few months. We can hope to get API access then.

Google oauth asks approval every time

I write Delphi/Lazarus app which reads and writes many Google Calendars for single user (me).
When I started I wrote ClientID and Client Secret in my code as constants and used then fine. I was prompted by Google for my app approval once, copy/pasted that key in my app and it worked fine. (60 days? ago). I have not changed anyting in my code or Google account settings since then, but now Google ask for my app approval every, every time. I do save refresh token every time when I close my app. Currently I am the one and only user of my app, and I would it to quietly fetch me my calendars on startup.
Only thing I can think of is that I created Brand Account for my Youtube channel, but I did not notice if app approval question started right after this. Seems unrelated, or is it?

Google Developers Console - Oauth consent screen configuration doesn't save the input

I'm trying to connect my application with Google calendar to receive data. I registered a new application in Google Developers Console, activated Google Calender API and tried to configure the Oauth consent screen.
There I selected my email address, entered a product name and tried to save it.
What it says:
Sorry, there’s a problem. If you entered information, check it and try again. Otherwise, the problem might clear up on its own, so check back later.
What's my mistake here? By Google it is not the best failure description. I also can not find anything else about it in the internet, only that some one suggested to enter a billing account, what I don't want. Any ideas?
I signed out of all Google accounts, signed back in, and then it worked.
I meet the some problem.
I used google cloud with two accounts, i guess there is conflict with two accounts. I clean the chrome browser history and cache , then the problem is solved.
If anyone is here within this last week in 2020, this is a GSuite bug that's being tracked here -
https://issuetracker.google.com/issues/150325704
No one has been able to update or create add-ons. Clearing cache, incognito - none of it has any effect here. Just have to wait for the devs.

Fetching data via Facebook connect taking over 10 seconds

Our site uses Facebook connect. When a new user signs up we ask for permission to pull their interest data, their list of friends, and their friends' interests. Fetching this data used to be a very quick process (couple seconds). Over the last week or so, the time to fetch this data has increase to 10+ seconds. According to Facebook insights, our site is not being throttled. We didn't make any changes to our site.
Anyone else experiencing this issue with Facebook? Have any ideas for how to address it?
Thanks!
As of 1/26 at 7:55 PM EST, the live status page doesn't indicate any irregular activity.
Sometimes this occurs because a user simply has a lot of likes and interests. I would recommend making this operation asynchronous following a flow something like this:
User connects with your app
Get the access token and store it in a queue that a background process can access.
Get all the information you need immediately to make the app work.
Some time later
In a background process, grab an access token from the queue, parse it and handle it however you'd like.
A simpler, although less stable option, is redirecting the user to a page upon installation which makes an AJAX request to that page telling it to download the information from the graph. This keeps the response time low, but does require your user to have Javascript enabled and for them to stay on the destination page long enough for the request to be created.