I am trying to pre-populate an sms with text and an url. But the iOS is removing the whole url and only the text "https" is left in the text.
Code:
Send SMS
In SMS:
Look at this awesome link: https
As you are already in a link, you need to encode the URL (the : and slashes / to be specific).
As example, https://example.com would become https%3A%2F%2Fexample.com
In your case, you'd need to change your URL to https%3A%2F%2Fnat5.com%2Fworkout.
Full link:
Send SMS
Reference to URL encoding: https://www.w3schools.com/tags/ref_urlencode.asp
And just as a side note: Both ways are looking to work on Android (At least on Android 7.0)
Related
My app sends unique URLs to users, there's a URL parameter that unique identifies that particular user.
For example:
Hi. Here's your password reset token:
https://myapp.com/password/reset/1111-2222-3333-4444
In iOS, when opening the link in the SMS message the browser opens up https://myapp.com/ without the rest of the URL.
Is there some special encoding iOS requires for URLs in SMS messages to open properly?
Turns out it was a domain redirecting issue where a # was inserted in the URL and client's couldn't follow it properly.
Similar to WhatsApp example https://wa.me/6588888888?text=I%27m%20interested%20in%20your%20car%20for%20sale, how to achieve it with Telegram with URL only? The username and message are required.
I will put the URL in HTML anchor tag href attribute e.g. Click. Thanks.
I have the following problem with Microsoft edge browser. When using 22%3A11 in URL parameter as value, then the browser don't send it as shown in url, but will send it modified as %E2%80%8E22%3A11%E2%80%8E.
With Google Chrome i dont have this issue.
Does anybody know why Microsoft Edge is sending it modified? Instead of sending it as it shown on the URL field?
I'm adding messages that includes url markdown to a slack channel using this format:
<http://somesite.com|friendly name> -> works
<mailto:email#domain.com|friendly name2> -> works
<sip:email#domain.com|friendly name2> -> url markdown doesn't works
When I use <sip://email#domain.com|friendly name2> the markdown convert it to link but the sip client fails to connect due to the extra "//"
Any idea how to make sip links on slack?
Slack's documentation only mentions http/https and mailto schemes for automatic linking, but I played around with their message builder and noticed the following:
Schemes followed by :// seem to be generally supported
In addition there seems to be a whitelist of other schemes supported. The only ones I found working so far are mailto and skype.
While that matches your observation it looks like there is no way to have automatic linking for the sip scheme.
What you could do is to write a Slack App, which provides a command (e.g. /sip email#domain.com), which will print a link to a website which redirects you to the proper sip-URL. I believe that's the approach other services like Zoom use as well for their Slack integration.
An interesting alternative could be to contact Slack and kindly ask them to add sip-URLs to their whitelist.
I am writing an application that lets the user specify a website URL in a textfield. As I gave the app to testers I noticed that most users will not naturally enter the "http://" or "https://" part of a website url, and when told they need to enter the url scheme before "www..." they get frustrated and some don't even know it.
So, once the user enters the url to a site in the textfield, if they did not specify either "http://" or "https://", I want the app to prefix the url entered by the user with the correct scheme, either "http://" or "https://".
When in an iOS app how can I know the correct scheme the website url needs to have so that I can simply prefix the string entered by the user with the correct url scheme?
So, this was marked as a possible duplicate. I can see how it could be perceived as such. However, my intention is not to make the URL work in a UIWebView, my main goal is to actually detect what the correct scheme is before trying to load the url in a UIWebView. So, the possible duplicate feedback is actually wrong. I want to know how to find the correct scheme without having to load the site through a WebView.