"Could Not Sign In" Error Message on iOS 8

[skylitmus]

I'm using the GM version of iOS 8 since the day it's available to the developers and everything is working fine until this morning. When I tried to make a download or purchase on the app store, I received this error message.

This error only happens on my iPhone but not on my iPad. Is anyone else having the same problem?

 

[bobhammer]

same here

 

[zemaker]

I am also having this error, never had it before...not even on the iOS 8 betas.

 

[skylitmus]

So i'm not alone.

Initially I thought the app store was having some issue, but apparently that this problem only occurred on my iPhone and not two other iPads that I have.

 

[snowcrash]

Was fine all day (on GM since release) but all the sudden about 10 mins ago went to download something and got this same error. Downloaded things fine earlier.

 

[zemaker]

I fixed it by going to Settings > iTunes & App Store > Apple ID > View Apple ID > Payment Information > here I changed the CC Security Code and this fixed it as this required me to login into my account and at this point I was able to go back into the store and download things without having to re-enter my password.

 

[snowcrash]

I fixed it by going to Settings > iTunes & App Store > Apple ID > View Apple ID > Payment Information > here I changed the CC Secyrity Code and this fixed it as this required me to login into my account and at this point I was able to go back into the store and download things without having to re-enter my password.

Worked! Thanks!!

 

[skylitmus]

I fixed it by going to Settings > iTunes & App Store > Apple ID > View Apple ID > Payment Information > here I changed the CC Security Code and this fixed it as this required me to login into my account and at this point I was able to go back into the store and download things without having to re-enter my password.

It works~!! Thanks for the help.

 

[JoeTomasone]

Just took a while for me and it cleared up all on its own.

 

[dcorban]

Just took a while for me and it cleared up all on its own.

Same. It was probably just a server error.