facebook.GraphResponse(30948): {HttpStatus: 400, errorCode: 100, subErrorCode: 33, errorType: GraphMethodException, errorMessage: Unsupported get request. Object with ID '111111111...' does not exist, cannot be loaded due to missing permissions

[Zelfapp]

Describe the bug
On Android, app starts up and there are 2 issues I've detailed here in the logs and I cannot sign in to Facebook. As you can see in the screenshot when I attempt to sign in with a test user (my FB app is still in development mode) I get the error in the screenshot.

Issue 1: Starting with v13 of the SDK, a client token must be embedded in your client code before making Graph API calls. Visit https://developers.facebook.com/docs/android/getting-started#client-token to learn how to implement this change.

The android installation docs do not mention a facebook_client_token. Once I did the following Issue 1 disappeared. However, Issue 2 still exists and I cannot Sign in with facebook.

Here you can see this is now required in strings.xml.

<string name="facebook_app_id">Facebook App ID</string>
<string name="facebook_client_token">Facebook Client ID</string>

And in AndroidManifest.xml

<application android:label="@string/app_name" ...>
    ...
    <meta-data android:name="com.facebook.sdk.ApplicationId" android:value="@string/facebook_app_id"/>
    <meta-data android:name="com.facebook.sdk.ClientToken" android:value="@string/facebook_client_token"/>
    ...
</application>

Issue 2: E/com.facebook.GraphResponse(31224): {HttpStatus: 400, errorCode: 100, subErrorCode: 33, errorType: GraphMethodException, errorMessage: Unsupported get request. Object with ID '111111111...' does not exist, cannot be loaded due to missing permissions, or does not support this operation.

I'm not sure how to overcome Issue 2 and I don't see anything docs regarding graph api permissions configurations?

Environment
flutter_facebook_auth: ^3.5.6

flutter doctor -v

[✓] Flutter (Channel stable, 2.5.3, on Manjaro Linux 5.4.150-1-MANJARO, locale
    en_US.UTF-8)
    • Flutter version 2.5.3 at /opt/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (4 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version
    31.0.0-rc2)
    • Android SDK at /home/nate/Android/Sdk
    • Platform android-31, build-tools 31.0.0-rc2
    • ANDROID_HOME = /opt/android-sdk
    • ANDROID_SDK_ROOT = /home/nate/Android/Sdk
    • Java binary at: /opt/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/google-chrome-stable

[✓] Android Studio (version 2020.3)
    • Android Studio at /opt/android-studio
    • Flutter plugin version 62.0.1
    • Dart plugin version 203.8452
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] Connected device (2 available)
    • sdk gphone x86 64 arm64 (mobile) • emulator-5554 • android-x64    •
      Android 11 (API 30) (emulator)
    • Chrome (web)                     • chrome        • web-javascript • Google
      Chrome 95.0.4638.69

• No issues found!

To Reproduce
Using with firebase auth.

Android docs maybe need to be updated? Or, have I made a configuration issue in regards to Issue 2? Why is FB trying to auth a user when the app is loading and the user is signed out? I guess that is why there is an error in startup?

Expected behavior
No errors in logs and to be able to login using facebook while my FB app is still in development mode.

[Zelfapp]

I am able to sign in now after doing the following, however, Issue 2 in the logs regarding missing permissions for graphi api still exists, when I start up the app and the user is not signed in.

[danielgomezrico]

@darwin-morocho why did you close the issue? is this solved?

[darwin-morocho]

@darwin-morocho why did you close the issue? is this solved?

Hi this is not an issue of this plugin for that reason I have closed it