Codename One项目Facebook登录无法调出表单，疑平台配置有新要求

I’ve run into similar headaches with Facebook’s ever-changing developer platform requirements, so let’s break down the likely configuration gaps and updated setup steps you need to follow:

1. Verify Basic App Status & Core Settings #

• Switch your app to "Live" mode: If your Facebook app is still in "Development" mode, only registered test users can access the login flow. Regular users will hit the "Not connected" error you’re seeing. Head to your app dashboard, go to App Settings > Basic, and toggle the app status to Live (you’ll need to fill mandatory fields like Privacy Policy URL first).
• Match platform identifiers exactly: Ensure your Android Package Name and iOS Bundle ID in Facebook’s platform settings are identical to what’s in your Codename One project (check codenameone_settings.properties for android.packageName and ios.bundleID—case sensitivity matters!).
• Don’t skip required fields: Facebook now enforces valid Privacy Policy URL, Terms of Service URL, and App Domains (if applicable) before you can go Live. These are non-negotiable for the login flow to work.

2. Update Facebook Login Product Configuration #

Facebook’s Login product has stricter rules now—double-check these critical points:

• Enable target platforms: In Facebook Developer Dashboard, go to Products > Facebook Login > Settings, and turn on the platforms you’re building for (Android, iOS, Web). Each needs its own setup:
  • For Android: Add your app’s Key Hashes (generate these via Codename One’s IDE or codenameone settings command in your project folder—include both debug and release hashes).
  • For iOS: Confirm the Bundle ID matches your project, and toggle on Single Sign On.
• Add valid OAuth redirect URIs: Codename One’s Facebook integration relies on a specific callback URL. Add this to the Valid OAuth Redirect URIs list under Facebook Login settings (it follows Codename One’s standard OAuth callback pattern). Without this, the login flow can’t complete, triggering the error you’re facing.

3. Validate Codename One Project Setup #

• Check your app ID: Make sure the facebook.appId property in codenameone_settings.properties is correct—no extra spaces or typos.
• Run login on the UI thread: Ensure you’re calling FacebookConnect.getInstance().login() from Codename One’s Event Dispatch Thread (EDT). Calling it off-thread can cause the login form to fail to load.
• Request explicit permissions: When initiating login, explicitly ask for needed permissions like public_profile or email (e.g., FacebookConnect.getInstance().login(new String[]{"public_profile", "email"})). Facebook now requires explicit permission requests, and missing these can break the flow.

4. Test with the Right User Accounts #

• If your app is still in Development mode, only use test users (registered in your Facebook app dashboard under Roles > Test Users). Regular accounts won’t see the login form in dev mode.
• Once Live, test with a regular Facebook account to confirm the flow works for all users.

If you’ve gone through all these steps and still see the error, check your app’s Error Logs in Facebook Developer Dashboard—they often show specific issues like invalid redirect URIs or missing permissions that are breaking the login attempt.

内容的提问来源于stack exchange，提问作者Quasar Wess