We are using webhooks for "instagram" resource and then executing some logics based on type of webhook we receive. One of the webhook in the list is the "message" webhook which we were receiving till 16th may 2022 around 1:30 PM IST and then it suddenly stopped triggering from facebook.
Surprisingly we are still able to receive webhooks for other event types for same "instagram" resource from facebook (like 'message_reaction', 'comments' etc)
I don't know what is wrong here, as I haven't made any changes to the developer account which I am using for testing these webhooks. Can anyone help here, as we are stuck at a very important step in our product lifecycle?
Also I have started a thread on Facebook community also, Link to the same can be found here
Screenshot to webhook setting page
I faced a similar issue couple of days ago, what I suggest you to do is first you can test your webhook using the the tests FB provides and make sure everything works fine on your side. If so, the threads and questions on FB community are rarely getting answered so I suggest you to report a bug on your app from here and the guys from FB are really helpful and will communicate with you within 2 working days max and follow up with you till you solve that issue.
Related
I connected IFTTT with Google Assistant in order to test some custom commands.
The idea was to tell the assistant:
Ok Google, this is, John
And I wanted the Assistant to reply, saying:
Hi John, nice to meet you!
Note: this is an example of the command I created. As I said before the original command was deleted (around November 2018) in IFTTT the same day I disconnected my account from the service.
It worked as expected but then I noticed that all the core commands were replaced by the custom command created in IFTTT.
For example, simple commands like:
Ok Google, what time is it?
Returned:
Hello what time is it, nice to meet you!
Since then (November 2018) I have tried all sort of things:
I have deleted the custom commands in IFTTT
I have disconnected IFTTT from my Google Assistant Account
Deleted the cache in Google App in my android handset
Delete the history of voice commands at https://myactivity.google.com
Restored Google Home device to factory settings
Looked into https://developers.google.com/actions/ to see if there was a way to DEBUG or RESTORE my Assistant. Unfortunately this only allows me to create apps to be used with the Assistant.
But nothing seems to fully restore the Assistant's behaviour to where it was before the integration with IFTTT.
Update: After all the things I have tried it seems to be improved (although not totally fixed).
I mean, now it does not reply with the custom command created in IFTTT but instead it replies saying Sorry I cannot process that request
For example, when asking simple commands like thew the following:
Ok Google, what time is it?
Ok Google, what day is today?
Ok Google, what can you do?
It replies saying:
Sorry I cannot process that request.
This only happen in the language I created the custom command for. If I ask the same question in another language it works fine.
Also, this only happen in the Google Account I used to created the custom commands. If I create a new Google Account and activate the Assistant in there it works fine in any language.
Same issue reported in Google forums
https://support.google.com/assistant/thread/252800?hl=en
https://support.google.com/assistant/thread/662913?msgid=662913
So here are the questions:
Is there a way to DEBUG/Fix this issue? (apart from creating a new Google Account which is my last resource)
Is there a way to restore the Google Assistant to its defaults?
Update2: I recently noticed (maybe I am going mad) that if I replace the word what with something else, the commands actually work.
For example if I say:
Ok Google, what time is it tell me the actual time?
Ok Google, what day is today which day is today?
Ok Google, what can you do how can you help me?
I get the right response from the assistant.
I run my own VPS in Amsterdam where I have a MySQL database that is being populated and maintained using ASP.NET. It's a Windows Server.
I use this API for four of my existing Android apps (published and working) with a few thousand users who never had any issues connecting to the API through those apps. Recently I finished one of the apps on the iOS platform and it got rejected because Apple couldn't get it to load any content, or it would get stuck on loading without ever returning anything (after we implemented a loading progress animation). After a lot of messaging between me and Apple's review team, they ended up accepting my app to be passed through review even though they never got it to work (or so I believe, they just said they would re-review it and it suddenly got approved after 7 rejects). None of my friends, family or users ever experienced any issues like this on either Android or iOS.
A good friend of mine who did most of the work on the API is also from the USA, which makes me doubt it's a location problem.
I must note that pretty much 99.99% of my users are Dutch and all my projects are build for Dutch users.
Does anyone have experience or ideas in this field? I'm about to publish an update for the already published app and I'm afraid they will reject it because of the same issue.
The exact message I got at first was:
Specifically, upon launch we found that the app failed to load any content.
Changing the API calls to be over HTTPS seems to have fixed the issue, Apple now has access to my API through all my apps.
I have an iOS App on the App Store, and it connects to Google Drive. In the past week or so, I've noticed two new problems in my live app.
The App suddenly stopped logging in. I would get a 401 - invalid_client. I found a lot of questions/answers for this problem, but they were all for people who couldn't get it working. Mine was working for about two years and then stopped working a couple of days ago. After trying a lot of things, I found that I was using <id>#developer.gserviceaccount.com as my Client ID, and when I changed it to <id>.apps.googleusercontent.com it worked again. I don't know why this change fixed it, and even knowing that this fixes it, I can't find if this is the correct/appropriate solution.
I explain my second problem, which is very specific here, but skip to the next paragraph to get to the point. The second issue is a a result of Google changing the way their API calls respond, and this is why this wasn't an issue when we submitted the latest version of the App to the App Store. Google has changed the way the explicitlyTrashed property of their GTLDriveFile class. Per their spec, this property should be either an NSNumber containing Yes, or null. They have recently changed it so that it is always an NSNumber set to either Yes or No. This is what's breaking our functionality.
Anyway, these are two changes Google has made on their end recently that currently has my customers on hold since I have to fix this and push it out. My question is if there's a place to keep up with these changes that Google is making recently. Also, if someone knows or can point me to why the first issue is happening, I would greatly appreciate it.
For the first issue, the reason why it got resolved by using [id].apps.googleusercontext.com is because it it requesting an authorization token from an app to the server, as opposed to a Server to Server transaction using impersonation ([id]#developer.gserviceaccount.com). This is the right solution for both android and IOS apps requesting a token.
As for your second question, the best way to keep up to date with the latest changes is through their official blog: http://googleappsdeveloper.blogspot.com/
Another resource is the G+ Google Drive Developer community: https://plus.google.com/communities/107264319205603895037
I'm trying to setup a test iOS app to see what I can do with the Razer Nabu but I'm struggling with the patchy documentation. The example for authentication only mentions a 'fitness' scope and with that I don't seem to be able to send a notification to the band (the main thing I'd like to try).
When I try and send a notification I get Operation 36 returned and no notification on the band so I assume that means it failed (return codes from the SDK aren't documented it seems).
Does anyone know if there is a different scope for notifications? I tried 'notification' and 'notifications' but they resulted in failure to authorise in the Nabu Utility app.
Any help or pointers to documentation/samples/guides I might have missed would be very helpful!
NB I managed to get authorised with the 'fitness' scope and read some fitness data so everything's working except for the notifications!
Having got in touch with the Razer support guys and talking to this lovely chap called Brandon the issue was that I had the Nabu Utility app from the App Store and the version from the developer site was actually more up to date in this respect, so getting that one installed (and uninstalling the App Store version) made everything work correctly!
I am working on phonegap with ios and using facebook login.
but on feb 6, its giving errors to users while login to facebook.
When logging into the app using Facebook - the dialog shows this message: "An error occurred. Please try again later.
I go through fb manual and enable migration in "February 2013 Breaking Changes".
it still not worked.
Can any one help me ?
Edited :
I reffer to facebook DOC and found this
"The following change will go into effect on February 6th, 2013:
End of custom actions for content consumption
We will no longer show Custom Open Graph actions that were published simply by a user consuming content. If you own one of these actions and it was previously approved, you will have received an email from us. Developers should stop publishing these actions as doing so will return an error starting February 6th. The only actions that can be published upon a user simply consuming content are built-in actions. For more info, see this blog post."
the solution given over there is to make migration oprion from "disabled" to "enabled" which i do,even they give me confirmation that problem resolved but problem is still on.
Working :
Its little surprising but now both of my links working well as describe below in answer.
Solved:
i am able to login now,there is little change in facebook doc for using graph api.
my issue solved by just replacing url from.
"https://graph.facebook.com/oauth/authorize?client_id=404196699634359&redirect_uri=http://www.facebook.com...."
to
"http://facebook.com/dialog/oauth?client_id=404196699634359&redirect_uri=http://www.facebook.com..."
And finally my app workes as before.
special thanks to this
http://developers.facebook.com/bugs/207955409343730?browse=search_5111f1ed718835f53574450
For people like me who know just enough to be dangerous and nothing more... I have no idea where this oauth URL lives and where to change it. Is this a facebook App settings? Is it a change in the src fodler? I can't find this link anywhere in my code to make the correction.