Magento_Sales module fails to upgrade (email has a wrong format)

[gtlt]

Preconditions

1. Magento 2.2.3
2. PHP 7.1.16
3. MariaDB 10.2.9

Steps to reproduce

1. composer update 2.2.3 to 2.2.4
2. upgrade Magento_Sales data: current version - 2.0.7, required version - 2.0.9

Expected result

1. update ok

Actual result

1. upgrade logs :
   Module 'Magento_Sales':
   Upgrading data.. We can't save the address:
   Email has a wrong format

In which table should I fix emails ? I have email Null values with the following request

SELECT * FROM `sales_order_address` where email is NULL
SELECT * FROM `sales_order_address` where email is null
SELECT * FROM `quote_address` where email is null ORDER BY `created_at` DESC

[gtlt]

It was related to null entry email in sales_order_address.
resolved by

update `sales_order_address` SET email = 'foo@foo.com' where email is null;

[webspeaks]

But why do we have this issue while upgrading to 2.2.4.
In my case all rows in sales_order_address table have null value in email column. Is the email column newly added in the upgrade?
Setting dummy email to the record doesn't seem correct.
What is the correct way?
@magento-engcom-team

[KM-HM]

I was affected by this issue too.

Solution from gtlt resolved this issue. But I also agree with @webspeaks, setting a dummy email address should not be the correct solution.

[kabadabra]

I am also affected by this issue:

Module 'Magento_Sales':
Upgrading data.. We can't save the address:
Email has a wrong format

Updating sales_order_address and quote_address with a fake email has not worked for me. Anyone else have another solution to get passed this? Other tables that might need to be checked/email faked as well?

[kamranmalikawan]

Any update on that i am facing same issue

Module 'Magento_Sales':
Upgrading data.. We can't save the address:
Address type doesn't match required options

Thanks,

[kamranmalikawan]

@kabadabra have you find any solution ??

[ComputerNorth]

I was affected by this issue too. Solution from gtlt resolved this issue. But I also agree that setting a dummy email address should not be the correct solution.

[hanego]

Based on gtlt solution, still not perfect but this query works too:
update sales_order_address a left join customer_entity b on a.customer_id = b.entity_id set a.email = b.email where a.email is null

[Schoeny1]

@gtlt solution worked for me too. Just make sure you
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf generated/code/*
Before running the magento setup:upgrade again

[niners52]

After I fix the emails I get this error- Missing required argument $options of Magento\Eav\Model\Entity\Attribute\Source\Config. https://imgur.com/a/SqhERi1 It happens on the exact same step. Anyone else getting this?

[kabadabra]

@kamranmalikawan
The solution from @gtlt worked for me, but it did not work at first. We are running Magento 2 Commerce and got their support to help me with a solution. Here is what I ended up doing:

1. I ran the following sql to help indentify which emails were incorrectly formatted on the table "sales_order_address":

SELECT * FROM `sales_order_address` WHERE `email` NOT REGEXP '^[^@]+@[^@]+\.[^@]{2,}$';

2. Similar to the above, I also checked the "quote_address" table just in case too:

SELECT * FROM `quote_address` WHERE `email` NOT REGEXP '^[^@]+@[^@]+\.[^@]{2,}$';

1. and 2. above I had a handful of emails that were not email addresses at all and fixed these up. Having already done @gtlt solution on NULL values, I had already replaced my NULL emails with noemail@foo.com. It should work with a NULL value if all rows are correct, but I can't be 100% sure. For me having a dummy email is ok.

2. I ran the following sql to make sure all my NULL values had dummy emails

UPDATE `sales_order_address` SET `email` = 'noemail@foo.com' WHERE `email` IS NULL

4. I had two emails which 1. and 2. didnt pick up with a <script> tag in it that might have been injected somewhere in Magento 1 days. I fixed these up as well.

After the above, everything upgraded and deployed smoothly. In short, just make sure all the data in the email column are valid email addresses. Hope this helps!