When you install and connect to a server, archipelago asks you if you want to install the companion app...on the companion app.
Steps to Reproduce
Log into a new machine with the companion app
It should prompt you to install the companion app
Expected Behavior
It should not ask
Actual Behavior
It asks you to install the companion app
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
### Description
When you install and connect to a server, archipelago asks you if you want to install the companion app...on the companion app.
### Steps to Reproduce
Log into a new machine with the companion app
It should prompt you to install the companion app
### Expected Behavior
It should not ask
### Actual Behavior
It asks you to install the companion app
### Archipelago Version
1.7.99-alpha
### Hardware
x86_64 (Intel/AMD)
### Relevant Logs
_No response_
### Screenshots
_No response_
The auto-popup is fixed: CompanionIntroOverlay checks for the companion's own JS bridge (window.ArchipelagoNative) and never auto-shows inside the companion app — the “install the companion app” prompt can’t appear there anymore. (Residual polish: the App Store companion banner is still shown to companion users; tracked with the companion-app work.)
The auto-popup is fixed: `CompanionIntroOverlay` checks for the companion's own JS bridge (`window.ArchipelagoNative`) and never auto-shows inside the companion app — the “install the companion app” prompt can’t appear there anymore. (Residual polish: the App Store companion banner is still shown to companion users; tracked with the companion-app work.)
Residual from the 2026-08-30 handoff closed in companion/0.5.28 (web-side, no APK change): the two ungated paths — <CompanionBanner /> (Discover.vue) and openCompanionIntro() (useCompanionIntro.ts) — now gate on isCompanionApp(), and CompanionIntroOverlay's manual-open watcher refuses to open inside the app. The overlay's raw window.ArchipelagoNative check also moved to the canonical helper so detection lives in exactly one place. Vitest added (composables/__tests__/useCompanionIntro.test.ts); full suite green (1013 tests), type-check clean.
Residual from the 2026-08-30 handoff closed in `companion/0.5.28` (web-side, no APK change): the two ungated paths — `<CompanionBanner />` (`Discover.vue`) and `openCompanionIntro()` (`useCompanionIntro.ts`) — now gate on `isCompanionApp()`, and `CompanionIntroOverlay`'s manual-open watcher refuses to open inside the app. The overlay's raw `window.ArchipelagoNative` check also moved to the canonical helper so detection lives in exactly one place. Vitest added (`composables/__tests__/useCompanionIntro.test.ts`); full suite green (1013 tests), type-check clean.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
When you install and connect to a server, archipelago asks you if you want to install the companion app...on the companion app.
Steps to Reproduce
Log into a new machine with the companion app
It should prompt you to install the companion app
Expected Behavior
It should not ask
Actual Behavior
It asks you to install the companion app
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
The auto-popup is fixed:
CompanionIntroOverlaychecks for the companion's own JS bridge (window.ArchipelagoNative) and never auto-shows inside the companion app — the “install the companion app” prompt can’t appear there anymore. (Residual polish: the App Store companion banner is still shown to companion users; tracked with the companion-app work.)Residual from the 2026-08-30 handoff closed in
companion/0.5.28(web-side, no APK change): the two ungated paths —<CompanionBanner />(Discover.vue) andopenCompanionIntro()(useCompanionIntro.ts) — now gate onisCompanionApp(), andCompanionIntroOverlay's manual-open watcher refuses to open inside the app. The overlay's rawwindow.ArchipelagoNativecheck also moved to the canonical helper so detection lives in exactly one place. Vitest added (composables/__tests__/useCompanionIntro.test.ts); full suite green (1013 tests), type-check clean.