Forum Discussion
Solved
BillingResponseCode is always DEVELOPER_ERROR after calling startConnection on BillingClient
I have this issue when integrating Meta Horizon Billing Compatibility SDK into my 2D android app. The returned BillingResponseCode is always DEVELOPER_ERROR after the BillingClient initialization and calling startConnection on the initializatied BillingClient. Anyone who give me a hint would be appreciated.
Hi,
As soon as you add the app id when initiliazing the billing client, it will work.
BillingClient.newBuilder(this).setAppId(MY_OCULUS_APP_ID).setListener(purchasesUpdatedListener).enablePendingPurchases().build();Regards
3 Replies
Replies have been turned off for this discussion
Hi,
As soon as you add the app id when initiliazing the billing client, it will work.
BillingClient.newBuilder(this).setAppId(MY_OCULUS_APP_ID).setListener(purchasesUpdatedListener).enablePendingPurchases().build();Regards
BillingResponseCode.DEVELOPER_ERROR usually means there's a misconfiguration. Common causes:
- App not installed via the Play Store (must be from internal testing or higher).
- BillingClient not properly initialized (don’t forget enablePendingPurchases()).
- Using an invalid product ID or missing product in Play Console.
- Not using a real Google account with Play Store access.
- Trying to test purchases on an unpublished app.
Hello! Our team is looking into this but they've asked me to relay a few questions:
-
Are you initializing the BillingClient with a null app id? Can you try passing in their app id in the arguments of BillingClient.startConnection()?
-
Is it possible you're calling startConnection() more than once?
-
Can you check your Android logs and share any relevant error logs? Do you see any logs about the application id you're using to initialize? It's possible that it's not being read correctly from the manifest.
-
