fafafacela

Me too. Running WordPress 4.7.2. Seems to have coincided with Facebook password change.

Fatal error: Uncaught exception ‘Facebook\Exceptions\FacebookAuthenticationException’ with message ‘Error validating access token: The session has been invalidated because the user has changed the password.’ in ../wp-content/plugins/fb-instant-articles/vendor/facebook/graph-sdk/src/Facebook/Exceptions/FacebookResponseException.php:89 Stack trace: #0 ../wp-content/plugins/fb-instant-articles/vendor/facebook/graph-sdk/src/Facebook/FacebookResponse.php(210): Facebook\Exceptions\FacebookResponseException::create(Object(Facebook\FacebookResponse)) #1 ../wp-content/plugins/fb-instant-articles/vendor/facebook/graph-sdk/src/Facebook/FacebookResponse.php(255): Facebook\FacebookResponse->makeException() #2 ../wp-content/plugins/fb-instant-articles/vendor/facebook/graph-sdk/src/Facebook/FacebookResponse.php(82): Facebook\FacebookResponse->decod in ../wp-content/plugins/fb-instant-articles/vendor/facebook/graph-sdk/src/Facebook/Exceptions/FacebookResponseException.php on line 89

Plugin not offering Facebook reauthentication, just fatal error. Also locks up entire plugin page so can’t edit, deactivate or delete Instant Articles for WP plugin.

Thank you for your assistance.

We will do so, thank you. I would like to emphasize for others who may encounter this issue, and read this information, that we are currently receiving emails from all other plugins that generate them — except from the Publish to Apple News plugin.

OK, thank you. The plugin’s Enable Debugging option is set to “yes.” We are receiving emails from other plugins (like Wordfence) that generate them. Same email address (a WP admin email address).

• This reply was modified 8 years, 1 month ago by fafafacela.

The update to 1.1.9 did not fix the issue we are having. Component Alerts was set to warn. It was changed to fail today to see what would happen. Debug mode was enabled a couple of days ago, which was when we began to see the “The following components are unsupported by Apple News and were removed:” message in the admin area when posts were published or updated. Unfortunately no email is being received. I did change the email address to see if one was being blocked or filtered, and checked junk mail boxes, but no emails related to the app’s debugging have been received. I thought perhaps changing Component Alerts from warn to fail would send the email, but it didn’t seem to change anything. Thanks for your continued troubleshooting.

Thanks for your reply. A link is: https://tchlp.com/2dO07hb

I’m not sure if this is pertinent, or points to something helpful in particular, but with the app’s debugging feature enabled, we now see the following message display when a new post is published, or an existing post is updated:

The following components are unsupported by Apple News and were removed:
div
div
empty body component

This debugging message accompanies the original error message:

There has been an error with the API: The attachment article.json could not be included in the request because it was empty.

Thanks again.

Yes, it is still occurring. We have “Use Remote Images?” set to “yes”. The plugin debugging option is also set to “yes” but no emails appear to be generating with an API response.

There are no Publish to Apple News-related PHP Notices in the debug.log at the time the “There has been an error with the API: The attachment article.json could not be included in the request because it was empty.” displays.

Thanks for your help.

We have the same issue. @pxforti were you able to resolve it? If so, would you please post how you did it? Thank you in advance.

Yes. It is set to Full (strict). The green “Active Certificate” badge is present. The setting was last changed 7 months ago. Thanks.

Thank you for your prompt response. No errors, but deactivating the plug-in returned the functionality to normal (i.e. returned the ability to edit existing posts, and add new posts, without getting the blank white page).

Running WordPress 4.6. Updated the plugin to 3.1.2 today. Identical issue still exists. Thanks for your help.

Yes, it is fixed in 2.3. Thank you.