🐛 Bugfix: How to fix blank page when unauthenticated guest user naviga...

Date: 2026-02-06
Time: 22:22:38 UTC
Session: editor2-97.14
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How to fix blank page when unauthenticated guest user navigates to non-temp space URL?

Task: Fix blank page crash when unauthenticated user navigates to space URL

🎯 Decision Made

Chosen:

Redirect guest users to /landing in spaceGuard when no space is loaded (line 519), and add safety-net redirect in spaceResolver

Options Considered:

1. Redirect guest to /landing when no space loaded
2. Create temporary space for guest at any URL
3. Add error boundary component
4. Redirect to /login for all unauthenticated users

💭 Reasoning

Root cause: spaceGuard returned true for guest users at non-temp space URLs (e.g., /space/chrome-space-1/...) even when no space was loaded. This cascaded through spaceResolver (returned null) to components that rendered blank. Fix: redirect to /landing instead of allowing navigation with no space context. Safety net in spaceResolver catches any edge cases where guards pass but space is still null.

📁 Files Involved

• libs/libs-foundational/core-angular/src/lib/guards/space.guard.ts
• libs/libs-foundational/core-angular/src/lib/resolvers/space.resolver.ts

🔗 Related

• Decision ID: dev_1770416557917_dxtqaj0
• Session: 97
• Workspace: editor2

Auto-generated by MCP Smart Consolidation