-
Notifications
You must be signed in to change notification settings - Fork 257
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
With Apple ATT refused by user, Facebook classic login fallback in a limited login and returns a non valid authentication token #721
Comments
I have the same issue and i think facebook couldn't fix this issue, and i can't fixed this. Facebook is regret. @Jaeger87 if you find a solution please let me know. |
Currently facing the same issue, and it was not happening before we upgraded to 17.0.2. |
I found a solution. Actually it's the only solution i found. You have to downgrade the facebook sdk version. I chose 16.0.2 and it worked. After downgrading the version, sdk works properly and had no problem so far. |
But I assume that you would have difficulties submitting any build through the app store without the privacy manifest required by Apple (and added in 17.0.0), unless you're adding this yourself (In that case, that could be a solution). I found that in case of ATT begin opt out, we need to use the Limited Login. I wasn't able to test it to confirm it works. Maybe someone can confirm this 😄 |
I added my privacy policy by myself via my own website. In 17.0.0 version, facebook login redirecting to the limited.facebook domain. Now its working correctly and app is now on the store (iOS and android) |
Can you please tell me what your login method looks like now? Is it still through FB.LogInWithReadPermissions or now through FB.Mobile.LoginWithTrackingPreference? |
My login methot is this: public void LoginFacebook() |
Thank you!) |
All i did was downgrading the version of the facebook sdk to 16. |
We are struggling the same issue. And downgrading to 16.0.2 is not an option. Any other suggestions? |
Problems still persist, they seem to have abandoned the SDK completely. This is a direct result of a large number of employees being laid off. |
@Jaeger87 |
Hello, we changed old login route to limit login route and it worked fine. Be aware that backend validation has also been changed. |
How do you switch between them? How does your code runs when user logged in with limited and then allowing tracking? Or the opposite way |
We are switching between them on different platforms: using old login on android and new on ios. Here is the code for ios part:
|
Checklist
Environment
Describe your dev environment here, giving as many details as possible. If you have them, make sure to include:
2022.3.20
17.0.2
[iOS]
version17.4.1
Goals
To know if a user is authenticated with classic or limited login.
Expected Results
If facebook classic login fallback to limit login, I expect access_token to be null and not populated with a no valid access_token
Actual Results
When the sdk fallback to limited login, access_token is populated with a non valid token.
Steps to Reproduce
Refuse or not accept ATT, then login with FB.LogInWithReadPermissions(permissions, resultHandler)
The text was updated successfully, but these errors were encountered: