Bug Description
1. Summary
Using the latest version of @amazon-devices/keplerscript-appstore-iap-lib@2.12.13 will cause all in-app purchase functions (such as getUserData, getProductData, and getPurchaseUpdates) to return a response code of FAILED.
Also, I can’t find @amazon-devices/package-manager-lib@1.0.0, likely because it’s private.
App Name: com.tatsuki.amazonpurchasingsample
App Link on Amazon Appstore (found through Developer Console → Actions column in App List → View on Amazon.com):
Bug Severity
Select one that applies
- Impacts operation of app
- Blocks current development
- Improvement suggestion
- Issue with documentation (If selected, please share the doc link and describe the issue)
- Other
2. Steps to Reproduce
- In the package.json file, add the @amazon-devices/keplerscript-appstore-iap-lib@2.12.13. @amazon-devices/package-manager-lib@1.0.0 was not found and therefore has not been added.
- Place AppstoreAuthenticationKey.pem in the assets/raw directory within the app’s root directory.
- Execute `kepler build —build-type Debug –build-number 1 —reset-cache` and create the vpkg(armv7).
- Submit the created vpkg(armv7) to LiveAppTesting.
- Upload your app to LiveAppTesting, then deliver it to the Fire TV Stick 4K Select via Amazon.co.jp under Your Account → Your Apps → Actions → Deliver to…
- Launch the app on your Fire TV Stick 4K Select and execute an in-app purchase.
3. Observed Behavior
Explain what actually happened, noting any discrepancies or malfunctions.
All in-app purchase functions (such as getUserData, getProductData, and getPurchaseUpdates) to return a response code of FAILED.
4. Expected Behavior
Describe what you expected the SDK to do under normal operation.
All in-app purchase functions (such as getUserData, getProductData, and getPurchaseUpdates) to return a response code of SUCCESS and return a value.
4.a Possible Root Cause & Temporary Workaround
Fill out anything you have tried. If you don’t know, N/A is acceptable
We will downgrade from @amazon-devices/keplerscript-appstore-iap-lib@2.12.13 to @amzn/keplerscript-appstore-iap-lib@2.12.10 without altering the public key, manifest.toml, or in-app purchase processing. We confirmed it returns a response code of SUCCESS along with the value.
In @amzn/keplerscript-appstore-iap-lib@2.12.10, there was a dependency on @amzn/package-manager-lib. However, in @amazon-devices/keplerscript-appstore-iap-lib@2.12.13, the dependency on @amzn/package-manager-lib had been removed.
This suggests that the cause is likely that @amazon-devices/package-manager-lib@1.0.0 is private and cannot be referenced as a dependency.
5. Logs or crash report
npm view @amazon-devices/keplerscript-appstore-iap-lib@2.12.13
@amazon-devices/keplerscript-appstore-iap-lib@2.12.13 | See license in LICENSE | deps: 5 | versions: 1
dist
.tarball: https://registry.npmjs.org/@amazon-devices/keplerscript-appstore-iap-lib/-/keplerscript-appstore-iap-lib-2.12.13.tgz
.shasum: 6d3308c81ff321d987209292f1651ca586c1cb4e
.integrity: sha512-O00hquk6y/oPxNVjd1NPZDMyZ1idiXb2nelFMjcZLfdnm4IrBCWZq/hovbQBzGy0gzsVe29ooMB8FTVp49fePQ==
.unpackedSize: 2.6 MB
dependencies:
@amazon-devices/keplerscript-turbomodule-api: ^1.0.0 react-native: 0.72.0
@amazon-devices/react-native-kepler: ^2.0.0 react: 18.2.0
react-native-uuid: ^2.0.1
maintainers:
- amazon-devices-admin <amazon-devices-npm-admin@amazon.com>
dist-tags:
latest: 2.12.13
published a month ago by amazon-devices-admin <amazon-devices-npm-admin@amazon.com>
$npm view @amazon-devices/package-manager-lib@1.0.0
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@amazon-devices%2fpackage-manager-lib - Not found
npm error 404
npm error 404 '@amazon-devices/package-manager-lib@1.0.0' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
6. Environment
Please fill out the fields related to your bug below:
-
SDK Version: 0.21.4686
-
App State:
Foreground -
OS Information
7. Example Code Snippet / Screenshots / Screengrabs
Include any relevant code or component setup in React Native that can help reproduce the bug.
import { ExampleComponent } from 'custom-sdk';
<ExampleComponent config={{ key: 'value' }} />
Additional Context
Any Additional Context you would like to provide?
Add any other relevant information, such as recent updates to the SDK, dependencies, or device OS that may affect the bug.
<!-- Answer here if applicable -->
