Skip to content

Known Issues

Issues and limitations documented for current and past versions of the portfolio stack.

UIGen v0.16.0 — Form Rendering Failure

Status: Blocking Component: UIGen API Explorer Affected Operations: Write operations (POST/PATCH/PUT) Version: v0.16.0 First Reported: 2026-05-24

Issue

When rendering forms for write operations in UIGen v0.16.0, forms fail with:

TypeError: Cannot destructure property 'setValue' of 'wO(...)' as it is null.
  at _ge (index-BlQ4jjmh.js:282:70254)
  at [react-hook-form internals]

This error occurs regardless of authentication state — even authenticated users with proper bearer tokens experience form rendering failures when attempting to interact with write operation forms.

Root Cause

react-hook-form context is not properly initialized when UIGen renders form components. The FormProvider context wrapper is either missing or initialization failed silently between v0.10.0 and v0.16.0.

Impact

  • ❌ Admin users cannot submit forms through UIGen dashboard
  • ❌ Write operations (project/experience creation, updates, deletions) are blocked
  • ✅ Read operations work fine (data browsing, retrieval)
  • ✅ API endpoints work correctly (tested with curl/Postman)
  • ✅ Authentication and OAuth flow work properly

Workarounds

Use API directly:

# Project creation via curl
curl -X POST http://localhost:8000/api/projects \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"slug":"my-project","title":"My Project",...}'

Downgrade to UIGen v0.10.0:

  • Forms render and work correctly
  • Older version but stable for write operations
  • Change Dockerfile.uigen lines 14 and 131

Monitor UIGen v0.17.0+:

  • Status of form rendering in newer versions unknown
  • Test before upgrading to production

Testing Status

  • ✅ Authentication flow verified
  • ✅ OAuth login button displays
  • ✅ Authenticated users can browse data
  • ❌ Form rendering fails even for authenticated users
  • ❌ Custom error boundary overrides don't work (React not in transpiler scope)
  • Portfolio PR #474: UIGen v0.16.0 upgrade investigation
  • UIGen repository: Issue pending report (repository lookup needed)

Timeline

  • 2026-05-10: UIGen v0.16.0 upgrade attempted
  • 2026-05-24: Form rendering failure confirmed for all write operations
  • TBD: UIGen upstream issue reported
  • TBD: Fix released in v0.17.0 or later

Previous Issues

(Historical issues resolved)

✅ DeploymentActive Race on Dev (Resolved)

Status: Fixed in PR #67 + hotfix Root Cause: Concurrent ARM template deployments colliding Solution: Concurrency group now includes github.ref

✅ Post-Deploy E2E Secrets Missing (Resolved)

Status: Fixed 2026-05-16 Issue: E2E_CLIENT_ID and E2E_CLIENT_SECRET not set in GitHub environments Solution: Secrets added to both dev and prod environment configs

Monitoring

Check this page for updates on known issues and workarounds.

For new issues, check:

  1. Portfolio CI logs — Actions tab on GitHub
  2. Local stack — docker-compose logs -f
  3. UIGen logs — docker-compose logs uigen
  4. Browser console — Playwright test screenshots in test-results/