TF-3278 Mobile handle corner cases of TWP redirection

[dab246]

Issue

#3278

Deep Links Config

• Uri format: twakemail.mobile://openApp?access_token=abc&refresh_token=acb123&id_token=abc&expires_in=36000&[email protected]

Resolved

user signed in SignUp page
user want to open tmail app from SignUp page
but tmail app was not installed 
open tmail store

usecase1.webm

user signed in SignUp page
user want to open tmail app from SignUp page
but tmail app was installed but not signed in
sign in app automatically

usecase2.webm

usecase2.mp4

user signed in SignUp page
user want to open tmail app from SignUp page
and tmail app was installed but signed in other account
notice user about it

• Android App terminated:

usecase3.webm

• Android App foreground:

usecase5.webm

• Android App with open composer:

usecase6.webm

• iOS

usecase3.mp4

user signed in SignUp page
user want to open tmail app from SignUp page
and tmail app was installed but signed in with the same account
open tmail app as normal

usecase4.webm

usecase4.mp4

[github-actions]

This PR has been deployed to https://linagora.github.io/tmail-flutter/3283.

[dab246]

• Work well on stg.lin-saas.com

demo-1.webm

demo-2.online-video-cutter.com.mp4

[dab246]

Propose

We are now using a different authentication method than the old flow before. That is, parsUri itself from the redirect url returned from TW. So we need some parameters that are required to be flexible in developing many TWs.

• access_token: MUST HAVE
• refresh_token, id_token, expires_in: Optional
• username: MUST HAVE
• registration_url: MUST HAVE
• jmap_url: MUST HAVE

E.g:

twakemail.mobile://openApp?access_token=abc&refresh_token=acb123&id_token=abc&expires_in=36000&[email protected]&registration_url=https://sign-up.example.com&jmap_url=https://jmap.example.com

@hoangdat

[dab246]

Propose

We are now using a different authentication method than the old flow before. That is, parsUri itself from the redirect url returned from TW. So we need some parameters that are required to be flexible in developing many TWs.

• access_token: MUST HAVE
• refresh_token, id_token, expires_in: Optional
• username: MUST HAVE
• registration_url: MUST HAVE
• jmap_url: MUST HAVE

E.g:

twakemail.mobile://openApp?access_token=abc&refresh_token=acb123&id_token=abc&expires_in=36000&[email protected]&registration_url=https://sign-up.example.com&jmap_url=https://jmap.example.com

@hoangdat

Has been processed