Improve uri handling workflow (#214)

This PR addresses two issues in the URI handler workflow to improve user experience and reliability. 1. Streamline version fallback behavior Problem: When the URI handler receives a build number that is no longer available, the application would fall back to the latest version but display a confirmation dialog. Netflix reported that this confirmation dialog disrupts the user workflow. Solution: Removed the confirmation dialog and replaced it with logging. The handler now silently falls back to the latest available version when the requested build number is unavailable, maintaining a seamless user experience. 2. Fix connect page not displaying when Toolbox is already open Problem: When Toolbox is already running and a URI is executed, the connect page fails to display. Investigation revealed that the UI event emitted via MutableSharedFlow(replay = 0) is lost because the UI collector is not yet active when processEvent() is called. Solution: Introduced a 66-100ms delay before emitting the UI event. This delay ensures the collector is ready to receive events, preventing them from being dropped. The timing was determined through testing and appears to account for the collector initialization time. Note: The delay in fix#2 is a workaround for what appears to be a timing issue with the MutableSharedFlow collector initialization.

Author: fioan89

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## Unreleased
 
+### Changed
+
+- URI handling no longer waits for confirmation to use latest build if the provided build number is too old
+
+### Fixed
+
+- IDE is now launched when URI is handled by an already running Toolbox instance.
+
 ## 0.7.1 - 2025-10-13
 
 ### Fixed

src/main/kotlin/com/coder/toolbox/util/CoderProtocolHandler.kt

@@ -26,6 +26,7 @@ import kotlinx.coroutines.time.withTimeout
 importjava.net.URI
 importjava.util.UUID
 importkotlin.time.Duration
+importkotlin.time.Duration.Companion.milliseconds
 importkotlin.time.Duration.Companion.minutes
 importkotlin.time.Duration.Companion.seconds
 importkotlin.time.toJavaDuration
@@ -111,6 +112,18 @@ open class CoderProtocolHandler(
 CoderCliSetupContext.token = token
  }
 CoderCliSetupWizardState.goToStep(WizardStep.CONNECT)
+
+// If Toolbox is already opened and URI is executed the setup page
+// from below is never called. I tried a couple of things, including
+// yielding the coroutine - but it seems to be of no help. What works
+// delaying the coroutine for 66 - to 100 milliseconds, these numbers
+// were determined by trial and error.
+// The only explanation that I have is that inspecting the TBX bytecode it seems the
+// UI event is emitted via MutableSharedFlow(replay = 0) which has a buffer of 4 events
+// and a drop oldest strategy. For some reason it seems that the UI collector
+// is not yet active, causing the event to be lost unless we wait > 66 ms.
+// I think this delay ensures the collector is ready before processEvent() is called.
+ delay(100.milliseconds)
  context.ui.showUiPage(
 CoderCliSetupWizardPage(
  context, settingsPage, visibilityState, true,
@@ -369,10 +382,7 @@ open class CoderProtocolHandler(
 val buildNumberIsNotAvailable = availableVersions.firstOrNull{it.contains(buildNumber) } ==null
 if (buildNumberIsNotAvailable){
 val selectedIde = availableVersions.maxOf{it }
- context.logAndShowInfo(
-"$productCode-$buildNumber not available",
-"$productCode-$buildNumber is not available, we've selected the latest $selectedIde"
- )
+ context.logger.info("$productCode-$buildNumber is not available, we've selected the latest $selectedIde")
 return selectedIde
  }
 return"$productCode-$buildNumber"