I am facing a strange bug, which I can repeat with FBCNact iPhone SDK to a great extent, Especially with class FBprimation dialog. The result is that instead of seeing the standard Extended Permissions dialog, the user is shown it:
The only way around it is to delete the user from the app and restore it.
In the same way I have repeated it:
- On the first login, the user is asked for extended permission on some (dialog is displayed correctly). User denies user permission, leaves the app.
- The user relies on the app again and whenever we need permission, we ask again. Instead of the permission dialog, the user is the "Welcome" Facebook "page.
The only way for the user to ask is to delete and restore the app. Has anyone else experienced this also? Is there any work around? I think the code asking for permission is here, I believe that this is very standard.
< Code> // create a permission dialog FBPermissionDialog * dialog = [[[FBprocity dialog] alloc] init] Autorelease]; Dialog.delegate = self; Dialog.permission = @ "read_stream"; [Dialogue show];
I have to face the same problem. In fact, you do not need to uninstall and reinstall the application. Based on this, a FBSession logout will run, there is a solution.
< P> Whenever one of those cases happens:- User "Canceled" FBPermissionDialog
- When FBPermissionDialog is displayed, publishing on the wall fails Because "the user has not authorized the app to perform this action"
-> Force logout using FBSession's "logout" methods.
The user has to re-enter his email and password the next time a Facebook request is made.
I must say that I am not really happy with it, but at least, it prevents the appearance of ugly popups. I'm still waiting for a better solution or even fixing on the FBCNact or Facebook server side.
Comments
Post a Comment