Gupshup integrated bot on facebook messenger not working on any pages but were working fine previously(until like one week back). Tested on Gupshup Proxy bot today and they were working fine.
There were some issues with publishing which has been fixed now. Both of the bots JurongNeighbourhoodAgent and latesteclaunch are working fine.
Related
The react app is working fine on localhost. But hosted site is facing some problem as shown in the below mentioned image. Initially it was working fine but after few days it started showing this issue. All of my firebase app is facing the same problem.chrome_console
firebase_hosting_problem
firebaser here
If you're in APAC or EMEA, you may be affected by this outage on the Firebase status dashboard:
Firebase Hosting is aware of some reports of connection issues in the APAC and EMEA regions. We are currently investigating.
If that sounds what you're seeing, I'd recommend following that page for updates.
I signed up for Google cloud platform added a card and got 300$ for free for 3 months. I uploaded my bot there using the app engine and got a link to access it. when I click on it and then close it, the bot works and responds to all my messages. But after a while it stops working again until I click on the link provided by google. What might be the problem? Is there any way to fix this? Please tell me how I can configure everything correctly so that my bot is not disabled. Maybe there are other free services? Thank you in advance
It is because if app engine does not receive any requests it stops , it depends on your app engine settings when it sleeps , you can create 2 app engine servers and make them sending GET requests to each other so they will not sleep , this is what i did and it worked fine
llhi,
I have configured Facebook connection thru Bot Framework, which has requested to configure one single Facebook page, app, and then token. Is it possible to indicate how to manage several Facebook pages thru the same Microsoft Bot Framework? If not possible, what are the available options?
Thx for your feedback,
Regards
If I understand your question correctly, you would like a bot that works across several Facebook pages? Do to this you'll need to create multiple registrations in the BotFramework for your bot (one for each Facebook page). Each registration can call back to the same bot (just use the same webhook).
A bot can configure on multiple fanpages. I tested it, just enter new pageId and PageToken then resubmit. It still work well.
The problem is the UI configure BotFramework not display all fanpages that authorized. When click deauthorized, it delete all pages. We can wait dev team upgrade it or create multiple registrations like Lars said . I think it will work better soon.
I have a GAE app that periodically requests a user's activities from G+. I'm using the google oauth client api for java.
This has been working fine for months with literally no code changes (I'll post the code if required, it's all taken straight from the oauth client project examples, using GoogleAuthorizationCodeFlow).
However, a couple of days ago this changed. Now, without fail from the GAE instance, I get this exception during token refresh:
java.net.SocketTimeoutException: Timeout while fetching URL: https://accounts.google.com/o/oauth2/token
at com.google.appengine.api.urlfetch.URLFetchServiceImpl.convertApplicationException(URLFetchServiceImpl.java:141)
at com.google.appengine.api.urlfetch.URLFetchServiceImpl.fetch(URLFetchServiceImpl.java:43)
at com.google.api.client.extensions.appengine.http.UrlFetchRequest.execute(UrlFetchRequest.java:77)
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1009)
at com.google.api.client.auth.oauth2.TokenRequest.executeUnparsed(TokenRequest.java:299)
at com.google.api.client.auth.oauth2.TokenRequest.execute(TokenRequest.java:323)
at com.google.api.client.auth.oauth2.Credential.executeRefreshToken(Credential.java:586)
at com.google.api.client.auth.oauth2.Credential.refreshToken(Credential.java:505)
at com.google.api.client.auth.oauth2.Credential.intercept(Credential.java:266)
Now this still works fine from my local machine. There are no reported quota issues on the GAE dashboard or on the Google APIS console for this app. Billing is enabled for the Google APIs console project, but not the GAE app.
I note there's a similar looking issue in a python app reported here, but that has no responses so far.
This has been happening continuously for a couple of days - the app tries once an hour for a hundred or so different users. If I limit the app to only perform this for a single user it still occurs.
Here is what I've noticed:
the service started working for me two days in a row at about 10:30 pm and then stopped working again next day at about 8am(both Saturday and Sunday this weekend: June 8-9 2013). Really looks like high load issue.
Will hope that Google fix it soon.
I absolutely made no changes in my code on app engine server. It just started working and then stopped working.
P.S. also it looks like it takes always about 40 seconds before server gets SocketTimeoutException every time I try to sign in with Google plus.
P.P.S. and yes it works on my local instance of Google App Engine.
We are still experiencing the same problem: at around 1pm-2pm GMT of every day the OAuth2 refresh token method starts failing with a time out error, for 10-14 ours. After that time it works again.
A similar issue is posted here: https://code.google.com/p/google-glass-api/issues/detail?id=99.
Lorenzo
Update: it seems the problem has been solved.
See https://groups.google.com/forum/?fromgroups#!topic/google-appengine-downtime-notify/TqKVL9TNq2A
I think it may have been due to this issue:
The problem with Google App Engine URL Fetch service to Google
Accounts authentication endpoints was resolved as of 5:15 PM
US/Pacific on June 7, 2013. We apologize for the inconvenience and
thank you for your patience and continued support. Please rest assured
that system reliability is a top priority at Google, and we are making
continuous improvements to make our systems better.
https://groups.google.com/forum/?fromgroups#!topic/google-appengine-downtime-notify/TqKVL9TNq2A
This timeout issue is happening consistently for on two app engine instances running my app anyCloud and staging.anycloud.co). I can not get an access token or refresh an existing one and consistent with the other posters, the same code works fine when running in a localhost dev environment.
We have developed a website, which was wroking fine until some days back, but suddenly it stopped working on custom domain. It still wroks fine on appspot subdomain. I rechecked all the settings, they are all okay as per gae guidelines...
http://www.thesudokutimes.com/ (This one is not working)
http://thesudokutimes.appspot.com/ (It is accessible here)
Can any one suggest what could be the problem?
This does not seem related to Google App Engine but to a more generic DNS problem.
Using Dnsstuff tools you can see that your domain name was updated by your Registrar the 23th november 2010 and the IP for thesudokutimes.com can't be determined.
I suggest you to double check your configurations and contact your Registrar asking for support.