In-app purchase made on a different device is not recognized (skuDetails 400 error)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
I purchased an in-app product through the official Google Play Store on a separate Android device (with full Google Play Services), using the same Google account that is configured in microG on my primary device. The purchase was confirmed successfully by Google.
On the device running microG, the app does not recognize this purchase. It displays "No Products Found", and the underlying request fails with a 400 error.
To Reproduce
Configure a Google account in microG on a device without Google Play Services (e.g. Volla OS)
Install an app with in-app purchases via Aurora Store (in this case: Noteshelf 3 by Fluid Touch)
On a separate device with full Google Play Services, purchase the in-app product using the same Google account
Open the app on the microG device and try to access the purchased content, or trigger a "restore purchases" action
Expected behavior
The app should recognize the existing purchase associated with the Google account, regardless of which device the purchase was originally made on.
Actual behavior / error
Network request failed (POST https://play-fe.googleapis.com/fdfe/skuDetails) invalid: 400
Device information
Device: Volla Tablet, Volla OS 15.0 20260601-STABLE-mimir
microG version: 0.3.15.250932
Aurora Store version: v4.7.5 (71)
App: Noteshelf 3 (Fluid Touch), version v4.5.5 (558)
Additional context
This appears related to the discussion in #2495 — purchase/license recognition for in-app products that were not originally completed on the same device running microG. Happy to provide a logcat if that would help diagnose this further.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the POST https://play-fe.googleapis.com/fdfe/skuDetails request and the related discussion in #2495. Reproduce the cross-device purchase flow on the listed Volla OS and microG versions, collect the suggested logcat details, and compare the request failure with successful same-device recognition; done means the existing purchase is recognized without the 400 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100