A
AC Question
We noticed a strange behaviour when sending text messages containing url's which contain a hashbang (#) character. When clicking on such a link, an in-app browser opens the url but cuts-off everything starting at the hashbang character.
Example url: "example.com/#/c?code=ABCDEFG" with https:// in front.
When sending this url in a text message to my Samsung Galaxy S6, opening the text message with the default message app and clicking the link, an in-app browser opens using the url "example.com/" with https:// in front. Everything starting with at hashbang character is cut-off from the url.
This does not happen when using another text messages app, e.g. textra, only using the default message app.
Anyone knows how to fix that in the default text messaging app?
Note: We are developing apps that need to work with such a default setup on a user's phone, therefore solutions like "just use another text messages app" can't be applied by us.
Thanks very much for any help,
Sebastian
Example url: "example.com/#/c?code=ABCDEFG" with https:// in front.
When sending this url in a text message to my Samsung Galaxy S6, opening the text message with the default message app and clicking the link, an in-app browser opens using the url "example.com/" with https:// in front. Everything starting with at hashbang character is cut-off from the url.
This does not happen when using another text messages app, e.g. textra, only using the default message app.
Anyone knows how to fix that in the default text messaging app?
Note: We are developing apps that need to work with such a default setup on a user's phone, therefore solutions like "just use another text messages app" can't be applied by us.
Thanks very much for any help,
Sebastian