Post marked as solved
Click to stop watching this thread.
You have stopped watching this post. Click to start watching again.
contentPostList.repliessolved.tooltip
what is more secure, sending the email / name (depending on the scopes) everytime we request it , or asking the users to "securely cache the credentials" which will leave breadcrumbs of the users identity somehow/somewhere (DB, keychain, some other store...) which probably could be accessable by other applications ?Or if something goes wrong downstream, we would have the customers complaining and support will tell them to go into AppleId website to revoke the permission, so they can properly register again. I believe this will be a poor experience and will make people not using this login mechanism if they start having this sort of problems.Probably on places with good internet this wont be much of a problem, but our app is used on places with low coverage (3G even) and network calls do fail quite often, so the register flow could fail once or twice, and it could lead to problems