Kepler adId retriver

I am trying to retrieve kepler device adid, I am followed the respective document → AdIdRetriever

When I add the dependency

@amzn/kepler-adid-retriever”: “^1.0.4”,

and Manifest.toml changes

[wants]
[[wants.service]]
id = “com.amazon.admanager.service.main”

and try to build kepler app it’s giving me below error

2025-09-23 14:52:04.873 [warning] npm error code E401

npm error Incorrect or missing password.

2025-09-23 14:52:04.873 [warning] npm error If you were trying to login, change your password, create an

npm error authentication token or enable two-factor authentication then

npm error that means you likely typed your password in incorrectly.

npm error Please try again, or recover your password at:

npm error https://www.npmjs.com/forgot

npm error

npm error If you were doing some other operation then your saved credentials are

npm error probably out of date. To correct this please try logging in again with:

npm error npm login

Note: I do have other dependency from @amzn registry.

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

Hi @Ivy_Mahajan

Yes, the mentioned configuration is set in .npmrc file

Screenshot 2025-09-24 at 11.09.42 AM

Hi @manoj_d_b,

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.

Hi @amen

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.

Hi @Ivy_Mahajan

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”.

Hi @manoj_d_b,

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

Hi @Ivy_Mahajan

sorry for the delayed response, I am able to import the following dependency!!

The issue was token path access from .env

Thank you

Hi @manoj_d_b
Thank you for letting us know ! If you require any further assistance, please reach out to us.
Warm regards,
Ivy

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.