Skip to content

Signal registration SMS provider rejects Ukrainian mobile range +380790 #15030

Open

Description

@Roman-JY

Guidelines

  • I have searched open and closed issues for duplicates
  • I am submitting a bug report for existing functionality that does not work as intended
  • This isn't a feature request or a discussion topic

Bug description

Signal registration fails for multiple active mobile numbers in the Ukrainian +380790 range operated by J&Y LLC. After completing CAPTCHA and requesting an SMS verification code, the app displays: “Signal couldn't send an SMS code because of issues with the SMS provider.”

The issue has been consistently reproducible for more than six months. The debug log confirms that the number is valid and the registration session is created successfully, but Signal’s third-party verification provider rejects the SMS request with reason=providerRejected.

Screenshots

Image

Device

Samsung SM-A075F

Android version

16 / API 36

Signal version

8.27.1

Link to debug log

https://debuglogs.org/android/8.27.1/f45b1750fc1c94f5373971c5414e93f98e2b0d138b0430a927c510b70404c65e

Activity

  1. westsibe commented on Sep 30, 2026

    @westsibe

    May be helpful here this manual for sign-up

  2. dimonalek commented on Oct 2, 2026

    @dimonalek

    I am also dealing with such problem on some +38063xxx prefixes. Others from this (Lifecell) operator are registering fine. Seems like some sort of blacklist at sms sender provider.

  3. Behekot commented on Oct 5, 2026

    @Behekot

    Having the same issue with Vodafone, +38050 prefix

  4. MauroFoti commented on Oct 6, 2026

    @MauroFoti

    How are you specifying the prefix in the registration UI? Did you enter it manually or it was autofilled? I'm asking you because I had a problem a few days ago registering an Italian number (+39 prefix) and, no matter what I tried, it gave me the same error.

    The workaround I found was, before entering the phone number, the prefix was autodetected and already filled and I simply changed it and selected it again manually from the list, then it sent the SMS immediately. This seems to me more like an UI issue, where some code is updating the selector when it detects the prefix, but it's probably not updating some other field sent to the server that is updated when selecting manually.

  5. Behekot commented on Oct 6, 2026

    @Behekot
  6. MauroFoti commented on Oct 6, 2026

    @MauroFoti

    You're welcome :) I think this issue should remain open as it's clearly a bug in the interface, and a very serious one since it prevents people from registering the first time and can lead a lot of people to just disregard Signal.

  7. cody-signal commented on Oct 6, 2026

    @cody-signal
    Contributor

    Yes, thanks for the extra details @MauroFoti on a workaround. We're looking into it.

  8. Behekot commented on Oct 6, 2026

    @Behekot
  9. jorr commented on Oct 14, 2026

    @jorr

    For what's worth this also happens to me now with a Bulgarian number. In the log i get:

    10-14 15:56:42.299 W/PhoneNumberEntryViewMod(xxxxx): [RequestVerificationCode] Third party service error.

    and no amount of resending codes, OR changing the prefix to something else and then back to Bulgaria, seems to work. It also doesnt offer the "Call me instead" option - that stays greyed out.

    Would be very happy to get a resolution on this.

  10. Ishchik commented on Oct 15, 2026

    @Ishchik

    I'm having the same issue with +38099 prefix.
    The logs say [RequestVerificationCode] Third party service error.
    And it doesn't matter if you try with or without a workaround suggested by Mauro
    Also, there is another bug that is relevant to this issue
    Steps to reproduce

    1. Input the phone data (with or without the workaround by Mauro)
    2. Press "Next"
    3. Confirm the number is correct
    4. You get the "We are unable to send the SMS to your number. Please try again in several hours". Press OK
    5. After the dialog closes, press "Next"
      It results in getting you to Verification code screen, where you can request the code again after the timer goes out. But you never have an option to press "Call me instead".

    Signal version - 8.30.3

  11. bodriiRB commented on Oct 29, 2026

    @bodriiRB

    Same bug with +38075 numbers (ThirdPartyServiceError and ProviderRejected)

    I've tried everything: multiple networks, different phones, and even signal-cli. Nothing works.

    This issue also occurs consistently with other Ukrainian mobile operators, including Vodafone, lifecell, and Kyivstar

  12. vladpersonally-cyber commented on Nov 4, 2026

    @vladpersonally-cyber

    Hello Signal Team,

    I am experiencing the same SMS verification issue in Ukraine, but on an iPhone 13 Pro (iOS).

    After restoring my iPhone as a new device, I have been unable to register Signal using either of my two Ukrainian phone numbers.

    I have already tried:

    • Manually entering both phone numbers and selecting Ukraine (+380).
    • Using mobile internet and disabling VPN.
    • Repeated registration attempts over several days.
    • Contacting Signal Support multiple times.

    Unfortunately, SMS verification still does not work, and I cannot access my account.

    Signal Desktop still contains my previous conversations, but sending new messages fails.

    I urgently need Signal for work-related communication.

    Could the Signal team please investigate whether the SMS verification provider is rejecting Ukrainian numbers or whether my registration attempts are being blocked?

    Is there any way to escalate this issue or use an alternative verification method?

    Thank you for your help.

  13. dimonalek commented on Nov 4, 2026

    @dimonalek

    Same issue with +38063311xxxx . Provider rejcts sending sms-code, phone call option inactive.

  14. sanyajr commented on Nov 5, 2026

    @sanyajr

    Та ж проблема з номером+38075 після проходження CAPTCHA вибиває не вдається відправити смс на вказаний номер спробуйте через кілька годин . І так вже не перший день!!!!

  15. sanyajr commented on Nov 5, 2026

    @sanyajr

    Служба підтримки не відповідає і вирішення цієї проблеми я бачу немає!!!!

  16. sanyajr commented on Nov 5, 2026

    @sanyajr

    Тепер така проблема перейшло на введення коду який так і не приходить і кнопка дзвінка не активна !!

    Image
  17. Varro88 commented on Nov 6, 2026

    @Varro88

    Hi Signal Team.
    The same issue as mentioned above for +38050... Both Android and iOS apps. Logs are like:
    [RegistrationSessionManagerImpl:541 serverFailureResponse]: Sending verification code failure from service provider. Permanent:false Reason:provider rejected. Workarounds with manual selecting country code did not help.

    I created request via "Submit a request" on official website, but there is no any feedback for a few weeks.

    Yes, thanks for the extra details @MauroFoti on a workaround. We're looking into it.

    Hi @cody-signal sorry for direct tagging, but for more than month we don't have any feedback from Signal team. Could you please clarify, are there any updates?

  18. dkartartstudio commented on Nov 8, 2026

    @dkartartstudio

    Hello Signal team,

    I am experiencing a registration SMS issue with my Ukrainian Vodafone number (+38050).

    This number was previously registered and working with Signal. About a month ago, I switched from one iPhone to another. I forgot my Signal PIN, and when I tried to register on the new iPhone, the PIN was rejected.

    Since then, Signal has consistently displayed this error:

    “Unable to send SMS to this number.”

    I have already tried:

    • Registering on two different iPhones.
    • Manually selecting Ukraine (+380).
    • Entering the number in the correct international format.
    • Contacting my mobile operator, Vodafone, which confirmed that SMS services are working normally.
    • Testing another Vodafone number, which successfully received a Signal verification code.

    The issue appears to affect my specific phone number rather than my device or the Vodafone network in general.

    I do not need to recover my old messages or chat history. I simply want to register and use Signal again with my existing phone number.

    Could you please investigate whether my number has been blocked or restricted by Signal’s registration system or SMS provider?

    Thank you for your help.

  19. dev-lab commented on Nov 11, 2026

    @dev-lab

    I have the same problem with a Ukrainian Vodafone number (+38050).

    The number is approximately 3 years old, and I am trying to register it with Signal for the first time. SMS reception works normally, and the number is active.

    Signal consistently reports "Unable to send SMS to this number". However, SMS-based verification works without any issues with other services, such as WhatsApp.

    I have attempted to register this phone number with Signal more than 30 times between September and November 2026, using two different Android phones, but without success.

    For comparison, other Vodafone numbers with the same +38050 prefix, registered previously, work perfectly with Signal. The most recent one was registered about a year ago without any issues.

    This looks like a registration provider issue rather than a problem with the mobile operator or number prefix.

  20. dev-lab commented on Nov 11, 2026

    @dev-lab

    UPDATE: I managed to register the number successfully!

    Previously, I entered the number without the leading zero after the country code (+380): 50XXXXXXX. This time, I entered the phone number with the leading zero: 050XXXXXXX, while keeping the country code set to +380.

    Signal displayed the same international number (+38050XXXXXXX) in both cases, but registration worked immediately only when the leading zero was included.

    This suggests a UI/validation bug: Signal accepts both input formats and displays them as the same valid international number, but apparently handles them differently during registration. There is no indication to the user that one format might fail.

    This might be a workaround for other Ukrainian users experiencing the same issue.

  21. dimonalek commented on Nov 11, 2026

    @dimonalek

    UPDATE: I managed to register the number successfully!

    Previously, I entered the number without the leading zero after the country code (+380): 50XXXXXXX. This time, I entered the phone number with the leading zero: 050XXXXXXX, while keeping the country code set to +380.

    Signal displayed the same international number (+38050XXXXXXX) in both cases, but registration worked immediately only when the leading zero was included.

    This suggests a UI/validation bug: Signal accepts both input formats and displays them as the same valid international number, but apparently handles them differently during registration. There is no indication to the user that one format might fail.

    This might be a workaround for other Ukrainian users experiencing the same issue.

    This worked for me flawlessly. Successfully registered 2 previously problematic numbers. There must be some issue with number field parsing.

  22. dkartartstudio commented on Nov 11, 2026

    @dkartartstudio

    Thanks a lot! U helped me! It works! Thank u once more!!!

  23. greyson-signal commented on Nov 11, 2026

    @greyson-signal
    Contributor

    This suggests a UI/validation bug: Signal accepts both input formats and displays them as the same valid international number, but apparently handles them differently during registration.

    Looking at the old registration code (which dates back to ~6 months ago on 8.21), this might have been the case, but it's definitely not the case now. These two numbers are treated identically in the data we send to the server is the same. It's more likely that just for trying a few times probably got you through, and it probably didn't have to do with a leading zero.

  24. dev-lab commented on Nov 11, 2026

    @dev-lab

    This suggests a UI/validation bug: Signal accepts both input formats and displays them as the same valid international number, but apparently handles them differently during registration.

    Looking at the old registration code (which dates back to ~6 months ago on 8.21), this might have been the case, but it's definitely not the case now. These two numbers are treated identically in the data we send to the server is the same. It's more likely that just for trying a few times probably got you through, and it probably didn't have to do with a leading zero.

    I appreciate your investigation, but I find it difficult to attribute this to coincidence.

    I had tried registering this number more than 30 times over approximately two months, on two different Android devices, and every attempt failed with the same error.

    Then I changed just one thing: instead of entering 50XXXXXXX after selecting +380, I entered 050XXXXXXX. Registration succeeded immediately.

    Other users have also reported success with this workaround. Given the repeated failures followed by immediate success after changing the input format, I believe there is a reproducible difference worth investigating, even if both inputs eventually appear as the same E.164 number in the UI.

    I understand that the current Android code may send the same normalized number in both cases, but that alone doesn't rule out differences elsewhere in the registration flow.

  25. greyson-signal commented on Nov 12, 2026

    @greyson-signal
    Contributor

    I understand why you may think this, but this is what I see.

    1. We always normalize the phone number before it's sent to the server. And that normalization strips leading zeros. I even wrote up a unit test with this specific number format to verify it strips the zero.
    2. When we send up the request for the SMS, this normalized number is the only thing that gets sent up. We're not sending up the user input with it. It's just this number, which is the same whether there's a leading zero or not.
    3. There are users on iOS with the same bug, and our codebases are completely separate. Maybe there's something going on over there with this leading zero, I didn't look into it.

    I still think it's more that "trying again" at the time you tried is more likely the reason. These are all server-side decisions, often decided by third party SMS providers, and we don't have a lot of insight as to what's happening with that system.

  26. e0pashko4sky commented on Nov 12, 2026

    @e0pashko4sky

    Same problem with +38095 prefix (Vodafone provider), reason=providerRejected. Tricks with changing inputs (i.e. adding leading zero) don't resolve the issue in my case

  27. bodriiRB commented on Nov 15, 2026

    @bodriiRB

    I just encountered some surprising behavior that might actually provide a workaround for this issue

    Over the past seven months, I've registered Signal on more than a dozen phones, and I've run into this problem almost every single time

    Yesterday, I tried registering Signal on yet another device, fully expecting the usual SMS verification failure. But something unexpected happened: Signal sent the verification code directly to WhatsApp account instead of via SMS

    And that's what confuses me

    Every single time I've attempted to register Signal in the past, I've already had WhatsApp installed and registered with the same phone number. Yet Signal had never offered or used WhatsApp as a verification method before

    This time, for whatever reason, it did. I received the code immediately and successfully completed the registration

    Unfortunately, I also needed to register Signal on a second phone yesterday, and that attempt failed as usual. No SMS, no WhatsApp verification code, nothing

    So my question is: Does anyone know what determines whether Signal sends a verification code via WhatsApp instead of SMS?

    Is there some specific condition, fallback mechanism, or verification provider involved?

    If we could figure out what triggers WhatsApp-based verification, it might provide a reliable workaround for this entire issue

  28. greyson-signal commented on Nov 16, 2026

    @greyson-signal
    Contributor

    @bodriiRB To the best of my knowledge, there is no circumstance where we'd send SMS verification over WhatsApp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions