Skip to content

fix: handle expired DA token without raw IPC errors#9

Merged
davidnuescheler merged 1 commit into
mainfrom
fix/da-session-expired
Jul 6, 2026
Merged

fix: handle expired DA token without raw IPC errors#9
davidnuescheler merged 1 commit into
mainfrom
fix/da-session-expired

Conversation

@davidnuescheler

Copy link
Copy Markdown
Contributor

Summary

  • When da.live / api.aem.live returns 401, clear the stored IMS token and emit da:session-expired to the renderer
  • Renderer refreshes auth state and returns to home instead of showing raw IPC errors like Error invoking remote method 'da:list': Unauthorized: invalid or expired token
  • Sync, push, and document view error dialogs skip the modal when the failure is an auth expiry

Test plan

  • Sign in, browse a site, then manually invalidate the token file (or wait for expiry) and expand the file tree — app should sign out cleanly, not throw an IPC error
  • After session expiry during browse, confirm Sign in works and the tree loads again
  • Trigger sync/push with an expired token — no error dialog; user is returned to signed-out state
  • npm run lint && npm test pass locally

Made with Cursor

Clear the stored IMS token and notify the renderer when da.live returns
401 so browse, sync, and document views sign out gracefully instead of
surfacing "Error invoking remote method 'da:list'".

Co-authored-by: Cursor <cursoragent@cursor.com>
@davidnuescheler davidnuescheler merged commit 42a616c into main Jul 6, 2026
4 checks passed
@trieloff

trieloff commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.6.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants