Hi everyone,
I’m experiencing a critical issue with the IAPHUB Start component in my Adalo app.
The setup works correctly on iOS. Users can create an account, log in, complete onboarding, and the IAPHUB Start component initializes properly. The paywall/subscription flow works as expected on iPhone.
However, on Android, the same flow does not work.
What happens on Android
Users can:
- Download the production app from Google Play
- Create an account
- Log in
- Complete onboarding
But when the app reaches the IAPHUB Start component, it triggers the Start Failed action and never reaches the paywall/subscription screen.
So the issue seems specifically related to the IAPHUB Start component on Android.
Important details
- Platform: Adalo native app
- Subscription provider: IAPHUB
- iOS: working correctly
- Android: Start component fails
- App is live/production, not only test build
- Same logic and same Adalo flow are used on both platforms
- The issue happens before the user reaches the paywall
- The Android app was downloaded through the official Google Play route
What I already checked
- The iOS version works with the same IAPHUB setup
- The user account creation/login flow works on Android
- The onboarding flow works on Android
- The failure happens exactly when reaching the IAPHUB Start component
- The Start Failed action is triggered on Android
Expected behavior
The IAPHUB Start component should initialize successfully on Android, just like it does on iOS, and then continue to the paywall/subscription screen.
Actual behavior
On Android, the Start component fails and blocks the subscription flow completely.
Has anyone else experienced this issue with the IAPHUB Start component working on iOS but failing on Android?
Could this be related to the Android build, Google Play Billing, the IAPHUB Adalo component version, or something specific in the Android configuration?
Any help or guidance would be greatly appreciated, because this is currently blocking Android subscriptions in production.
Thanks!