Facebook Login using SDK 17.0.0 always displays a limited login warning

[Sireikis]

Checklist before submitting a bug report

• I've updated to the latest released version of the SDK
• I've searched for existing GitHub issues
• I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group
• I've read the Code of Conduct
• This issue is not security related and can safely be disclosed publicly on GitHub

Xcode version

15.3

Facebook iOS SDK version

17.0.0

Dependency Manager

SPM

SDK Framework

Login

Goals

I want to continue using the classic login method that provides an access token for GraphAPI requests and not see a red limited login warning as part of the user login flow.

Expected results

The user does not see a red limited login warning as part of the user login flow and the token we receive from the facebook login request allows us to make Graph API requests.

Actual results

The user sees a red limited login warning as part of the user login flow and the access token we receive from the facebook login request does not allow us to make Graph API requests on our backend.

I'm very confused as to what is causing the red warning to appear. I've uploaded to Testflight in an attempt to see if environment mattered, but it was present on our production pre release build as well.

Steps to reproduce

Updated to Facebook SDK 17.0.0 from 15.1.0. The red warning appeared immediately, regardless of which login method I attempted to use (classic, limited, limited with tracking enabled) and the token returned was invalid.

Code samples & details

I also get the same error as in this task #2365. I don't see anyone mention the red warning however.

[fgeracitano]

Hi @Sireikis, for us the login warning appears for test users (those added via the Facebook Developer Console).
However, when we use profiles that are not designated as test users, we don't see the warning but are unable to proceed. #2387

[Sireikis]

Hello @fgeracitano, looks like that's what was causing the red warning, thanks for that tip! Since my other issue is a duplicate of existing issues I'll close this issue.