Hi @manoj_d_b
Can you please verify if the contents of ~/.npmrc for (Step:3) Set up Amazon repository access in this document matches what you used for your setup ?
Warm regards,
Ivy
This could be a token expiration issue. The Kepler token has a validity period of 90 days, after which a new token is automatically generated (see this page). Kindly verify that your token hasn’t expired using the Kepler Token Details page. Please let us know if you still face issues after.
I believe with respect to latest kepler version 0.20.3719 we no longer need this token, it’s replaced with ~./npmrc file configuration with generic token. Correct me if I am wrong!!
Hi @manoj_d_b
The Authorization Token is still unique, it’s not generic. It’s part of ~/.npmrc content. You can follow this document to verify if the contents of your setup and the contents of ~/.npmrc matches.
Yes my Token matches with the document u shared, it’s working for other @amzn dependencies I am facing above issue with following dependency only “@amzn/kepler-adid-retriever”: “^1.0.4”.
I tried to replicate this but successfully built the project without encountering the issue you reported.
Although, Kepler SDK v0.20.x supports @amzn/kepler-adid-retriever API v1.0.12, both of us used "@amzn/kepler-adid-retriever": "^1.0.4" in package.json.
The system automatically used v1.0.12, ruling out API version as the cause.
To investigate further, could you please share your complete build logs?
In the meantime I’ll also try to arrange a troubleshooting session for you with your Amazon Contact.
Warm regards,
Ivy