My app is a Business Type and has advanced permissions for oEmbed Read. However, I received a message from Meta saying "oEmbed Read to be deprecated for Business Type apps on 05/16/2024".
Meta said that if we change the app from a business type to a nontype, we can continue to use the oEmbed Read advanced permissions. But won't changing to non-type cause any major problems? For example, the permissions that were previously only available for business type will no longer be available.
The following page on Meta's App Type says "Apps designated as None are apps that don't fit any of our app types. Apps designated as None contain combinations of some, but not all, of the Apps designated as None contain combinations of some, but not all, of the consumer and business permissions and products. https://developers.facebook.com/docs/development/create-an-app/app-dashboard/app-types/
I am very afraid to move to None Type because there is no mention of Available Products and Available Permissions available in None Type. Does anyone know what Available Products and Available Permissions are available for None Type? Or can you give me some advice?
Below is the full text of the message received from Meta.
Title"oEmbed Read to be deprecated for Business Type apps on 05/16/2024"
On 05/16/2024, we’re deprecating Advanced Accessto oEmbed Read feature for Business Type apps.
Action Required
If your app(s) need to stay on the Business Type, please downgrade to Standard Accesslevel for oEmbed Read. Please note, once downgraded, you will not be able to regain Advance Access level again.
If your app(s) need to maintain the Advanced Access level of oEmbed Read
Create a new None Type app
Or, if no actions are taken before the deadline, your app will be automatically migrated to None Type app while keeping Advanced Access to oEmbed Read feature on 05/16/2024.
If your app was previously usingFacebook Login for Business but has been changed to None type, it will switch to using Facebook Logininstead. If the login dialog for Facebook Login for Business is invoked via configuration id, the login dialog might fail to load as Facebook Login does not support the 'config_id' parameter. You will need to replace the 'config_id' parameter with the 'scope' parameter instead.
After 05/16/2024, all Business Type apps can no longer use oEmbed Read to make API calls and cannot make new review requests for oEmbed Read.
February 17

Tag:-

2 comments.

  1. Eugenia

    We have the same problem. We asked for "oembed read" permission 2 years ago to get the thumbnail url and embed instagram posts in our website. Now we are faced with a fork in the road: either stop embedding posts or take the risk of having our app go from like "Business" and "None" but not knowing what we are getting into.
    What will you do?

    Reply
  2. Philip

    I also have this issue. Our app relies on the Page Public Content Access feature/permission and Oembed read. I cannot find anything to confirm if this feature will still be available if the app switches to None type so that we can hang on to the Oembed read permission.
    Watching this space to see if there is a resolution.

    Reply

Add a new comment.