Invalid Scopes: publish_actions.

That message is correct. The permission publish_actions has been removed and should not be requested by JFBConnect at all if you're using a current release (which it seems like both of you are).

Can you please go to the Scope Review section in the Admin area and see if that properly shows you what feature in JFBConnect is requesting 'publish_actions'? That will help us narrow down what's wrong. It could be any of:
1) An outdated Social Profile plugin requesting it
2) A channel setup incorrectly
3) A custom permission request from another extension or manually entered in the Configuration -> Facebook area of JFBConnect

It's possible #2 above is the cause if you had a channel setup before upgrading to 8.0, then deleted the channel after the upgrade. I'm just thinking through this now as a possibility, but if that is the case, then a permission request for your user may still be present from the earlier JFBConnect version. We'd have to investigate further.

Let me know if any of the above helps narrow things down and we'll help you figure out how to resolve it.

The good news is that the message above will only show to your developers, not users, and everyone should still be able to login normally. This shouldn't cause any functional issues, but we definitely want to get to the bottom of it.

Thanks,
Alex

We've looked into the code a little bit further and do see where the publish_actions permission from an earlier installation may not have been properly removed and replaced with the newer permissions Facebook requires. With that said though, it should be as simple going into the Channel and clicking the 'Save' button. That should update the permissions that are being requested of the owner of the Channel.

James - You're case is odd though. If you deleted the Channel, then your user should not be getting that permission request. Please let us know what the Scope Review area shows. If the publish_action permission isn't in there, it means something funky is going on with the Channel you deleted. We'll have to investigate further to understand though.

Thanks,
Alex

We're investigating the problem. It definitely is related to channels that were created before JFBConnect v8.x that weren't updated properly with the update. To be clear, that's JFBConnect's issue, not something you may have done during wrong during the installation.

We are working on an updated release which will automatically fix these permissions. That may take a few days to implement, validate and test. The safe and quick way to fix this now is:
* Delete any Facebook Channels you have setup
* Go to the JFBConnect -> Usermap area
* Find your Facebook user
* Delete that user - This will only delete the link between your Facebook user and Joomla user. It will not effect your Joomla account
* Re-authenticate on the front-end with Facebook.
** Do this while already logged into Joomla or,
** If your Facebook and Joomla email addresses are the same, the accounts should be automatically linked
* Re-configure your Facebook Channel

The above will clear the permissions that are set on your Facebook user for logging in and should get things back to normal. We apologize for the trouble but hopefully this will get you going now instead of waiting for the update.

Thanks,
Alex

We've been doing further investigation into this. Our code seems to be handling things properly in most cases. We're still unsure where things get out of sync. Simply saving (or deleting and recreating) the channel should work to remove the erroneous publish_actions permission. We are working on an update that will auto-upgrade permissions if they are old, but I don't think that would fix the cases above because they are out of sync some other way that we'd like be able to automatically detect.

Have you tried the steps above for deleting channel and the user-mapping in JFBConnect and then recreating the channel? Again, deleting the user-mapping will not delete the Joomla user. You'll just need to re-authenticate with Facebook again and it should automatically recreate that mapping to your existing Joomla user (if the emails match or you use the Reconnect feature in the SCLogin module while you're already logged into Joomla). That new user-mapping will have a clean slate of permissions and shouldn't have the publish_actions problem.

Then, when you create the new channel, it will request only the correct permissions based on the JFBConnect v8.0 update.

Please let me know if somehow deleting the usermapping and recreating it still has the issue, because that would indicate there's something unrelated to channels or the specific user that is causing the problem. That would help us investigate further because, as I mentioned, we can't fully understand how that permission is still being requested if you deleted or re-saved the channel.

Thanks,
Alex