IAPHUB Start fails on production build (certified international device) - Unsupported billing API version 23

Get Help
1

Issue Description:

I’m experiencing a critical issue where the IAPHUB Start component consistently fails to initialize in my production build. The behavior is: spinning for ~10 seconds, then triggering the fail action (my error page).

Environment:

  • App ID: 69f44835809552d8e8b70dc8

  • Adalo Plan: Starter

  • Build Type: Production AAB, signed and uploaded to Google Play Closed Track

  • Test Device: Google Play certified international version (full GMS, not a China ROM)

  • Android Version: 14

What I’ve Tried (Complete List):

  • :white_check_mark: I have multiple-checked every configuration step following the IAPHUB official guide (Google Cloud service account, API keys, Product ID, Bundle ID, etc.).

  • :white_check_mark: I have granted the service account View financial data and Manage orders and subscriptions permissions in Google Play Console.

  • :white_check_mark: The subscription product (monthly_sub_4usd) and its base plan are Active.

  • :white_check_mark: I have switched IAPHUB Dashboard to Production data.

  • :white_check_mark: I have tested on a certified international version Android device (Play Protect certified, full GMS). The issue persists, ruling out the China-ROM incompatibility theory.

  • :white_check_mark: I have captured a full logcat during the failure. The only relevant error I can find is:

    text

    W/Finsky: Unsupported billing API version: 23

Question:

  1. Has anyone successfully resolved this Unsupported billing API version: 23 error with IAPHUB?

  2. Could this be an issue with the IAPHUB SDK itself?

  3. As a fallback, has anyone successfully migrated to Adalo’s native IAP Beta component for subscriptions? Is it reliable for production?

I have already contacted IAPHUB support but haven’t received a solution yet. Any advice or workaround would be greatly appreciated.

Thank you.

2

Hi @phc,

Welcome to the community! :tada:

This issue has been reported already on Monday and the team is aware of this issue currently which are working on a fix, I’ll keep you updated here with the progress!

Thank you and have a great day!

3

@phc, this issue should be fixed now! Could you push a new Android build and test the app out again? Thank you and have a great day!

4

Hi Dilon,

Thanks for the update.

I just pushed a new Android build and tested it again. Unfortunately, the issue is still the same: the IAPHUB Start component spins for about 10 seconds and then triggers my fallback error screen. No success.

To be sure, I did the following:

  1. Removed the app from my test device.

  2. Cleared Google Play Store cache.

  3. Reinstalled via the opt-in link.

The problem persists.

Is there any additional step I need to take on my end (e.g., re‑generating API keys, re‑saving the IAPHUB Start component)?

Let me know what else I can provide to help debug this.

Thanks for your support!

5

Thanks for the update @phc!

It did not worked for me on an app but now back to normal after the fix. (internal testing & production) This might be some setup issue, could you submit a support ticket? : New Bug Form

Thank you and have a great day!

6

Hi Dilon,

Thank you for the update and for looking into this.

I will submit a support ticket with all the details (app ID, logcat, device info, reproduction steps) so your team can investigate my specific setup.

Just to confirm – I have already tested the fix on a certified international device (full GMS, Android 14), but the issue remains. The logcat shows the same error:

W/Finsky: Unsupported billing API version: 23

I hope the support team can help resolve this.

Thanks again for your help.

Best,
Pak Ho