FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    "The [user.mobilePhone] property must be a valid phone number that can be parsed to a E.164 formatted value" error

    Scheduled Pinned Locked Moved Unsolved
    Q&A
    1
    1
    640
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mcsymiv
      last edited by

      Hello,

      When submitting text value, e.g. "my phone", to 'user.mobilePhone' to /api/user/registration, we receive E.164 error, which is expected.

      But, I can perfectly create users with following values '123text', 123z'
      Screenshot 2024-05-20 at 14.02.13.png

      And, mobilePhone values like '12z', 12zzzz', yield expected error message - Invalid number
      Screenshot 2024-05-20 at 14.05.04.png

      What are exact formatting rules for user Mobile phone [user.mobilePhone] field? Is this a bug, or FA allows some other phone formats which are not described in the documentation? (https://fusionauth.io/docs/apis/users)

      1 Reply Last reply Reply Quote 0
      • First post
        Last post