Document allowSubdomains field for web-to-app linking JSON configuration #5603
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.
The
allowSubdomains
field in the web-to-app linking JSON configuration was missing from the documentation, despite being essential for subdomain support. Users registering both main domains (e.g.,example.com
) and wildcard subdomains (e.g.,*.example.com
) in their app manifest need this field to enable proper subdomain handling.Problem:
Without
allowSubdomains: true
in the JSON file, subdomain links likefr.example.com/path
would open in the browser instead of the app, even when the app manifest includes wildcard subdomain registration.Changes:
allowSubdomains
field usageThe documentation now provides complete guidance for developers who need subdomain support in their web-to-app linking configuration.
Fixes #4510.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
maps.windows.com
curl -s REDACTED
(dns block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.