Uh oh!
There was an error while loading. Please reload this page.
feature(dev-middleware): use userAgent query parameter as fallback when header is unset - #43364
Closed
byCedric wants to merge 1 commit into
Closed
feature(dev-middleware): use userAgent query parameter as fallback when header is unset#43364byCedric wants to merge 1 commit into
userAgent query parameter as fallback when header is unset#43364byCedric wants to merge 1 commit into
Conversation
…when header is unset
4 tasks
motiz88
commented
Mar 8, 2024
Contributor
Unit test please, but LGTM otherwise |
ContributorAuthor
Heads up that none of the tests currently test the
Edit: We don't have access to the One thing we could do is rebase this on #43291 and test it through the |
motiz88
commented
Mar 12, 2024
Contributor
Yes please, that would help us keep from breaking your code that depends on it. |
motiz88
commented
Mar 12, 2024
Contributor
Let's do the test in a separate PR to make sure we can land this in time for the next RC. |
facebook-github-bot
commented
Mar 12, 2024
Contributor
@motiz88 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
facebook-github-bot
commented
Mar 12, 2024
Contributor
huntie pushed a commit
that referenced
this pull request
Mar 18, 2024
…when header is unset (#43364) Summary: At Expo, we use [Expo Tools](https://github.com/expo/vscode-expo/blob/main/src/expoDebuggers.ts) to connect the [built-in vscode-js-debug](https://github.com/microsoft/vscode-js-debug) to Hermes. Since there are a few differences in vscode vs chrome devtools, we need to enable a couple of modifications through the [`customMessageHandler` API](#43291). Unfortunately, vscode itself doesn't set the `user-agent` header when connecting to the inspector proxy. Becuase of that, we'd need a fallback to "manually" mark the debugger as being vscode ([we use this query parameter here](https://github.com/expo/vscode-expo/blob/main/src/expoDebuggers.ts#L208)). This PR supports setting the `user-agent` through `?userAgent=` when the header is not set. ## Changelog: <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [GENERAL] [ADDED] - Fallback to query parameter based `user-agent` when header is unset Pull Request resolved: #43364 Test Plan: - Install [Expo Tools](https://marketplace.visualstudio.com/items?itemName=expo.vscode-expo-tools) - Start Metro with this change. - Connect a device. - Run the vscode command `"Expo: Debug Expo app ..."` - Debugger should connect, and have it's user-agent marked as: `vscode/1.87.0 vscode-expo-tools/1.3.0` Reviewed By: huntie Differential Revision: D54804556 Pulled By: motiz88 fbshipit-source-id: 1ff558ba5350811ad042d08a713438e046759feb
facebook-github-bot pushed a commit
that referenced
this pull request
Mar 20, 2024
…#43559) Summary: This is a follow-up bugfix for expo/expo#27425, related to: - #43291 - #43307 - #43310 - #43364 The middleware API works as intended and can run our extended CDP events. Unfortunately, this only applies to an actual `Page` from the device, not for the `React Native Experimental (Improved Chrome Reloads)` synthetic / virtual page. That's because the middleware instantiation gets aborted when the page can't be found in `this.#pages.get(pageId)`, which always returns `null` for this synthetic page. ## Changelog: [GENERAL] [FIXED] Create custom message handler for synthetic page Pull Request resolved: #43559 Test Plan: See added test case. Reviewed By: motiz88 Differential Revision: D55129412 Pulled By: huntie fbshipit-source-id: 9679d8fe68f3cb4104f4a042f93612b995baddc9
huntie pushed a commit
that referenced
this pull request
Mar 21, 2024
…#43559) Summary: This is a follow-up bugfix for expo/expo#27425, related to: - #43291 - #43307 - #43310 - #43364 The middleware API works as intended and can run our extended CDP events. Unfortunately, this only applies to an actual `Page` from the device, not for the `React Native Experimental (Improved Chrome Reloads)` synthetic / virtual page. That's because the middleware instantiation gets aborted when the page can't be found in `this.#pages.get(pageId)`, which always returns `null` for this synthetic page. ## Changelog: [GENERAL] [FIXED] Create custom message handler for synthetic page Pull Request resolved: #43559 Test Plan: See added test case. Reviewed By: motiz88 Differential Revision: D55129412 Pulled By: huntie fbshipit-source-id: 9679d8fe68f3cb4104f4a042f93612b995baddc9
This was referenced Apr 5, 2024
This was referenced Jun 28, 2024
Merged
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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:
At Expo, we use Expo Tools to connect the built-in vscode-js-debug to Hermes.
Since there are a few differences in vscode vs chrome devtools, we need to enable a couple of modifications through the
customMessageHandlerAPI. Unfortunately, vscode itself doesn't set theuser-agentheader when connecting to the inspector proxy. Becuase of that, we'd need a fallback to "manually" mark the debugger as being vscode (we use this query parameter here).This PR supports setting the
user-agentthrough?userAgent=when the header is not set.Changelog:
[GENERAL] [ADDED] - Fallback to query parameter based
user-agentwhen header is unsetTest Plan:
"Expo: Debug Expo app ..."vscode/1.87.0 vscode-expo-tools/1.3.0