I'm on a Galaxy A15 5G which was working fine until I updated the app to fix a bug. The bug is fixed and the Android will fade an info message saying that "Message sent", but I don't receive the message.
The app was able to send messages before I put in the update to the html.
I have an older version of the app on my other phone and it works fine.
Is there something wrong with the OS settings of this device?
How exactly did you upgrade the app? Did you simply update the existing installation or did you uninstall/reinstall? Usually the latter will reset the permissions, including SMS. I've noticed in newer Android versions as well I have to manually request via the Settings app to turn on "restricted" permissions such as SMS before the app can even ask for the permission.
I uninstalled/reinstalled the app. I got a popup asking to allow permission to send SMS and I accepted. The phone will create a text message which looks sent, but never gets received.
I have another app on the same phone where I can write a message out and hit send, and it works fine. I receive the messages that are sent via SendMessageDirect.
I just tried manually setting the SMS permission, but it's not working.
I'm using window.AppInventor.setWebViewString(${job.phone}|Update your phonebook: ${job.url}); to set the reply. The phone sends the message the first and fourth time, it takes 3 tries to send the message again
Which device and Android version are you using for your tests?
see also this thread
Taifun
Galaxy A15 5G, Android 15
SendDirectMessage works fine for short messages, but it won't send the text of my weblinks which are like 38 characters long
Okay, did some more testing. The text won't receive when it's my weblink, mentafresca.space. But if I use a faulty url like mentafresca.com or google.com, the text works. I think it's my phone that's placing an antispam measure. Any suggestions?
In your tests are you sending the sms from your device to the same device? Try to send it to another device
What happens if you try to send your weblink manually from your default sms app?
Taifun
I'm doing both.
So I think I found the diagnosis. The phone blocks texts with weblinks that doesn't use common subdomains like .com or .org, etc.
I bought a new TLD name, and my tests are working without issue now.
Any comments? Has anyone else encountered this before?
What happens if you try to send your weblink manually from your default sms app?
I have a test app where I send the message manually using SendDirectMessage. .space TLD had trouble sending, but not .com domains. .com TLD's had no issue
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.