Weird behavior with facebook test users (gets redirect to connect page after accepting permission)

[lmammino]

Hi,
I just tried connecting a Facebook test user. After giving permissions to the app i have been redirected to the connect page (hwi_oauth_connect route) instead of being redirect to the registration page.
That's really weird and happens only with facebook app test users (not with real ones).

Tell me if I can try something more to find out why the issue occurs.

You can find my whole codebase here: lmammino/just-had-a-cocktail

[stloyd]

Sorry to say, but according to my knowledge, those test users can't be easily used as users for OAuth testing, mainly because theirs sign-in urls are generated by facebook (for real ones it's generate by bundle with data from facebook), and it's one time use only, so those generated by bundle are leading to facebook OAuth error which blocks proper sign-in action.

[lmammino]

Really weird.
This makes test users meaningless for most of the apps.

Thanks for the clarification. I'll dig further on google for this issue and let you know if I found something useful.

[lmammino]

It seems that it should be possible: http://stackoverflow.com/questions/11431990/how-can-i-get-a-user-access-token-for-a-specific-facebook-test-user

And it seems that facebook team should be able to login with a test user to your app to approve your custom open graph actions and objects...

[lmammino]

Problem spotted!
The problems is due to an exception thrown by the getValueForPath method of the PathUserResponse class.
When a path cannot be mapped an AuthenticationException is raised.
So the whole login process is stopped and the user is redirect to the default login page.

When using facebook test users they don't have a nickname (the nickname key/value couple is not present into the user object returned into the OAuth response) so if I mapped the nickname property I am not able to connect with that user...

I think we should throw a different kind of exception here or find another way to map proprerties.
For example we might have optional and mandatory properties, when a mandatory option misses we may throw the exception, otherwise we can simply provide a NULL value for that property...

[stloyd]

Maybe additional "response" class for facebook test users ?

[lmammino]

I haven't tested it deeply, but I think the problem is not only for facebook test users. It seems to appear every time that a path response does not match a user property.
In case of the facebook test users the always does not have a nickname...

Anyway I'm not sure throwing an AuthenticationException is a good idea...

[asm89]

I think this is fixed by the username/id refactoring @stloyd did earlier.