When a user deletes its account and tries to sign up with a different email, an access token of previous user is sending to server together with a new https call for sign up.
Even though the data source of sign up doesn't have any https header of authorization.
Then server returns a message of user not found since the token is not active anymore.
This issue is solved only when the user deletes app and download it again.
Same issue goes with preview app too.
Plus, when an access token is expired and a user try to login again, even though its email and password are correct but the expired token is sent to server with a https call for login.
Same as above, the data source of login doesn't use any https headers.
And login is failed since the expired token is sent to server with https call for login.
This issue can be solved only when the user delete app and download it again as well.