Skip to content

fix(openworlds): Resume→play banner mints a DM in the native app (Addresses #356) #359

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
100yenadmin merged 1 commit into from
May 30, 2026
Merged

fix(openworlds): Resume→play banner mints a DM in the native app (Addresses #356) #359

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions viewer/openworlds/screen-launcher.jsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,14 @@ function ScreenLauncher({ onNavigate, state, setState }) {
const target = c || playableCampaign;
if (!target) return;
setState((s) => ({ ...s, activeCampaign: target.id }));
// #356: in the native app a canResume-but-not-yet-live campaign has NO attached DM, so navigating
// straight to the table lands in the read-only director's view. Mint a provider session via the
// bridge (the startPlay path, exactly as onResume does). Only drop straight into the table when the
// session is ALREADY live (an in-browser already-live run, or a browser preview with no bridge).
if (window.OpenWorldsNative?.hasBridge?.() && !target.live) {
startPlay(target.world);
return;
}
onNavigate("table");
};

Expand Down
Loading