Incorrect type in Zod schema causing issues for /status/sessions endpoint

[DominicFichera]

https://github.com/LukeHagar/plexjs/blob/03910be91fd278a70695462cc9aeefe16971b2ec/src/sdk/models/shared/tag.ts#L25

A number of the types in the Zod schema don't match the actual response provided by the Plex API response to the /status/sessions endpoint, and as a result, Zod is throwing an error and not returning response.

Currently running Plex version: 4.147.1

Full URL: http://127.0.0.1:32400/status/sessions

  const plexAPI = new PlexAPI({
    token: "xxxxxxxx",
    accepts: Accepts.ApplicationJson,
    clientIdentifier: "xxxxxxx",
    serverURL: "http://127.0.0.1:32400",
  });
  plexAPI.status.listSessions({}).then((res) => console.log(res));

{
    "code": "invalid_type",
    "expected": "number",
    "received": "string",
    "path": [
      "object",
      "MediaContainer",
      "Metadata",
      0,
      "Director",
      0,
      "id"
    ],
    "message": "Expected number, received string"
  }

{
    "code": "invalid_type",
    "expected": "boolean",
    "received": "string",
    "path": [
      "object",
      "MediaContainer",
      "Metadata",
      0,
      "Media",
      0,
      "hasVoiceActivity"
    ],
    "message": "Expected boolean, received string"
  }

[johnschult]

Also seeing this....

[HermesMora]

Thanks for the report, and to @johnschult for confirming — a second independent report makes this a real issue rather than an environment-specific one.

The problem: the Zod schema for /status/sessions types the session id as a string (matching what PMS actually returns), but the generated TypeScript model/response shape expects a number (or vice versa), so validation fails on a successful response. This is the same class of spec-vs-reality type drift seen in #22 and in the plexgo reports (LukasParke/plexgo#7).

Recommendation: align the spec's id type for session resources (string) and regenerate. If you can share the exact SDK version and the failing field path from the SDKValidationError, that would make the spec fix quicker. Tracking under the same spec-drift work.

— HermesMora (automated assistant to the maintainer)