Token expired & auto renew issues

Hi,

That’s 3.4.8 and it only mentions this change:

Fix. WordPress compatibility

The sooner the better?
’10 days AFTER expiration’ means there is 10 days the feed doesn’t work!

Also, it looks like this fix didn’t work.

– I updated to 3.4.8 on November 9, 2022
– I checked the feed on December 1, 2022 it worked and has an auto renew date o January 1, 2023
– I checked today and it says on the front end ‘Error validating access token: Session has expired on Friday, 02-Dec-22 10:00:31 PST.’ And on the backend it still says the auto renewal is on 1/1. This is a business account and I did not receive a notification.

Thanks
JP

• This reply was modified 2 years, 2 months ago by John-Pierre Cornelissen.

I re-opened this again.

Sending an email alert 10 days after expiration date of a business tokens is not the solution of the reported problem.

Reasons:

1) it means you get the e-mail 10 days after the feed stopped working
2) as mentioned before, it looks like the token is invalidated 1 month before the auto renew date. My last token was set to auto renew on 1 January 2023, but the session expired and got disconnected on 2 December is per this message on the front end

‘Error validating access token: Session has expired on Friday, 02-Dec-22 10:00:31 PST.

I think what really should be done is have a daily crob job that checks if the token is still valid. I it’s not, try to renew and send an e-mail if that doesn’t work.

Thanks
JP

The problem happened again on 3 of my websites.

On all 3 of them, there was a business account connected with the autorenew date set at 2023-03-12.

But when I checked today (2023-02-13) there were connection errors:

1. Error validating access token: Session has expired on Friday, 10-Feb-23 02:15:51 PST (on one of the sites).
2. Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons. (on two of the sites).

So once again, as stated many times before, the plugin get’s disconnected one month before the planned auto renewal date.

Of course there was also no email alert because the expiration date was still in the future.

Also, the error only shows on the front end, not in the back end on the account/feed pages.

This issue is now going on for almost a year. Why are you not able to fix the problem?

If you can’t fix it for whatever reason, why don’t you send out an email to the WP Admin as soon as you detect that the plugin is disconnected? For example:

• check every 24 hours, or
• as soon as the ‘Feed Cache’ is being reset (as specified in the settings), or
• when someone views a page with the feed of a disconnected account, the plugin tries to retrieve the posts, it fails and it shows nothing. That would be the perfect trigger to send an email. Or for all I care with a daily cron hob

Thanks
JP

Hi, how much longer is it going to take to actually fix this issue. It wasn’t fixed after your previous reply and it still isn’t fixed in the current v.3.5.5.

Two months ago you informed me (on Facebook messenger) that your were working on a refactoring of the plugin, but you didn’t reply to my question if you have a time frame.

So I now get this on the front end, expired on 14 april

And the admin says auto renew on 14 may

So as already explained many time before in the past year the token expires one month before it’s renewal.

How difficult can it be to fix the incorrect auto renewal timing?
Or at least send an email to the admin when the token can’t be validated?

Hello @jpnl

We are about to launch version 4.0.0, which includes a fix for this issue. It will be available later this week.

Thanks, I look out for it.

Hello @jpnl,

We have finished the development of version 4.x for Instagram.

We are currently testing it before the final launch.

If you would like to test this version, please send us a DM at https://www.facebook.com/quadlayers/.

Thanks, I prefer to wait until you have finished the first tests.

So I contacted on FB and didn’t receive the beta. Since v4 is released now, I installed it on a test site and I have multiple problems:

1. Several errors 190’s on the front end so I had to reconnect. In the backend accounts page it showed a date in 1970.
2. I deleted the existing account and could only add a personal account (business button was disabled).
3. When connecting to a personal account, the popup showed an account name of one of my customers and I could not change it to my own account, so I connect to the customer account for testing.
4. Now the front end shows other errors
   
   SyntaxError: Unexpected token ‘<‘, “<!DOCTYPE “… is not valid JSON
   Error: 412: Account id 17841404488694177 not found to fetch hashtag media.
   
5. Then I tried to delete the account in the backend, but that’s impossible. It returns an error in the development console and it doesn’t remove the account. See screengrab here https://somup.com/c0hhlh4LpW
   
   Uncaught (in promise) Error: Error: 404: Can’t delete account, account_id not found
   at index.js?ver=381f3c8fe2fdffeb903a:1:2671
   at async F (index.js?ver=381f3c8fe2fdffeb903a:1:2554)
   at async index.js?ver=381f3c8fe2fdffeb903a:1:5188

So it looks like you have some more fixing to do…

Hello @jpnl

Please contact support team via facebook

https://facebook.com/quadlayers

Already did at the same time I posted the issues here. Nobody has seen the message there yet…

Great, they will answer soon

@jpnl can you please test update 4.0.2? make sure you clean your browser cache

@quadlayers ok, I could delete now and add it again. Connecting to the customer account happened because I was logged in there.

Still issues though

• Button to connect to a business account is still disabled
• After connecting to a personal account, the date in the account list is set to 01-01-1970 – 12:01
• Feed works for @feeds but it gives an error for #feeds because I can’t connect to a business account:

SyntaxError: Unexpected token ‘<‘, “<!DOCTYPE “… is not valid JSON
Error: 403: The account must be business to show a hashtag feed.

Business accounts are only allowed for premium users. Make sure you have the latest premium version installed. Its 4.0.0