Urgent] Gemini API - Persistent "API_KEY_ANDROID_APP_BLOCKED" despite correct and verified configuration

Google AI Studio
1 
    Hello Google Cloud Community,

    We are experiencing a persistent and critical issue with the Generative Language API. All our requests from our Android application are being blocked with a `PERMISSION_DENIED` error, and we have exhausted all possible client-side and configuration troubleshooting steps.

    **The Core Problem:**
    Every API call results in the following error, indicating our app's identity is not being recognized:

    {
      "error": {
        "code": 403,
        "message": "Requests from this Android client application <empty> are blocked.",
        "status": "PERMISSION_DENIED",
        "details": [
          {
            "@type": "type.googleapis.com/google.rpc.ErrorInfo",
            "reason": "API_KEY_ANDROID_APP_BLOCKED",
            "metadata": {
              "consumer": "projects/459920726362",
              "androidPackage": "<empty>"
            }
          }
        ]
      }
    }

    **Exhaustive Troubleshooting Performed:**
    We have systematically diagnosed this issue and can confirm:
    1.  **Project & Billing:** We created a brand new, clean project (`sahby`, consumer `projects/459920726362`) with an active and linked billing account.
    2.  **API Enabled:** The "Generative Language API" is enabled for this new project.
    3.  **API Key Verification:** The error occurs even when the key is correctly restricted to our Android app with the correct package name (`com.freegesh.help`) and a verified SHA-1 fingerprint obtained directly from `./gradlew signingReport`.
    4.  **SDK vs. Raw Request:** The error persists when bypassing the official SDK and making a direct, raw HTTPS request.
    5.  **Network Test:** We have tested on different network connections to rule out local network issues.

    **Conclusion:**
    The evidence overwhelmingly suggests this is a server-side or account-level issue where our Android application's identity is not being recognized (`<empty>`), leading to an incorrect block.

    Could anyone from the community or the Google Cloud team provide insight into this unusual behavior? We are completely blocked.

    Thank you.
3

Hi @Ya_Ssi
403 errors can be of your API key doesn’t have the required permissions. Have you checked that your API key is correctly set and possesses the necessary permissions? Also, ensure you have completed the proper authentication required to utilize models.