“Account Locked”

I am. 🙂This does not help, I already deleted the whole Accounts folder. Sorry for not mentioning it.

Maybe related to this:https://discussions.apple.com/thread/6610852?searchText=outgoingThe option to edit your incoming mail server is grayed out because of the new option in Yosemite to Automatically detect and maintain account settings. Disable that option in the advanced settings of your account in Mail, click back to General settings, and select save settings on the popup that appears. Then you will be able to edit your incoming mail server.

same issues here... when i tried to open it it would freeze my phone and require locking... its so annoying having to go into settings to change things usually in there

One thing is certain: You're forbidden to use StoreKit for that sort of transaction system.11.4Apps that use IAP to purchase credits or other currencies must consume those credits within the App Whether it's allowed to do that sort of thing using PayPal has several component questions, including Is that allowable under PayPal's terms of service? and Do you understand the account restrictions that PayPal imposes? that you need to ask in a PayPal support forum.

Worth a shot :]I've read and/or tried to troubleshoot dozens of iCloud account related issues with 10.11 and yours seems the strangest to me - all others could be explained/resolved without assuming a bug that either doesn't correctly read/decrypt username & password from server or fails to check them against input properly. Bizarre!

From the perspective of a part-tme dev:0) All of the below have been reported by multiple users in this forum...1) With watchOS 2...BETA 2...2) Restarts periodically, BETA 1 was ok.3) Battery drains very quickly, BETA 1 was ok.4) Haptic Feedback is broke, BETA 1 was ok.5) Erratic paring issues during setup, required restart, BETA 1 was ok.6) Several apps don't start, BETA 1 was ok.7) iMessage is erratic, non working most of the time, locked up a couple times when receiving IMessage.I knew what I was getting into, but I am surprised at some of these...Fortuntately I imagine the devs at Apple are experiencing the same, so I bet the next week or two or three will move us in the right direction with improvements.

Looking into it further, I'm afraid it's probably the motherboard. I've read two accounts where that (lesser known) configuration turned out, either by trial and error component replacement or by bringing it into the Apple store, to be the mobo.

Are you in a position where you could store the contacts on a server? If so you could consider having a server which provides a CardDav account which the user could then have the contacts in their Contacts, but you can control the contents server side. That's certainly a non-trivial undertaking but could potentially be one approach if this is a strong enough requirement.

This thread, and the solution to your problem is ALL about static vs dynamic typing and value vs reference semantics.Let's make this really simple and say we have a JSON file in which we have encoded one of the primitive Swift types (Int, Double, UInt8 et al, which are defined in the std lib as structs).How could it (ever) be possible to write a deserializer that would not have to take into account all the different possible types of structs that such a JSON file would be allowed to encode?This is why you would use dynamic typing for such tasks.So this is the last time I repeat this (promise): You are asking for the impossible.Unless you are willing to give into the fact that you need some dynamic typing here, and you can not serialize and deserialize structs as such.

Look in System Preferences -> Internet Accounts -> Google and disable Messages.