Pinpoint SMS Message with URL Isn't Actually Sent(Received by phone)

[mjmostachetti]

Describe the bug

I can send messages via the Pinpoint SMS without a problem if there is no https:// url in the text message. It even works just fine with a custom scheme(fakeScheme://). I'm trying to setup some deep linking messages on Android, which requires an https url, but these texts are not received by the phones. Is this expected? Am I missing something/configuration within pinpoint, or is this a bug?

Expected Behavior

I can send text messages with valid https:// urls in the message and it be received by the phone.

Current Behavior

I get this response, even though the message never gets to my phone.

{
    "MessageResponse": {
        "ApplicationId": "34740ce3c47e44d2adc7bfbd7fa3a9b8",
        "RequestId": "145d4e31-0c93-4a69-a5b5-c27fbb477ef5",
        "Result": {
            "myvalidnumber": {
                "DeliveryStatus": "SUCCESSFUL",
                "MessageId": "q9r65afkslog0pbpk248c1tto0d89d5poq1hj5o0",
                "StatusCode": 200,
                "StatusMessage": "MessageId: q9r65afkslog0pbpk248c1tto0d89d5poq1hj5o0"
            }
        }
    }
}

Reproduction Steps

var message = "Hello, please go to this link - https://environment.fjasdfaklsjdfasd.amplifyapp.com/blah/blah";
 
 const params = {
      ApplicationId: applicationId,
      MessageRequest: {
        Addresses: {
          [phoneNumber]: {
            ChannelType: "SMS",
          },
        },
        MessageConfiguration: {
          SMSMessage: {
            Body: message,
            Keyword: registeredKeyword,
            MessageType: "TRANSACTIONAL",
            OriginationNumber: originationNumber,
            SenderId: senderId,
          },
        },
      },
    };

pinpoint.sendMessages(params, function (err, data) {
      if (err) {
        console.log(`ERROR : ${JSON.stringify(err)}`);
        reject(err);
      } else {
        console.log(`SUCCESS : ${JSON.stringify(data)}`);
        resolve();
      }
    });

Possible Solution

No response

Additional Information/Context

No response

SDK version used

^2.1264.0

Environment details (OS name and version, etc.)

Node AWS Lambda

[RanVaknin]

Hi @mjmostachetti ,

While we try to reproduce this, can you please check out this troubleshooting guide?
I would also check against a different phone on a different network, and check your spam folder for auto-screened messages.

Maybe the carrier blocks incoming messages with hyperlinks in them as a security measure against phishing attacks and marketing campaigns?

Thanks,
Ran~

[CayneBartoo]

I am experiencing something similar, is this still an issue?

[mjmostachetti]

We stopped trying this and resorted to sending emails with the url instead.

…

On Thu, Sep 14, 2023 at 10:15 PM CayneBartoo ***@***.***> wrote: I am experiencing something similar, is this still an issue? — Reply to this email directly, view it on GitHub <#4334 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRPWL6AQVB6YS2YB472YX3X2PQARANCNFSM6AAAAAAUQYMEPY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mjmostachetti]

@RanVaknin Do you have any documentation or info about this? How does AWS assign a phone number to send from in Pinpoint? It seems like there's an issue there or however carriers allow/block numbers from sending content. I just tried out a trial Twilio account, and I can send links through their API without any issues to my phone. The Twilio number is toll-free, just like the AWS phone number.