No output from formatter after upgrade to 4.x (using oEmbed API)

Here's a patch.

I committed your patch. If you really have access to the oEmbed API, then could you please help me out testing another functionality that is connected to this module: 📌 Check if it still works when rendering post with Facebook Oembed API Postponed: needs info All we need is to know is what exactly is returned from the oEmbed API and rendered with the field. If you could open a webpage with a Facebook media and right click See source (CTRL + U) and paste the field's HTML to that issue, so we'd be really thankful if you could help us out there.
Neither me or my collegues could get the permission from Facebook to use oEmbed API. I just don't understand why they are rejecting us and not enabling these for development.

Thanks for the commit!

I'll certainly test if I can. Our set-up is a bit unusual in that the embeds generated by this module are rendered only for admins/authorized users (it is a decoupled site). I'll try to have a look in the next week or so.

I did a lot of research (mostly reading about others' experiences) and took copious notes before and during the application submission process, which was approved within minutes, so if you're still aiming for app approval I may be able to help.

I understand. I tried to apply twice with an existing news site as they use Facebook embeds from politicians and social groups for referencing source material. We went through business verification but they declined both of our requests for oembed with no clear explanation after weeks. All we need to see is what response or raw HTML comes through the oEmbed API exactly when it is working (does it include a script tag with SDK, iframe etc.). After that we can mock the oembed service, write tests for it etc.

Automatically closed - issue fixed for 2 weeks with no activity.