IOS app doesn't work fix it !

I agree with nwo009. Chess is very addictive. It's nice to have a rehabilitation day or two I suppose. 😀 Thanks for Vicountvonjames suggestions 😀

I had a problem with my ipad for about a week, IOS 10.3.2, but it works fine now. I go to the internet and log in to chess.com. I don't go to chess.com thru the app anymore.



Would like some answer.
Arguments of paying customers: I have been a paying customer with the diamond from time to time at situations I have time to concentrate in improving my skills. I would sign to pay if that would be told to be needed. Argument of paying customers is on a lame base in my view. As it is, my devices are not working, I certainly won't pay if that isn't told as the reason. An app I might pay (and have paid several years) 100 eur a year doesn't get jammed with support not answering with a feasible reason within a reasonable time frame. Initially didn't see a reason paying 100 eur a year for a game the opponents can repeatedly stall for tens of minutes without capability to contact online support to make them move or end the game. However would be paying reasonable cost for the existing quality if it were required for gameplay.

Is my username not a clue ?

https://www.chess.com/forum/view/general/stuck-on-loading-screen?page=2 erik's post 25:
This is a crazy issue, but here is the explanation:
The reason that some iOS devices are unable to connect to live chess games is because of a limit in 32bit devices which cannot handle gameIDs above 2,147,483,647. So, literally, once we hit more than 2 billion games, older iOS devices fail to interpret that number! This was obviously an unforeseen bug that was nearly impossible to anticipate and we apologize for the frustration. We are currently working on a fix and should have it resolved within 48 hours.
Thanks!
That said, a new update is out and some people say it fixed their issues. The one mentioned in this blog post:
https://www.chess.com/blog/News/chess-com-dev-update-june-9-2017

This should be fixed with the recent update 3.6.14. If you are still having issues, you can PM me. Thank you for your patience!

https://www.chess.com/forum/view/general/stuck-on-loading-screen?page=2 erik's post 25:
This is a crazy issue, but here is the explanation:
The reason that some iOS devices are unable to connect to live chess games is because of a limit in 32bit devices which cannot handle gameIDs above 2,147,483,647. So, literally, once we hit more than 2 billion games, older iOS devices fail to interpret that number! This was obviously an unforeseen bug that was nearly impossible to anticipate and we apologize for the frustration. We are currently working on a fix and should have it resolved within 48 hours.
Thanks!
That said, a new update is out and some people say it fixed their issues. The one mentioned in this blog post:
https://www.chess.com/blog/News/chess-com-dev-update-june-9-2017
It has nothing to do with the fact that the failing app runs on 32 bit devices. 32 bit devices can handle "gameIDs" of any size. It's the app that couldn't handle it, and that's a design issue. I suspect that the Apple developer declared his gameID as an int, and then just compiled the same source code for 32 and 64 bit machines. The problem is that an int compiles into an integer that is sized according to the architecture the compiler is running on. For a 32 bit device, it would be a (signed) 32 bit integer with a maximum value of 2,147,483,647. For a 64 bit device, it would be a (signed) 64 bit integer with a maximum value of something in the quintillions, I think. We will have colonized the galaxy (or gone extinct) before chess.com hits a quintillion games.
The developer should have declared the gameID as int64_t (or the equivalent in whatever language he's using). This would have compiled into a 64 bit number regardless of the device it was running on. Even an 8 bit device (Commodore 64, for example) can handle a 64 bit number if the compiler does its job properly.