I have App on firebase everything was working fine push notification, phone authentication. but yesterday it stopped working. I search for answers on Stack overflow & other blog. Any help would be appreciated.
Solution I tried here, but no luck ...
Force refresh browser. try login in incognito mode.
Login/Logout many times.
Deleting ios App and Added it again.
Contact to firebase support team, but its 2 day's still no response.
Solution worked for me ...
I Delete the project from firebase and Create a new Project.
firebaser here
Some steps for troubleshooting, that most often help in such situations.
Force a refresh of your browser with cmd-shift-R, to make sure you have a completely fresh version of the Firebase console.
Check the JavaScript console of your browser for any relevant error messages.
If you have any plugins in your browser blocking content (such as ads), please disable those and try again.
If neither of those gives a hint to the cause of the problem, reach out to Firebase support for personalized help in troubleshooting. Be sure to include information about the OS you run on, the version of your browser, and anything from #1.
Related
I've been developing authentication flow on php lib: googleapis/google-api-php-client v2.9.1. Everything was working fine, but after some time while trying to authenticate the google started displaying "Something went wrong" message with 500 in console and after pressing next button "The server cannot process the request because it is malformed. It should not be retried. That’s all we know." with 400 code. But everything works fine if I use incognito mode.
The similar issue is described here and it only occurs on chrome and when user is logged in into several google accounts, works fine if you delete accounts.google.com domain cookies or use Incognito mode.
Is there a way to solve it ?
So to answer my own question the solution was quite simple - after you apply for verification and Google verifies your app this issue disappears without any additional efforts.
I assume that main issue is that if you have multiple google accounts connected to your chrome and you add only some of them to an app as a tester or etc. Google can't handle not connected accounts for security measures and returns an error. Of course the error itself could be handled little bit better.
I hope this answer saves some time for everyone else who is struggling with this issue.
So I'm trying to register a new client on the instagram API. I have a business account and have done the proper steps prior to this. Everytime I fill out the "Register New Client ID" form and submit it, I get an error "The captcha solution was not correct. Please try again." But no there is no captcha for me to fill out!! Looking at the console errors it says the CSP page setting's are blocking this source https://www.google.com/recaptcha/api.js. I'm gonna take a wild guess and say that has the captcha I need that's not appearing..lol.
Anyway, I've disabled all my content blocking settings and JS is enabled on firefox (oh I'm using firefox developer edition btw) and no change. I've also tried this in chrome and safari, no change. I don't have this issue with other sites that use captchas.
Anyone have any idea what's going on?
'preciate it!
Had the same issue here on Google Chrome. Used IE11 (version 11.345.17134.0 to be exact), and captcha displayed instantly. I've successfully registered a new client
I suggest to wait until Instagram team realizes to upgrade their whatever scripts & parameters.
I found myself in the same scenario:
I'm logged on Instagram
I land to instagram.com/developer/clients/register/ over Google Chrome 70.0.3538.102 (no extensions)
No captcha. And I get the following from the console:
ps: I tried figuring out how to submit this specific report, but after several searches I find myself loosing too much time... to make them aware.
Our web app allows users to log in via Facebook. Technically, we are using Facebook OAuth2. We have implemented this login process two years ago. It worked fine until 13th November 2015 but since that day it does not. When our server sends the request
https://graph.facebook.com/oauth/access_token
with appropriate parameters (client_id, redirect_uri, client_secret, code), the response from Facebook has HTTP status 400. The response body is a HTML page saying "Sorry, something went wrong".
On 13th November, there was some problem on Facebook probably.
I have found the following message:
http://www.independent.co.uk/life-style/gadgets-and-tech/news/facebook-down-site-breaks-for-many-people-though-not-for-everyone-a6732906.html
However, our server still gets this error response after a week. We have an instance of the system deployed in the production environment and one more instance in the test environment (with different Facebook account, i.e. with different client_id and client_secret). Currently, Facebook login works fine in the test environment. I am not sure if it worked on 13th November.
Do you have any experience with recovery from such problem? Why does Facebook login work in test environment and does not work in the production environment in the same app? Why did the production instance break on a particular day and is still broken a week later?
Thanks for any help.
I had the same issue. I believe that the issue stems from passing in invalid scope in your authentication requests. Try removing the scopes in your authentication request to see if that works.
One more corner case I found in 2022:
In the App Dashboard, if you choose Facebook login for Business, same error happens. It will go away as soon as you select Facebook Login one.
Finally, the issue was resolved by restarting the servlet container (Tomcat 7). However, I have no idea why.
All of this is using exclusively the login button. Not the API serverside and not FB.login(). It would work for me sometimes and sometimes not and I couldn't figure out why. I would open a new window and it may work, or may not - but it seemed like once broken it was broken.
There appears to be an issue when using the Chrome 'Device simulator'.
Looking at the SDK Javascript (that's to say the SDK that the Facebook Login button uses) it checks to see if the device is a 'touch' device and if so it will use the m.facebook.com domain when requesting the oauth token.
This domain fails m.facebook.com:
However if the mobile device mode isn't activated when the page loads then it uses www.facebook.com and succeeds:
So for me the current workaround is:
Assuming you are developing with the console active.
When you need to reload your page press Ctrl + Shift + M to deactivate the mobile device mode.
Refresh the page
Once the button has initialized press Ctrl + Shift + M to reactivate it again.
If you see m.facebook.com then you didn't do it fast enough, or maybe you're using something like Angular with hot reload and you need to manually refresh.
I got an problem after i create and APIs on Google Developer Console and enable the GCM service,
but i want to add an server key at Credential next to APIs on left hand menu.
But it show me You do not have sufficient permissions to view this page.
Below are the image:
Is that any config i need to add?
I did follow what You do not have sufficient permissions to view this page to clear cache and use incognito mode to login, but still not work.
EDIT
Some time i relogin it work back, when i click to another side and click back it show the error again, and my solution is go to Credential than use top right corner account to logout and relogin , let it redirect you back to Credential, than it work. So is there any solution to fixed it permanently without relogin?
Thanks
It because of you have logged in multiple devices. so u have to log out from all devices. to do this go to gmail.com and log in using your email and password. and scroll down . you can see Details link . Click that link.
it will open new window. there u click
Sign out all other web sessions. than clear history. than do login and try . it will open without showing error.
I got the same problem. After following the below steps it got solved. This may help you as well.
Click on Apis under Api & auth
Click on "Google Play Game Services".
Enable the service.
Optional: enable "Google Play Developer API" as well. Most of the time it will enable by default.
I am facing the same issues.
Try using another browser like firefox - sometimes it works.
but after awhile, same error pops up.
Having the same issue as with you regardless what api i enable.. have tried all the suggestion posted earlier. but none of them worked, but when i tried to change my i.p.. using a vpn. and tried to access it.it worked, i can create or view my api now,tested it with other gmail account to confirm and started from scratch. to my surprise i didnt encounter that issue im having for hours.. no idea why my i.p is being rejected when accessing the credentials area..
I've resolve my issue, it's about the ISP you are using. I tried 3 ISP's and 1 of them got a success all the time, I don't have any permission error.
I had a working hangout app until yesterday - but now now I can no longer launch the app in the developer sandbox.
In the process of diagnosing the problem I have tracked back to simply trying to launch one of the Google sample apps (https://plushangoutstarter.appspot.com/static/simpleHangoutApp.xml) in the developer sandbox.
This fails in the same way as my app: the hangout says loading app along with a lovely animation but never loads.
I have tried this from different Google accounts and OS's but the problem is the same whatever.
The js console shows the following error:
Uncaught SyntaxError: Unexpected token < login.corp.google.com/request?s=oz-autopush-full.plus.corp.google.com:443/u….google.com/js/api.js&maxAge=1200&authLevel=2000000&rpMode=v2&keyIds=Do0:2
Interestingly I can launch the hangout apps (mine and the sample ones) outside the sandbox. For example, https://plus.google.com/hangouts/_/16fae425e33645b520c4b14f71adbdbba843f00d
To me it seems as if Google has deployed a breaking change but I can't believe that there would be no activity on twitter or the google plus developer group if they had.
My questions are:
1) Can anyone launch an app in the developer sandbox
2) If not, anyone got any idea what the problem is.
Thanks in advance for any help. As usual in these situations, I was planning on demoing my app to my colleagues in a couple of days to show them how cool the hangouts api is :(
Neil
There was a problem on Google's side over the weekend and has now been corrected.