I'm using Twilio to send an SMS message. However, the message is not displayed properly on the mobile devices with German text. For example, the message is "Grüße" but the character "ü" and "ß" is not displayed correctly like this:
The issue happen on both Java SDK and cURL with REST. Is there any solution for this?
Open a ticket via the Twilio console to report this issue, along with the Messaging SID(s) experiencing the issue, so they can determine what is causing the problem.
Also, indicate your troubleshooting steps above (Java/cURL), which is important information as well.
Related
have an interesting problem I need to solve, I was hoping if anyone could give me some sort of an idea.
For example, if I get a text from someone saying (string) “URGENT” on my iPhone, I want to call them immediately.
So say I get a message, it could be any message but if their message says “urgent”, I need to call them ASAP, even when my phone is turned off.
Is there a way to do this, using API or anything?? I have no idea!!
Example say I get a messages saying:
Number 042XXXXX sends me a text:
"Hi Name, I have some urgent work for you"
Number 1300 XXX XXX sends me a text:
"Urgent help needed"
Both of these messages would be read by iPhone and their respective numbers would be dialled urgently.
Is there such a way to do this/automate this??
Any advice would be appreciated!!
I have no idea what to do, I am blank!!
I think the problem you have needs an indirect solution because, as Paulw11 points out, Apple don't allow you to inspect the message directly.
It would be possible to make use of Twilio's Programmable SMS API to setup a special phone number that customers could send text messages to. Then you use the APIs of Twilio to read the messages and then send an Apple Push Notification message for those the had "urgent" in the message.
You could then write an iOS app which receives push notification messages and takes the actions you desire. For example, it could present a screen which could automatically dial the number in question.
I think I've found a Telegram bug on the iOS app that causes the bot to send multiple times the same message. The steps to reproduce the problem are:
click on an inline button, type callback
immediately lock the phone screen, before the bot answers
wait a few moments and then unlock the screen
It will be noticed at this point that the bot starts sending the same message numerous times. It is not easy to reproduce, it is important to lock the screen when the bot has not yet answered, so it is easier with bots that take a few moments to respond. Also, in the answer the bot has to send a message (not editing one that already exist).
I use Microsoft Bot Framework to develop the bot, however all the bots give me the same problem, both mine and others developed with other technologies different from mine. For example, I was able to reproduce it on #BotFather too. Sometimes it enters in a loop, and to stop it you have to send any message to the bot.
I use an iPhone 5, iOS version 12.1.2, Telegram version 5.2. I also tried it on an iPhone 8, but not with other versions of Telegram.
I also happen to receive more than 20 identical messages.
I've already contacted Bot Support on Telegram but no one answers me. Is there anyone who experienced the same problem?
On iOS and macOS, when I click on an inline button and switch the client computer (macbook) off (sleep mode) and turn it on my bot receives the last message sent by the user. Each time message_id is the same.
I solve it the following way: when my script sends a request to the Telegram server it receives a response. That response contains a message_id field and I save it.
Any next message must have another message_id. I just compare that number with the stored number and only if the number is other than saved I run the rest part of my script.
You can try my test bot and watch results in google table.
#ios_bug_bot (https://t.me/ios_bug_bot)
https://docs.google.com/spreadsheets/d/1VTx-O1w_-ka1RzGfaVLVBDu0CQxk16QeJTeFYOE4yvo/edit?usp=sharing
The bot source code is here
https://github.com/avtomatron/telegram_bot/blob/master/google_script_bot
I am using twilio to send SMS messages to phone numbers. What I am having problems with is making sure that once a user gets the message the preview of what is at a certain link actually loads in the message the user sees on the phone.
What is the proper way to send a link that automatically shows the preview?
EDIT:
I tried the open graph api. Apple does have a tech note on that. But, then, why does this link provided a proper preview in messages when I send this link to another phone? It works, and it does not use open graph.
https://i1.wp.com/www.asphaltandrubber.com/wp-content/uploads/2017/11/2018-Ducati-Panigale-V4-29.jpg?ssl=1
a couple of things you can try
have the link at start of the message or end of the message
the link should be properly formatted with either http:// or https://
iOS uses The Open Graph protocol to support what image to show in the link . http://ogp.me/
I am trying to build an iOS application. The basic premise is that the user receives an SMS which has a message, a link to the application, and other details. For example, the message might look like this:
Good morning! Kindly open the application: mylink://here
Additional Info: 123123
Additional Info: 321321
I know that if the user has installed my application, he or she will be able to click the mylink://here and it will open my application. Answers in this question discuss said topic thoroughly. My concern mainly has something thing to do with fetching the additional information from the text message. My application will need the additional informations in the SMS and is there a way to fetch the additional information without having to programmatically go through them in my application?
Since the application is opened via SMS, is there a provision in iOS that provides your application, if opened by an SMS, with the raw SMS text?
I'm a bit new in iOS development and I'm mostly relying on what I am able to research online. As much as possible I do not want to fetch the SMSs (if iOS even allows that), find the one I'm looking for, then parse from there.
Well you can't read or send sms messages... At all. That's a big no-no in standard iOS. However, you could pass some simplified info via url scheme. It could look something like this:
myappscheme://www.someurl.com?flag=true&myotherinfo=hi
You'll want to read more about it here: https://developer.apple.com/library/ios/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/Inter-AppCommunication/Inter-AppCommunication.html
Sorry from Apple side but can't access these on a standard, non-jailbroken iPhone. You should file a bug with Apple, perhaps they'll improve SMS access in the future.
Not possible
Check this https://developer.apple.com/library/ios/documentation/MessageUI/Reference/MFMessageComposeViewController_class/index.html
For SMS sending through application allowed but for accessing inbox for sms/email not allowed.
It is only possible when the phone is Jailbreaked. There are many tools to jailbreak your phone.
Once Jailbreaked, an application cal open the SQLite database at
/var/mobile/Library/SMS/sms.db and read the message table.
It contains, the date/time at which the message was received, the sender/recipient phone number and even the clear text of the message.
Refer this Question to read content of sms: Read SMS message in iOS
Is there anything special I need to do when sending http links as part of sms message from IOS programmatically?
When I send a message that includes a link http://echowaves.com/mobile?token=123123 the first part of the link shows as a link, but everything after ? (including ?) shows as a plain text. So when the link is clicked the token parameter is not included. I thought, maybe there is a problem with SMS client that does not know how to parse the links, but the same exact behavior is experienced in IOS as well as on Android. Also, when I try to send the SMS message and manually type the link with parameter -- it get's interpreted properly when received.
Wacky,
just retyped the whole string manually by hand -- and it works. Perhaps some special character or encoding was getting on a way after copy paste string around.