Skip to content

Fix Discord deeplink forwarding to a running FrameRelay instance - #44

Merged
hugoalves-dev merged 1 commit into
mainfrom
codex/fix-discord-deeplink-forwarding
Sep 30, 2026
Merged

hugoalves-dev merged 1 commit into
mainfrom
codex/fix-discord-deeplink-forwarding

Conversation

@hugoalves-dev

Copy link
Copy Markdown
Owner

Discord launch links can fail when FrameRelay is already open, forcing users to close the app and launch it again. The activation pipe creates auto-flushing UTF-8 writers on both ends before reading, which can block while flushing the preamble.

Read the request before creating the server writer and use UTF-8 without a preamble on both ends. Keep BOM detection enabled for incoming messages. Add regression coverage for consecutive share and watch activations over a unique pipe, so tests can run while the installed application is open.

Validation: all 5 focused activation coordinator and instance policy tests passed. The original forwarding test hung before the fix. Build and git diff --check passed. The installed application and real Discord flow have not been updated or validated.

Test command:

dotnet test tests/SonicDesktopRelay.App.Tests/SonicDesktopRelay.App.Tests.csproj --no-restore --filter 'FullyQualifiedName~LaunchActivationCoordinatorTests|FullyQualifiedName~LaunchInstancePolicyTests' --verbosity quiet --blame-hang-timeout 45s --blame-hang-dump-type none

@hugoalves-dev
hugoalves-dev merged commit 7d9cac6 into main Sep 30, 2026
4 checks passed
@hugoalves-dev
hugoalves-dev deleted the codex/fix-discord-deeplink-forwarding branch September 30, 2026 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant