Hello, we are currently implementing an inbox in our application which should make use of instagram direct messages via webhooks. Our rejected review states that we must implement the following: 1. user sends a message to an instagram business and the message shows in the inbox (works) 2. user recalls that message and it must get deleted from the inbox in our app too
The issue is, that when a user recalls an instagram direct message via the mobile app, we are getting the webhook notification as expected and we can delete the message. But when the user recalls the message via browser, it does NOT fire ANY webhook. (??)
Help: because we need the 2nd step to work for our permission "instagram_manage_messages" - does any of your know what the issue is here? Has anyone dealth with it? How did you get through the app review with that? Seems like app review for that permission is impossible if the webhook does not fire..?
This is a very crucial feature for our app, so any input is greatly appreciated!
I have seen another thread on here discussing the same thing, but there was no solution found. (https://developers.facebook.com/community/threads/301113412595248/)
Thank you very much in advance!

Issue Description: While making an API call to {InstagramGraphApiID}/tags, we received a post that does not correspond to the photo tag account associated with the specified InstagramGraphApiID. As per the expected behavior, the API should only return posts that are explicitly linked to the provided tag account. However, the post retrieved appears to be unrelated, leading to inconsistencies in the data.
Expected Behavior: The {InstagramGraphApiID}/tags API should return only those posts where the photo tag matches the tag account associated with the given InstagramGraphApiID.
Actual Behavior: The API is returning a post where the photo tag does not match the specified InstagramGraphApiID, causing data inconsistency and incorrect association of posts.

Hi Meta Team,
We are observing an issue where Instagram Messenger text events are being received as JSON. This has been noticed across multiple accounts.
Could you please confirm if there is any ongoing issue or anomaly related to Instagram Messenger events? Is anyone else also facing a similar issue?
Kindly assist on this at the earliest.

Hi, I have been using Facebook Login for authentication into a Rails application, that uses omniauth and omniauth-facebook. Graph API is used only for user authentication. The integration has been implemented and working for more than a year. There are no issues with the integration itself, however I noticed a change in the flow. I would like to find out if this is intentional on the Facebook side or does this need tweaking on the application side.
When a user is already signed into Facebook in his browser and then he opens another tab in the same browser to sign into the Rails application, he clicks the Facebook icon and this click initiates a request to the Facebook and signs user into the Rails application.
During the integration and until quite recently, in above cases user would get a quick redirect to the Facebook and back to the Rails app, where he would be authenticated. So the entire authentication flow required user to click the Facebook icon in the Rails app. This applied only to cases when user is already signed into Facebook at the moment he clicks the Facebook icon in the Rails app. It's a different story if user is not signed into Facebook.
Recently I noticed that the flow described above has changed, now if a user who is already signed into Facebook clicks on the Facebook icon he is redirected to Facebook page with a modal, page url is something like https://www.facebook.com/privacy/consent/gdp/?params.....¶ms%5Bsteps%5D=%7B%22read%22%3A%5B%22email%22%2C%22public_profile%22%2C%22baseline%22%5D%7D¶ms%5Btp%5D=%22unspecified%22¶ms%5Bcui_gk%5D=%22%5BPASS%5D%3A%22¶ms%5Bis_limited_login_shim%5D=false&source=gdp_delegated
Modal on the page says: "Rails app is requesting access to: Your name and profile picture and email address." or "You previously logged in to Rails app with Facebook. Would you like to continue?"
And there are two buttons "Continue as Username" and "Cancel".
This requires the user to perform one more step in the authentication flow (click a continue button on this confirmation modal) and I would like to ensure seamless authentication as it was before so users don't have to provide this confirmation if they are already signed into Facebook within the same browser.
Unfortunately, I cannot recall exact date when the flow has changed but I remember the flow being seamless when I integrated it less than a year ago. I wonder if this is something intentionally enforced by Meta or is it something that can be fixed on my side?
Thank you.

Is it possible to use facebooks free apis to get a count of the unread messages in a personal messenger and what would the limitations be?