# Problems to observe login\_status of AccountLogin

**URL:** <https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054>\
**Category:** Q&A\
**Created:** [September 1, 2026, 8:08am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054 "2026-09-01T08:08:04Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sergio\_Gomez](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sergio\_Gomez](https://community.amazondeveloper.com/u/Sergio_Gomez)\
**Post date:** [September 1, 2026, 8:08am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/1 "2026-09-01T08:08:04Z")

</div>

We are verifying the Account Login status our app reports to Fire TV. The signal is the  
`ContentAppEndpoint: ... partner_id=... login_status=` line emitted by `kcs-lib`, and we cannot capture it.

**Environment**

- Device: Fire TV Stick running Vega — product `callie`, `armv7l`, profile `tv`

- OS: `OS 1.2 (TV Ship/547)` — `OS_VERSION=1.2`, `RELEASE_ID=21`, `OE_VERSION=4.0.0`,  
`VERSION_NUMBER=2101020054720`

- `BUILD_VARIANT=user`, `BUILD_TAGS=release-keys`, `inDeveloperMode: true`

- Vega CLI `1.2.22`, SDK `0.22.6150`

- `kcp-cli-v2` `<VERSION>` (downloaded from the forum thread)

```auto
vda shell journalctl --follow --since now | grep -E 'ContentAppEndpoint.*<PARTNER_ID>.*login_status'

```

No output. Without the `grep`: `WARNING: journalctl is not supported in developer mode shell. Please use loggingctl instead.`

 ![image](https://d3mq594dkmpl37.cloudfront.net/original/2X/b/b8c6bd47ec7686f9cd51b1ffe41a91437b22114e.png)

This worked a few months ago during our initial Content Launcher and Account Login integration, though we were using `kcp-cli-v2` then rather than the log line. Retrying that route now gives the  
`No endpoint found` result above. We cannot tell whether something changed in the expected  
implementation that we are not aware of, or whether we are doing something wrong.

Questions:

1. What is the supported way to observe that line ?

2. Are application logs expected to be unavailable to the developer-mode shell on `BUILD_VARIANT=user`?

I can attach our `manifest.toml` or `service.js` if that helps rule out a configuration problem on our  
side.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Ivy](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/ivy/32/5637_2.png) [@Ivy](https://community.amazondeveloper.com/u/Ivy)\
**Post date:** [September 1, 2026, 12:32pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/4 "2026-09-01T12:32:29Z")

</div>

Hi @Sergio_Gomez,

Thanks for the detailed writeup and the attempts table.

On a **User build device with developer mode enabled** , Account Login status is observable via different workaround and which our team is looking to add to developer documentation in upcoming days (like through testing via inbuilt CLI). Can you please try below workaround and let us know if it works?

**Prerequisites:**

1. The app build must be a debug build. These are INFO-level logs and are suppressed on  
Release builds
2. The line to watch is **AccountLoginServer::updateStatus** (and journalctl isn’t supported in the developer-mode shell, loggingctl is the right logging tool)

**Test Steps:**

1. Start log monitoring in a separate terminal: Replace \<APP\_PACKAGE\_ID\> with your package name (e.g. com.partner.app).  
` vega exec vda shell loggingctl log -f -v <APP_PACKAGE_ID> | grep -E 'AccountLoginServer::updateStatus'`
2. Uninstall the app if already installed: `vega device uninstall-app --appName <APP_PACKAGE_ID>`
3. Install the debug variant: `vega device install-app --packagePath <path-to-debug.vpkg inside the device>`
4. Launch the app, you should see: `AccountLoginServer::updateStatus invoked. status: 1` ← represents signed in status as false
5. Log in → `AccountLoginServer::updateStatus invoked. status: 0` ← represents signed in status as true
6. Log out → `AccountLoginServer::updateStatus invoked. status: 1` ← represents signed in status as false

**Status values:**

- 1 = signed out ( signed in status is false)
- 0 = signed in ( signed in status is true)

**Pass Critieria:**

- **Pass** - status changes 1 → 0 on login, and 0 → 1 on logout.

**Troubleshooting:**

- No logs at all - the app is a Release build (INFO suppressed), or Account Login isn’t implemented.
- Status doesn’t change - Account Login is implemented but not updating state on login/logout events.
- These INFO-level logs only appear on debug app builds, regardless of OS variant. We’re also updating the public documentation to reflect this. Please give it a try and let us know how it goes.
- Rebuild the app with below commands if you see any errors like "_Cannot update status until a handler has been set"_ against your app on the full logs

```auto
  npm install @amazon-devices/kepler-media-account-login@1.1.22
  rm -rf node_modules package-lock.json && npm install
  npm ls @amazon-devices/kepler-media-account-login 

```

Warm Regards,  
Ivy

---

<div class="post-metadata">

**Author:** ![Sergio\_Gomez](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sergio\_Gomez](https://community.amazondeveloper.com/u/Sergio_Gomez)\
**Post date:** [September 2, 2026, 11:32am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/6 "2026-09-02T11:32:11Z")

</div>

_Hi @Ivy,_

_We ran the verification test on our current debug build using the command provided:_

```auto
vega exec vda shell loggingctl log -f -v com.orange.es.amzftv | grep -E 'AccountLoginServer::updateStatus'

```

### _ **Observed Sequence** _

_Each status transition is immediately accompanied by an **`ERROR`** log:_

- _ **Launch** (status: **`1`** ) → **`AccountLoginServer::updateStatus invoked. status: 1`** _
- _ **Login** (status: **`0`** ) → **`AccountLoginServer::updateStatus invoked. status: 0`** _
- _ **Logout** (status: **`1`** ) → **`AccountLoginServer::updateStatus invoked. status: 1`** _

_Each invocation triggers the following error:_

> _ **`ERROR ... AccountLoginServer::updateStatus failed to update status, error=KeplerScriptAccountLogin::updateStatus error in updating status`** _

### _ **Full Log Excerpt** _

```auto
Sep 02 11:23:04 ... INFO ... AccountLoginServer::updateStatus invoked. status: 1
Sep 02 11:23:04 ... ERROR ... AccountLoginServer::updateStatus failed to update status, error=KeplerScriptAccountLogin::updateStatus error in updating status
Sep 02 11:24:22 ... INFO ... AccountLoginServer::updateStatus invoked. status: 0
Sep 02 11:24:22 ... ERROR ... AccountLoginServer::updateStatus failed to update status, error=KeplerScriptAccountLogin::updateStatus error in updating status
Sep 02 11:24:50 ... INFO ... AccountLoginServer::updateStatus invoked. status: 1
Sep 02 11:24:50 ... ERROR ... AccountLoginServer::updateStatus failed to update status, error=KeplerScriptAccountLogin::updateString error in updating status

```

### _ **Questions** _

1. _Does this sequence match the expected pass criteria ( **`1 → 0`** on login, **`0 → 1`** on logout)?_
2. _Should we treat the **`failed to update status`** error as expected behavior on this build, or indicates an issue?_

_Thanks!_

---

<div class="post-metadata">

**Author:** ![Ivy](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/ivy/32/5637_2.png) [@Ivy](https://community.amazondeveloper.com/u/Ivy)\
**Post date:** [September 3, 2026, 4:31pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/7 "2026-09-03T16:31:52Z")

</div>

Hi @Sergio_Gomez

Answering the 2 questions you added here:

1. Does this sequence match the expected pass criteria ( **1 → 0** on login, **0 → 1** on logout)?\*  
A\> Yes, the sequence should look like this.
2. Should we treat the **failed to update status** error as expected behavior on this build, or indicates an issue?  
A\> Along with the above sequence, we should not see this error. If we see this error, above status will not bind correctly. In this case you should run below to fix this error:

```auto
npm install @amazon-devices/kepler-media-account-login@1.1.22
rm -rf node_modules package-lock.json && npm install
npm ls @amazon-devices/kepler-media-account-login

```

Warm regards,  
Ivy

---

<div class="post-metadata">

**Author:** ![Sergio\_Gomez](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sergio\_Gomez](https://community.amazondeveloper.com/u/Sergio_Gomez)\
**Post date:** [September 4, 2026, 2:10pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/8 "2026-09-04T14:10:29Z")

</div>

Hi @Ivy,

Thanks again for the guidance so far — following up with the results after applying the fix you suggested, plus a new detail I’d like to confirm with you.

**What we did**

Our `package.json` had `@amazon-devices/kepler-media-account-login` pinned to the range `^1.1.0`, which after a clean reinstall (`rm -rf node_modules package-lock.json && npm install`) resolved to `1.1.24` instead of `1.1.22`. We pinned it to the exact version you recommended:

```auto
npm install @amazon-devices/kepler-media-account-login@1.1.22
rm -rf node_modules package-lock.json && npm install
npm ls @amazon-devices/kepler-media-account-login

```

`npm ls` now confirms `1.1.22` is installed. We rebuilt the debug variant, uninstalled/reinstalled on the Fire TV device, and re-ran the verification.

**Result — the original error is gone**

Running the exact command from your instructions:

```auto
vega exec vda shell loggingctl log -f -v com.orange.es.amzftv | grep -E 'AccountLoginServer::updateStatus'

```

Before (version `1.1.24`), every transition looked like this:

```auto
Sep 02 11:23:04 ... INFO ... AccountLoginServer::updateStatus invoked. status: 1
Sep 02 11:23:04 ... ERROR ... AccountLoginServer::updateStatus failed to update status, error=KeplerScriptAccountLogin::updateStatus error in updating status

```

After pinning `1.1.22`, the `ERROR ... failed to update status` line no longer appears on launch, login, or logout.

**New detail we’d like you to confirm**

However, the log output itself looks different now, and we want to make sure we’re not missing something. With `1.1.22`, using both the exact grep from your instructions and a broader case-insensitive one (`grep -iE 'accountlogin|account\.login|account_login'`), we no longer see:

- The native line `AccountLoginServer::updateStatus invoked. status: X` (with the status value), or
- Any log at all from the `com.amazon.kepler.media.account.login` component (the one that previously logged the `error=...` line).

Instead, the only lines we see on every login/logout are:

```auto
Sep 04 14:06:02.116931 ... INFO KeplerScript.TurboModule: KeplerScriptAccountLogin::updateStatus invoked.
Sep 04 14:06:02.119363 ... INFO KeplerScript.TurboModule: KeplerScriptAccountLogin::updateStatus completed.

```

No status value, and no line from the `AccountLoginServer`/`account.login` native provider at all — just the TurboModule bridge `invoked`/`completed` pair.

**Questions**

1. Is this a known/expected change in logging format for `1.1.22` (i.e., the native provider-level `status: X` log line was replaced by the TurboModule `invoked`/`completed` pair in this version), or should we still expect to see the `AccountLoginServer::updateStatus invoked. status: X` line with the exact same format as before?
2. Given `completed.` appears with no error, can we treat this as equivalent confirmation that the status update succeeded and is bound correctly — even without the explicit `status: X` value in the log — or is there another way to verify the actual 1→0 / 0→1 transition on this version?

We don’t want to close this out as fully verified until we’re sure the log change is expected and not masking a different issue.

Thanks again for your help, Sergio

---

<div class="post-metadata">

**Author:** ![Ramachandran](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Ramachandran](https://community.amazondeveloper.com/u/Ramachandran)\
**Post date:** [September 4, 2026, 2:44pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/9 "2026-09-04T14:44:27Z")

</div>

Hi @Sergio_Gomez , to double check are you using the debug build of your app while checking the logs.

---

<div class="post-metadata">

**Author:** ![Ivy](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/ivy/32/5637_2.png) [@Ivy](https://community.amazondeveloper.com/u/Ivy)\
**Post date:** [September 10, 2026, 3:37am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/11 "2026-09-10T03:37:44Z")

</div>

Hey @Sergio_Gomez

Checking again.  
Are you using the debug build of your app while checking the logs?

Warm Regards,  
Ivy

---

<div class="post-metadata">

**Author:** ![Sergio\_Gomez](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sergio\_Gomez](https://community.amazondeveloper.com/u/Sergio_Gomez)\
**Post date:** [September 10, 2026, 9:39am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/12 "2026-09-10T09:39:08Z")

</div>

Hi @Ivy @Ramachandran  
I’m testing with the debug version. I also updated the SDK version—just in case—and updated the dependencies in the package.json (amzn → amazon-devices), but the command now returns nothing.

---

<div class="post-metadata">

**Author:** ![Ramachandran](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Ramachandran](https://community.amazondeveloper.com/u/Ramachandran)\
**Post date:** [September 10, 2026, 10:26am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/13 "2026-09-10T10:26:32Z")

</div>

Thanks @Sergio_Gomez - could you help us provide below items to investigate further.

1. Full logs ( capturing from : Debug vpkg install → sign-in → sign out → again sign-in )
2. OS version details
3. Manifest file if possible

---

<div class="post-metadata">

**Author:** ![Sergio\_Gomez](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sergio\_Gomez](https://community.amazondeveloper.com/u/Sergio_Gomez)\
**Post date:** [September 10, 2026, 11:03am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/14 "2026-09-10T11:03:19Z")

</div>

Hi , attaching what you asked for.

1. Full logs captured with logging started before the uninstall, then: uninstall → install debug vpkg → launch → sign in → sign out → sign in.

- vega exec vda shell loggingctl log -f -v com.orange.es.amzftv

1. Versions

- Device: firestick-61dc7f4262e3ee0e
- OS version: OS 1.2 (TV Ship/44)
- Vega SDK: 0.24.9914
- @amazon-devicesamazon-devices/kepler-media-account-login: 1.1.22
- Build: Debug, armv7. Package declares os\_versions [“1.2”], contract\_package\_version 1.0.323.0

1. Manifest

---

<div class="post-metadata">

**Author:** ![Ramachandran](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Ramachandran](https://community.amazondeveloper.com/u/Ramachandran)\
**Post date:** [September 10, 2026, 12:26pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/15 "2026-09-10T12:26:30Z")

</div>

Thanks for sharing this @Sergio_Gomez , wanted to double check on couple of things again

1. can you please share complete OS version (similar to once you added in initial description)

2. When you login with creds, were you able to see the buybox change in the content detail page in the universal search for titles from Orange TV ( **subscribe** → **watch now** )

Also, while we are checking internally with engineering team and get back on the same,

I am attaching an analysis

[Accout\_login\_not\_printing\_status.md](https://community.amazondeveloper.com/uploads/short-url/j2vMhvU9mkRypUBWeHU8CIYlXhG.md) (8.9 KB) from our externalized builder tool [MCP](https://www.npmjs.com/package/@amazon-devices/amazon-devices-buildertools-mcp) ( you can also try on your end to go through Content launcher and account login implementation in your code project to see if the implementation is correct)

---

<div class="post-metadata">

**Author:** ![Sergio\_Gomez](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sergio\_Gomez](https://community.amazondeveloper.com/u/Sergio_Gomez)\
**Post date:** [September 10, 2026, 2:13pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/16 "2026-09-10T14:13:32Z")

</div>

Hi @Ramachandran,

1. OS version:

- `OS 1.2 (TV Ship/44)` — `OS_VERSION=1.2`, `RELEASE_ID=23`, `OE_VERSION=4.0.0`,  
`BRANCH_CODE=TV Ship`, `VERSION_NUMBER=2301020004420`
- `BUILD_FINGERPRINT=4.0.454119.0(3072cab629675a74)/44N:user/release-keys`
- `BUILD_VARIANT=user`, `BUILD_TAGS=release-keys`, `inDeveloperMode: true`
- Fire TV Stick, product `callie`, `armv7l`, profile `tv`
- Vega CLI `1.2.22`, SDK `0.24.9914`, `kepler-media-account-login` `1.1.22`, Debug armv7

(My first post reported RELEASE\_ID=21 / TV Ship/547; the device has since taken an OS  
update.)

1. Buybox: I cannot check it. No OrangeTV titles appear in universal search on this device  
at all, so there is no content detail page to open. A colleague running the same build on  
a whitelisted device does see our content.

From your analysis, the real finding was the manifest routing, now fixed:

before: override\_attribute\_component = { Status = “com.orange.es.amzftv.main.interface.provider” }  
after: override\_attribute\_component = { Status = “com.orange.es.amzftv.interface.provider” }

With the app-side logging added, the push side passes. Capture from launch → sign in →  
sign out (consecutive duplicate lines removed):

status 1 at launch (13:53:51), 0 on sign in (13:55:06), 1 on sign out (13:55:30). No  
errors, and KeplerScriptAccountLogin::updateStatus completed. with no error following it.  
handleReadStatus is still never invoked, even after the routing fix.

Could you confirm whether this device (firestick-61dc7f4262e3ee0e) is enrolled for the  
OrangeTV catalog integration? If it is not, it explains what is still open: nothing  
triggers a Status read, and our service component is a singleton started on demand, so it  
never starts either.

---

<div class="post-metadata">

**Author:** ![Ramachandran](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Ramachandran](https://community.amazondeveloper.com/u/Ramachandran)\
**Post date:** [September 10, 2026, 2:26pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/17 "2026-09-10T14:26:23Z")

</div>

Thanks @Sergio_Gomez , seems like we have a good improvement there. if you have a full logs that also would help confirm if status is correctly being set.

when you say your colleague can see the orange TV titles but you cannot, then we may need to allow-list your DSN for the orange tv catalog. can you share your DSN ( **Settings → Fire TV → About → Device Serial Number** ) , we can double check and put in a request so that titles can appear and you can check the buybox ( **subscribe** to **watch now) .**  
meanwhile, you can use your collegue’s device to test this buybox scenario if possible.

---

<div class="post-metadata">

**Author:** ![Sergio\_Gomez](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sergio\_Gomez](https://community.amazondeveloper.com/u/Sergio_Gomez)\
**Post date:** [September 10, 2026, 2:39pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/18 "2026-09-10T14:39:24Z")

</div>

Hi @Ramachandran , thanks.

DSN:  
Full logs:

Unfiltered, covering launch → sign in → sign out → sign in on the current debug build (SDK 0.24.9914, kepler-media-account-login 1.1.22, armv7), with the manifest routing fix in place.  
The AccountLoginServer::updateStatus lines are printed by our own wrapper, following the convention from your sample apps, since KCP itself does not log the value.

---

<div class="post-metadata">

**Author:** ![Ramachandran](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Ramachandran](https://community.amazondeveloper.com/u/Ramachandran)\
**Post date:** [September 10, 2026, 2:49pm UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/19 "2026-09-10T14:49:04Z")

</div>

Thanks @Sergio_Gomez , have put in request for allow-listing your DSN for orange tv catalog to test on vega devices. will update once it is done.

---

<div class="post-metadata">

**Author:** ![Sergio\_Gomez](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@Sergio\_Gomez](https://community.amazondeveloper.com/u/Sergio_Gomez)\
**Post date:** [September 11, 2026, 10:18am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/20 "2026-09-11T10:18:46Z")

</div>

Hi @Ramachandran ,  
We have performed a check on the whitelisted device and wanted to confirm if this behavior is correct so we can close the ticket.

After logging into the application and searching for content—specifically the series _Watson_—we see two screens:

- The initial screen that appears after selecting the series

- The screen where we access the seasons and episodes

- We have also observed this behavior with another series—for example, _Death Valley_

 ![Image (3)](https://d3mq594dkmpl37.cloudfront.net/original/2X/c/c996527215ba0bc3e72d6420b793ee2e92b25b2f.jpeg)

Is this the expected behavior?

Thanks.

---

<div class="post-metadata">

**Author:** ![Ramachandran](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@Ramachandran](https://community.amazondeveloper.com/u/Ramachandran)\
**Post date:** [September 11, 2026, 10:36am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/21 "2026-09-11T10:36:03Z")

</div>

yes, this is the right behavior @Sergio_Gomez . we are good to close this

---

<div class="post-metadata">

**Author:** ![system](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/system/32/5065_2.png) [@system](https://community.amazondeveloper.com/u/system)\
**Post date:** [September 25, 2026, 10:36am UTC](https://community.amazondeveloper.com/t/problems-to-observe-login-status-of-accountlogin/29054/22 "2026-09-25T10:36:27Z")

</div>

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