-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS Linking escapes hash's #28508
Comments
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Backlog |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
I got same issue |
can fix by using encodeURI |
We recently landed 2b4e1f5 that should fix the issue. |
We had to back out the changes due to some internal tests failing. |
Summary: This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Differential Revision: D45078923 fbshipit-source-id: 97f417bbad086df1d16dbf509e7bf49f6f745583
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: b7154302260304291b09be5d5e7a0d43e0514ed3
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. The problem here was that the e2e tests sends some urls with some `%` symbol which does not belongs to an escape sequence. For example: `anna://launch?height=25%`. The previous code (v1) was trying to unescape this case. V2 fixes this. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: 0f29e94523c35e97c86daf7d710c599363d56352
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. The problem here was that the e2e tests sends some urls with some `%` symbol which does not belongs to an escape sequence. For example: `anna://launch?height=25%`. The previous code (v1) was trying to unescape this case. V2 fixes this. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: 94e882e797db879c4f1be24d163817aa60ef3776
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. The problem here was that the e2e tests sends some urls with some `%` symbol which does not belongs to an escape sequence. For example: `anna://launch?height=25%`. The previous code (v1) was trying to unescape this case. V2 fixes this. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: a09e434ac1365949f1a738c9c17111a92d55677b
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. The problem here was that the e2e tests sends some urls with some `%` symbol which does not belongs to an escape sequence. For example: `anna://launch?height=25%`. The previous code (v1) was trying to unescape this case. V2 fixes this. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: 6daac460dd4424131341d18c400a39ce2b605436
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. The problem here was that the e2e tests sends some urls with some `%` symbol which does not belongs to an escape sequence. For example: `anna://launch?height=25%`. The previous code (v1) was trying to unescape this case. V2 fixes this. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: 3e6cbd0c0532e85c31fb0b7aa3ab3cef1c5c6f6c
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. The problem here was that the e2e tests sends some urls with some `%` symbol which does not belongs to an escape sequence. For example: `anna://launch?height=25%`. The previous code (v1) was trying to unescape this case. V2 fixes this. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: 2796d175ac21befc49afd1b940d5c2a0c93ed00b
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. The problem here was that the e2e tests sends some urls with some `%` symbol which does not belongs to an escape sequence. For example: `anna://launch?height=25%`. The previous code (v1) was trying to unescape this case. V2 fixes this. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: 010a5c173784f8341a1a08bcbd06a6ad14299c75
Summary: Pull Request resolved: facebook#36949 This change is a second attempt at fixing URL encoding and escaping that was already tried [here](facebook@2b4e1f5). We had to roll it back due to some internal tests failing as it looks like Jest is manipulating the URL somehow. We manage to replicate the issue, which occur when we pre-decode a url even if it is not partially encoded (we were too aggrsssive). This fix ensure that we pre-decode the urls only if they present some `%` characters. The problem here was that the e2e tests sends some urls with some `%` symbol which does not belongs to an escape sequence. For example: `anna://launch?height=25%`. The previous code (v1) was trying to unescape this case. V2 fixes this. This change should also fix facebook#28508 for good. ## Changelog: [iOS][Fixed] - Properly escape URLs Reviewed By: mdvacca Differential Revision: D45078923 fbshipit-source-id: 010a5c173784f8341a1a08bcbd06a6ad14299c75
Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
When I try to link with
import { Linking } from 'react-native';
an url with#
on iOS the safari opens the url escaped with%23
instead of#
.for example
https://www.democracy-deutschland.de/#!engineering#help
opens in safarihttps://www.democracy-deutschland.de/%23!engineering%23help
React Native version:
Steps To Reproduce
#
Expected Results
do not escape by Linking library. or add options to handle this
Snack, code example, screenshot, or link to a repository:
https://github.com/demokratie-live/democracy-client
The text was updated successfully, but these errors were encountered: