You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reprovision informs that it isn't possible to signin wth incorrect infomation and the AppleID is locked for security reasons, even though it is not in either case
#34
Open
bebongchoi opened this issue
Nov 6, 2023
· 1 comment
Describe the bug
I type in my Apple ID and my password. For the first 7 (or somewhere under ten) attempts, I was told by Reprovision that I had put in incorrect information, even though I made doubly sure that I did not, i.e. signing in appleid.apple.com and in iPhone Settings with the same username and password copied from plain text successfully, but not for Reprovision.
After that, I was told by Reprovision that "This Apple ID has been locked for security reasons... etc (-20209)". Despite such message, I could still login my Apple ID from my browser and my phone just fine. I even changed my password multiple times, and Reprovision still told me that this Apple ID has been locked.
To Reproduce
Steps to reproduce the behavior:
Open a newly installed Reprovision Reborn
Type in Apple ID account information accurately
Click "Confirm" button to the top left
Repeat this process multiple times if the signin fails
Expected behavior
Successfully signing in Reprovision Reborn with the Apple ID given
Screenshots
(It is nothing but the usual messages when failing signin normally I suppose)
Device (please complete the following information):
iOS 12.5.7
iPhone 6 Plus
Additional context
This happens with both Reprovision Reborn version on https://repo.satoh.dev repo (version 0.8.5.1~release) and https://havoc.app repo (0.8.4 ~release)
The phone was jailbroken by Chimera, Reprovision Reborn was installed by Sileo from either repo. I used the Havoc version first, failing signin multiple times until finally was told the AppleID is locked. I changed password and tried again, still locked on Reprovision. Then I uninstalled it, installed the version from the dev's repo, and upon the first signin, I was told the AppleID is locked, despite the fact that of course, it is not
Edit: Oh right, I found this file called ReProvisionDebug.txt under /User/Documents
Describe the bug
I type in my Apple ID and my password. For the first 7 (or somewhere under ten) attempts, I was told by Reprovision that I had put in incorrect information, even though I made doubly sure that I did not, i.e. signing in appleid.apple.com and in iPhone Settings with the same username and password copied from plain text successfully, but not for Reprovision.
After that, I was told by Reprovision that "This Apple ID has been locked for security reasons... etc (-20209)". Despite such message, I could still login my Apple ID from my browser and my phone just fine. I even changed my password multiple times, and Reprovision still told me that this Apple ID has been locked.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Successfully signing in Reprovision Reborn with the Apple ID given
Screenshots
(It is nothing but the usual messages when failing signin normally I suppose)
Device (please complete the following information):
Additional context
This happens with both Reprovision Reborn version on https://repo.satoh.dev repo (version 0.8.5.1~release) and https://havoc.app repo (0.8.4 ~release)
The phone was jailbroken by Chimera, Reprovision Reborn was installed by Sileo from either repo. I used the Havoc version first, failing signin multiple times until finally was told the AppleID is locked. I changed password and tried again, still locked on Reprovision. Then I uninstalled it, installed the version from the dev's repo, and upon the first signin, I was told the AppleID is locked, despite the fact that of course, it is not
Edit: Oh right, I found this file called ReProvisionDebug.txt under /User/Documents
ReProvisionDebug.txt
I don't really know, I hope that it helps
The text was updated successfully, but these errors were encountered: