Package ID Conflicts from Account-Associated Extensions in Local Development

Dear Lucid Community,

I’m encountering package ID conflicts while testing a locally loaded extension. I suspect Lucid’s heartbeat mechanism is polling all extensions registered under my account, causing errors despite my manifest specifying the correct package ID. Below are the errors:

2603117…cd8957bf.js.br:2598 Attempting to heartbeat data from a locally loaded extension with package id: 404f484c-776f-4e9c-aaf1-0ecb56722e84 but the current locally loaded extension has package id: 7d1b85e8-df91-4c38-8e97-a10345ac9bf3. Skipping heartbeating for this data.
2603117…cd8957bf.js.br:2598 Attempting to heartbeat data from a locally loaded extension with package id: d38c7ced-35e8-4962-a622-1d3fa480ab58 but the current locally loaded extension has package id: 7d1b85e8-df91-4c38-8e97-a10345ac9bf3. Skipping heartbeating for this data.
[Repeated multiple times]
​​​​​​​

Details:

Details:

• My extension’s package ID is 7d1b85e8-df91-4c38-8e97-a10345ac9bf3, matching the Developer Portal: https://lucid.app/developer#/packages/7d1b85e8-df91-4c38-8e97-a10345ac9bf3.
• Conflicting IDs (404f484c-776f-4e9c-aaf1-0ecb56722e84, d38c7ced-35e8-4962-a622-1d3fa480ab58) are tied to my account, likely from old test packages.
• Local server: http://localhost:3002.

Steps Tried:

• Cleared browser storage for lucid.app and localhost:3000.
• Ran npm cache clean --force, npx clear-npx-cache, deleted node_modules, and rebuilt.
• Tested in a fresh browser profile.
• Searched codebase for conflicting IDs (none found).
• Confirmed conflicting IDs are in Developer Portal but couldn’t delete them yet.

Manifest:

{
  "id": "7d1b85e8-df91-4c38-8e97-a10345ac9bf3",
  "version": "0.0.21",
  "extensions": [
    {
      "name": "iwm_editor_extension",
      "title": "iwm_editor_extension",
      "products": ["chart", "spark", "teamspaces"],
      "codePath": "editorextensions/iwm_editor_extension/bin/extension.js",
      "scopes": ["READ", "WRITE", "DOWNLOAD", "SHOW_MODAL", "CUSTOM_UI", "NETWORK"]
    }
  ],
  "shapeLibraries": [],
  "oauthProviders": [
    {
      "name": "local-dev",
      "title": "Local Development",
      "authorizationUrl": "http://localhost:3002/oauth/authorize",
      "tokenUrl": "http://localhost:3002/oauth/token",
      "scopes": ["read"],
      "domainWhitelist": ["http://localhost:3002"],
      "clientAuthentication": "clientParameters"
    }
  ],
  "dataConnectors": [
    {
      "name": "shape-logger-data-connector",
      "oauthProviderName": "local-dev",
      "callbackBaseUrl": "http://localhost:3002/?kind=action&name=",
      "dataActions": { "LogShapes": "LogShapes" }
    }
  ]
}

Questions:

1. Does Lucid’s heartbeat poll all account extensions, and how can I limit it to my active extension?
2. How do I delete/archive old packages in the Developer Portal to stop conflicts?
3. Are there tools to disable heartbeating or clear metadata locally/server-side?
4. Any tips to resolve this and regain control over my local environment?

Thanks for your help!