email permissions

JFBConnect will automatically request the email permission from the user, so you shouldn't need to set that at all.

As for the @unknown.com address, we're looking into the cause of this. The only time that should happen is if JFBConnect can't fetch the email address for the user from Facebook. That should never be the case, but it does happen depending on a couple of variables.

Can you let me know the following, which may help diagnose things further:
* Is it a specific user that gets the unknown address?
* Is it a lot or all users?
* Do you know if there's anything specific about the users with the unknown address that may be preventing their email from being fetched (such as stricter privacy settings or a specific location, etc)?

There's a few other options in-code that we can have you implement that will force the user to re-authenticate if their email address can't be found, but, again, that simply should be necessary.

Thanks,
Alex

Alessio,
We're still doing a lot of testing to see why an email may not be retrieved for a user. We've set every privacy setting in Facebook to the strictest level, but it always seems to come in. There is code in JFBConnect that checks for a missing email address from Facebook and replaces it with the @unknown.com address. That code should never be called as there's no reason that Facebook shouldn't return the email address.. especially when the rest of the information is fetched.

With that said, we are looking into it more. The 'email' setting you configured has no function. It can be removed or left, it really won't affect things either way. We'll likely change how our logic works in the future to completely deny the registration if an email can't be obtained, even if other profile information can.

Again, if you find any specific setting in Facebook that would be hiding the email address, let us know, but we don't know of any and there isn't any documentation in the API that that information can be hidden by the user.

Thanks,
Alex