Problem
After clicking the Flashtype update button and restarting through the update flow, Flashtype does not reopen the Markdown document that was opened from Claude. Instead, it opens a different document that had been viewed earlier.
This is confusing because the app appears to lose the file handoff context during the update restart and restores stale document state instead.
Steps to reproduce
- In the Claude app, open a chat that contains a Markdown file.
- Use Open in Flashtype for that Markdown file.
- Confirm that Flashtype opens the expected Markdown document.
- Click the Flashtype update button and let the app update/restart.
- Observe which document is opened after the update completes.
Expected behavior
After the update restart, Flashtype should reopen the same Markdown document that was handed off from Claude via Open in Flashtype.
If the app cannot preserve that exact file context across the update restart, it should avoid opening a stale previous document and instead show a clear recoverable state.
Actual behavior
After the update restart, Flashtype opens a different document that had been opened before, not the Markdown document that was opened from Claude.
Impact
The update flow can make it look like the wrong file was opened or edited. This is especially risky when users launch Flashtype from another app expecting a specific document context.
Reproducibility
Reproducible with the Claude app flow:
- open Markdown file from a Claude chat using Open in Flashtype
- update Flashtype
- a previously opened document is restored instead of the requested file
Problem
After clicking the Flashtype update button and restarting through the update flow, Flashtype does not reopen the Markdown document that was opened from Claude. Instead, it opens a different document that had been viewed earlier.
This is confusing because the app appears to lose the file handoff context during the update restart and restores stale document state instead.
Steps to reproduce
Expected behavior
After the update restart, Flashtype should reopen the same Markdown document that was handed off from Claude via Open in Flashtype.
If the app cannot preserve that exact file context across the update restart, it should avoid opening a stale previous document and instead show a clear recoverable state.
Actual behavior
After the update restart, Flashtype opens a different document that had been opened before, not the Markdown document that was opened from Claude.
Impact
The update flow can make it look like the wrong file was opened or edited. This is especially risky when users launch Flashtype from another app expecting a specific document context.
Reproducibility
Reproducible with the Claude app flow: