Open rgg-egunnery opened 4 weeks ago
Any news on this one?
same
same
same
same here
same here
any updates?
same,and I had to drop the version to 16.3.1
any updates?
same,and I had to drop the version to 16.3.1
Don't we need version 17.0.0 to conform to Apple's Privacy Policy, since version 17.0.0 has the Policy Privacy File?
+1
Just confirming that this is also the case on 17.0.1
same,and I had to drop the version to 16.3.1
Don't we need version 17.0.0 to conform to Apple's Privacy Policy, since version 17.0.0 has the Policy Privacy File?
+1
same,and I had to drop the version to 16.3.1
Did your build pass through Apple's Privacy Policy check?
same!, and
Just confirming that this is also the case on 17.0.1
yes, same on 17.0.1
Our company have more than 10 FB Application, after migrating to iOS FBSDK 17.0.0.
We found that when using one of the Facebook AppID and ClientToken, the following method always return result with isCancelled = true
.
- (void)logInFromViewController:(UIViewController * _Nullable)viewController
configuration:(FBSDKLoginConfiguration * _Nullable)configuration
completion:(FBSDKLoginManagerLoginResultBlock _Nonnull)completion;
What makes our team confused is that:
Not sure it is a bug in the Facebook Login SDK or any potential misconfiguration on the Facebook Developer console
FBSDKLoginManager *login = [[FBSDKLoginManager alloc] init];
FBSDKLoginConfiguration *configuration = [[FBSDKLoginConfiguration alloc]
initWithPermissions:@[@"public_profile", @"email"]
tracking:FBSDKLoginTrackingLimited];
[login logInFromViewController:[UITool getCurrentVC]
configuration:configuration
completion:^(FBSDKLoginManagerLoginResult * _Nullable result, NSError * _Nullable error) {
if (error) {
// error
} else if (result.isCancelled) {
//
// this is the code always goes to under one
// of the specific fb app configuration
//
} else {
// success, which should be expected
}
callback(responseDic);
}];
Update:
same,and I had to drop the version to 16.3.1
Did your build pass through Apple's Privacy Policy check?
passed
same,and I had to drop the version to 16.3.1
Don't we need version 17.0.0 to conform to Apple's Privacy Policy, since version 17.0.0 has the Policy Privacy File?
16.3.1 build passed through Apple's check for me
We had a call with Facebook last Thursday to discuss this and I've sent them the logs I collected for success vs failure for test and public accounts. They had no solution to offer on the call for this, but I will update this thread if I hear anything further.
their latest suggestion is: "you need to submit for review"
if that is the real problem there must be a bug on their review app flow
I tested with many fb app and i see: with fb app go live, if fb sdk ios version on "App Settings/Advanced/Check your SDK version":
I hope it can help fb developer team detect this issue.
I tested with many fb app and i see: with fb app go live, if fb sdk ios version on "App Settings/Advanced/Check your SDK version":
- fb sdk version 15.x or later => its worked
- fb sdk version under 15.x => always return cancel
I hope it can help fb developer team detect this issue.
In my FB App Setting, it display like that. What's wrong?
I tested with many fb app and i see: with fb app go live, if fb sdk ios version on "App Settings/Advanced/Check your SDK version":
- fb sdk version 15.x or later => its worked
- fb sdk version under 15.x => always return cancel
I hope it can help fb developer team detect this issue.
In my FB App Setting, it display like that. What's wrong?
It's a know problem on their side, they don't keep track of the latest release, and that piece of UI tands to bring even more confusion 🤦
We have iOS v15.0.0 and it's not working
same in V17.0.1
same happens to us in unity sdk as well
We have iOS v15.0.0 and it's not working
I tested and it's working on fb sdk v15.1.0 (>10 fb app id)
I tested with many fb app and i see: with fb app go live, if fb sdk ios version on "App Settings/Advanced/Check your SDK version":
- fb sdk version 15.x or later => its worked
- fb sdk version under 15.x => always return cancel
I hope it can help fb developer team detect this issue.
In my FB App Setting, it display like that. What's wrong?
It's a know problem on their side, they don't keep track of the latest release, and that piece of UI tands to bring even more confusion 🤦
I submited my app with a fb app id not worked, i'm waitting for fb console update SDK version to fb sdk v17.0.1. I hope it will work for this fb app id. Anybody try this case?
I have two app,they have same sdk version but only one worked ,one not。 @BunLV and my sdk version is V17.0.1
Hi all. We received an email from Facebook a few minutes ago saying that this issue has been fixed. Without any changes on our end, it seems that we can now login with public accounts. You might want to give yours a try. I am curious if this needs to be fixed on an account basis or if this was a general bug fix in the backend.
Hi all. We received an email from Facebook a few minutes ago saying that this issue has been fixed. Without any changes on our end, it seems that we can now login with public accounts. You might want to give yours a try. I am curious if this needs to be fixed on an account basis or if this was a general bug fix in the backend.
We just have tried but it's still not working.
Hi all. We received an email from Facebook a few minutes ago saying that this issue has been fixed. Without any changes on our end, it seems that we can now login with public accounts. You might want to give yours a try. I am curious if this needs to be fixed on an account basis or if this was a general bug fix in the backend.
I tested on all our fb app and it's still not working :( (account test & account normal)
Update: I jumped the gun. We have two apps, the first was working and the second was not. We contacted them again and now the second is working. It appears this needs to be fixed on a per app basis, presumably just some configuration on their end.
Updated: I tested and it's not working only iOS 17.x, below 17.x it worked
Checklist before submitting a bug report
Xcode version
15.3
Facebook iOS SDK version
17.0.0
Dependency Manager
SPM
SDK Framework
Login
Goals
Login for all users
Expected results
I expect both test users and regular users to be handled correctly when the app is live.
Actual results
I keep getting a cancellation returned when trying to use the new login method for limited login, only for non test users.
Steps to reproduce
No response
Code samples & details