<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[&quot;The [user.mobilePhone] property must be a valid phone number that can be parsed to a E.164 formatted value&quot; error]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">When submitting text value, e.g. "my phone", to 'user.mobilePhone' to /api/user/registration, we receive E.164 error, which is expected.</p>
<p dir="auto">But, I can perfectly create users with following values '123text', 123z'<br />
<img src="/community/forum/assets/uploads/files/1716203007862-screenshot-2024-05-20-at-14.02.13-resized.png" alt="Screenshot 2024-05-20 at 14.02.13.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">And, mobilePhone values like '12z', 12zzzz', yield expected error message - Invalid number<br />
<img src="/community/forum/assets/uploads/files/1716203241548-screenshot-2024-05-20-at-14.05.04-resized.png" alt="Screenshot 2024-05-20 at 14.05.04.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">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? (<a href="https://fusionauth.io/docs/apis/users" rel="nofollow ugc">https://fusionauth.io/docs/apis/users</a>)</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2685/the-user-mobilephone-property-must-be-a-valid-phone-number-that-can-be-parsed-to-a-e-164-formatted-value-error</link><generator>RSS for Node</generator><lastBuildDate>Thu, 10 Sep 2026 15:52:57 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/2685.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 20 May 2024 11:15:39 GMT</pubDate><ttl>60</ttl></channel></rss>