[davidsu]

Note

Description

base44 site open on an app that was never published failed with "Error fetching site URL: App not found", which reads as if the app id were wrong. The published-URL endpoint only answers for live apps, so a 404 from it means "not published" — the command now says exactly that and hints at publishing. Any other lookup failure (e.g. a 500) still surfaces the server's own error unchanged.

Related Issue

Follow-up to #693 (BUG-893). Task: BASE-36419

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

• Added AppNotPublishedError (code APP_NOT_PUBLISHED, a UserError) in packages/cli/src/core/errors.ts, with the message "This app has not been published yet, so it has no site URL" and a hint pointing at base44 deploy.
• site open wraps getSiteUrl() in getPublishedSiteUrl(), which maps an ApiError with status 404 to AppNotPublishedError and rethrows every other error untouched.
• Documented the new error code in the error-code table in docs/error-handling.md.
• Added a Fixed entry to CHANGELOG.md.
• Tests: the existing 404 case now asserts the new message, the base44 deploy hint, and the absence of "App not found"; a new 500 case asserts the server error still comes through and the "not published" wording does not.

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (npm test)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated docs/ (AGENTS.md) if I made architectural changes

Additional Notes

The 404 → "not published" mapping lives in the site open command rather than in getSiteUrl(), so other callers of the URL lookup keep their current error behaviour. If more commands need the same treatment, the mapping is the natural thing to lift into core/project/.

---

_{🤖 Generated by Claude | 2026-11-04 18:55 UTC | b9f40b5}

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.3.1-pr.694.631024e

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.3.1-pr.694.631024e"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.3.1-pr.694.631024e"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.3.1-pr.694.631024e
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}