Skip to content

Unable to create a new user on fresh install of v2.5.14: TypeError: Cannot convert undefined or null to object #1577

Closed

Description

@lumiera

/about output:

{
  "version": "v2.5.14",
  "uiVersion": "v2.5.14",
  "commit": "08073d6",
  "deploymentId": "01KKBMQ41SRQX84E59YHVR4EV4",
  "updateAvailable": false,
  "latestVersion": null,
  "llmActive": false,
  "llmProvider": null,
  "oidcActive": false,
  "license": {
    "name": "AGPL-3.0-only",
    "version": "v1",
    "plan": "OSS",
    "deploymentInfo": "Managed"
  },
  "mode": "Standalone",
  "staging": "/data/staging",
  "hotTier": "Disabled",
  "grpcPort": 8001,
  "store": {
    "type": "Local drive",
    "path": "/data/local-storage"
  },
  "analytics": {
    "clarityTag": null
  }
}

Description:

Navigating to Teams -> Users and clicking the "+ Add User" button produces the following in the browser window:

Unexpected Application Error!
Cannot convert undefined or null to object
TypeError: Cannot convert undefined or null to object
    at Object.keys (<anonymous>)
    at Ms (http://hostname/assets/index-DPzyeB0C.js:1:1517)
    at Fv (http://hostname/assets/react-vendor-BGNZeM7C.js:30:17862)
    at SS (http://hostname/assets/react-vendor-BGNZeM7C.js:32:44990)
    at mS (http://hostname/assets/react-vendor-BGNZeM7C.js:32:40558)
    at v3 (http://hostname/assets/react-vendor-BGNZeM7C.js:32:40486)
    at Jd (http://hostname/assets/react-vendor-BGNZeM7C.js:32:40339)
    at ug (http://hostname/assets/react-vendor-BGNZeM7C.js:32:36598)
    at pS (http://hostname/assets/react-vendor-BGNZeM7C.js:32:37410)
    at Ua (http://hostname/assets/react-vendor-BGNZeM7C.js:30:3273)
💿 Hey developer 👋

You can provide a way better UX than this when your app throws errors by providing your own ErrorBoundary or errorElement prop on your route.

This is v2.5.14, fresh install.

Activity

  1. nitisht commented on Mar 10, 2026

    @nitisht
    Member

    Thanks for reporting @lumiera we'll take a look ASAP

  2. nitisht commented on Mar 10, 2026

    @nitisht
    Member

    This is a regression in 2.5.14, we've identified the issue and we'll fix this in the next release - within the next week. Meanwhile, you can use the release 2.5.13 if this is blocking your work.

  3. lumiera commented on Mar 10, 2026

    @lumiera
    Author

    Thank you, I just tried 2.5.13 and it works. I will use this version until the fix is out.

  4. nitisht commented on Mar 18, 2026

    @nitisht
    Member

    The fix is released now - closing this for now. Feel free to reopen if this is still a problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions