Xee Docs
Test & release

Android troubleshooting

View as Markdown

What to do when something on Android does not work. Set Xee.logLevel = XeeLogLevel.VERBOSE while you look: log lines say what the SDK did and why, under the tag Xee.

What you seeWhyWhat to do
Success with verified falseXee could not check the purchaseCheck App settings, Android: the package name and key must be set, and the service account needs the permissions in Set up Google Play. New permissions can take up to a day
The customer is refunded after three daysThe purchase was never acknowledgedSame as above. Check that Manage orders and subscriptions is on
No products on the paywallThey have no Google ID, or Google does not offer themAdd the IDs on each product's page, activate the product in Play Console, and install from a testing track. The log names each one
BILLING_UNAVAILABLEThe device has no usable Play StoreUse a device or emulator image with the Play Store, signed in
Last notification stays at None yetThe push does not reach XeeCheck the Push URL, that authentication is on, that the audience is Xee's, and that Google's account can publish to the topic
Access does not end after a refundThe notification did not arriveXee also checks for refunds once a day, so it ends within a day. Connect notifications for it to happen at once
Revenue is missing but access worksXee cannot read the orderCheck View financial data on the service account
A new test has no Android numbersThe paywall's products have no Google ID, or no view was loggedSee the warning on the paywall's page, and call logShowPaywallVariant
Xee.track sends nothingThe name or keys are not snake_case, or the person opted outThe log says which
Access bought on iOS does not show on AndroidTwo different profilesCall identify with the same customer ID on both