Fix external Clash control shortcuts#805
Open
ZenX404 wants to merge 1 commit into
Open
Conversation
Replace the cached Remote.broadcasts.clashRunning state with a direct StatusClient query for start and toggle actions. Always dispatch the stop request for ACTION_STOP_CLASH, ensuring the stop shortcut works even when the app process has not initialized or refreshed its cached service state.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix external Clash control shortcuts when the app's UI process has not initialized or refreshed its cached service state.
Changes
StatusClientto query the service state for start and toggle actions.ACTION_STOP_CLASH.Remote.broadcasts.clashRunningfrom external shortcut handling.Result
The stop shortcut can now stop Clash even when the main application interface has not been opened.
Related discussion: #775