broken procedure that generates a key during setup

[tomholub]

Ok, so there are three issues when creating a key during setup:

• missing / unclear details of that error message. It should be showing clearly the URL and http code like other API errors do. This will need an appium test as well. The Attester mock will be set to return a 400 on submission with some error message, and the above modal must show that error message (we had a mechanism for this that was supposed to work across modals)
• the fact that there is an error submitting to attester
• when there isn't above error, key not stored as backup anyway, tracked separately at consumer setup - the key is not backed up to inbox when creating new key #1304

Originally posted by @tomholub in #484 (comment)

[Kharchevskyi]

First issue I faced now is that call to MailServiceProviderFactory.services executes not on main thread both for gmail and imap

Which cause issue with Main thread checker

@sosnovsky probably would need assist with this issue.
Will fill a separate issue for that

[Kharchevskyi]

looks like call to attester returns 409 status code

[URLSession] URLSession.call status:409 ms:175 PUT https://flowcrypt.com/attester/pub/anton_flowcrypt........, headers: [:]

just wondering should it be post instead?

if yes, what token to use here for imap?

[github-actions]

There were 1 email addresses found in the above comment. Please:

1. Click three dots -> edit to remove the email addresses.
2. Click edited in the comment header, and click on the previous revision of the comment.
3. When viewing the old revision with an email in it, click options -> delete this revision from history.

[tomholub]

Make it a POST, and add id_token to the authorization header.

[Kharchevskyi]

@tomholub this is for outlook authentication.
Mailcore uses SASL way of authentication

[tomholub]

On that case, we need to use a PUT for IMAP. But we have to add a modal with retry/skip option.

[Kharchevskyi]

@tomholub do we still need to do smth in scope of this issue after #1311 merged?

[tomholub]

@fcvakintos does it behave as expected for you now? If yes, you can close this.