-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.1.0 - facebookConnectPlugin.login uses Limited Login and returns unusable accessToken #14
Comments
Update: the warning appears because I was loggin in with an administrator/test account, it doesn't appear for normal users. As for limited login, it appears it will redirect to limited.facebook.com automatically if you don't have ATTrackingManager |
@gabrielnicolae3103 any idea why the accessToken doesn't work or what it could be used for? How do you enable ATTrackingManager? |
I don't know why your accessToken is not working, you should check the facebook sdk page for it, there are multiple tokens (client token, app access token etc). There is also a tool where you can see all your tokens. As for enabling ATTrackingManager, you can read more about it here (I haven't tried it, I just let it work as limited.facebook.com) because I don't need extra informations. https://stackoverflow.com/questions/63587364/how-to-add-the-apptrackingtransparency-permission-to-your-ios-apps |
I have the same issue. AuthResponse token doesn't work from 4.1.1 downgrading to 4.0.4 it works fine. More specifically I can call the Graph API to get name and email, etc but I cannot login with the AuthResponse provided. |
@jasonandress that was exactly my same issue. I just stuck with 4.0.4. I am not sure if anything useful can be done with whatever that token is that is provided with 4.1.1 |
@gabrielnicolae3103 are you sure your accessToken even works? |
@codeconsole hi, have you resolved the issue with access token? Is there in this thread who uses 4.1.1 version and everything is ok? |
Just researched it and my backend version does not support Facebook Limited Login. It returns a different object than the original. I wonder if there is a setting with 4.1.1 to not user Facebook limited login and use the one that's exposed in 4.0.4. If not I'll stay with 4.0.4 |
@jasonandress @codeconsole @gabrielnicolae3103 @MaximBelov I have researched a lot for the last days and what I found:
So, here is the solution: This flow is not a bug, this is a normal flow, but not very clear and expected. |
4.04 works fine, but calling the following
goes to
limited.facebook.com
and results inbut the
accessToken
doesn't seem to be usable on the server side like it was in 4.0.4accessToken
change somehow from <= 4.0.4? Is it something different?facebookConnectPlugin.login()
even thoughfacebookConnectPlugin.loginWithLimitedTracking()
is not being used?The text was updated successfully, but these errors were encountered: