Hello everyone, yesterday I saw the update to my APP rejected because when a new user registers through the “Sign-In With Apple” component, I would later ask for a password to be added.
Apple told me that this is not good and it does not respect the guidelines.
So I modified the current workflow by eliminating the password request thinking that the component was going to add the same password as the Apple ID in my PASSWORD field.
But I found out that’s not the case.
In practice, a new user is created in the database, but the password field is EMPTY, and does not have the usual [HIDDEN] inside.
In fact, after registering if I log in with Mail and password (Id Apple) he replies that it is not good because the password is wrong.
I need to save the user’s password because the user in the app can change it or to access some private settings the password is required.
In doing so, the component is useless for me, as it does not save an essential data.
Am I wrong something? Or is it normal that you do not save the PASSWORD in the database and leave the field blank?
I am attaching a screen where there is the white field for the user registered by “Sign-in with apple” and the second from normal registration.