clock stuck?

Sort:
BlindThief
Abhinav0121 wrote:

Looks like a lot of people have been affected from this bug. I don't think there's a fix right now. 

There's another thread discussing the same thing~

https://www.chess.com/forum/view/site-feedback/clock-bug-in-the-app

I found that if you shut down the app and log into the website from your phones browser, you can continue the game there. 

StormCentre3

By logging out you risk being forfeited- as you are abandoning the game while connected. Best to simply swipe the app to close and reopen. The clocks start back up.
It’s impossible to play anymore as the clocks are freezing constantly in every game. We were promised an update by last nite or today- they’ve known about the issue for sometime . Claim the Apple store has been closed. I’ll wait and see. If not in by tomorrow no point in a premium membership.

Think CC would offer iOS users any reimbursement for the troubles ( some of us for weeks)? LOL

mirekpet

This is so frustrating. Lost several winning games on timeout due to this. Please leave App Store ratings as the app is unuseable.

StormCentre3

I’m thinking my original inclinations to be true. The issue is more tied to server capacity than any “bug” in the iOS app. No update as yet in the Apple store- as said would be happening. The clocks freezing issue acts more like a server issue than any bug. A hint was given by the one response made by Staff- how the problem is connected to the over-loaded capacity issues being seen by the site. 

LightningPanda_8

I have the bug too... on a iPad

Da-Vere
BadBishopJones3 wrote:

I’m thinking my original inclinations to be true. The issue is more tied to server capacity than any “bug” in the iOS app. No update as yet in the Apple store- as said would be happening. The clocks freezing issue acts more like a server issue than any bug. A hint was given by the one response made by Staff- how the problem is connected to the over-loaded capacity issues being seen by the site. 

thumbup.png I know nothing about IT stuff. However, gaining over 100k new “ members” daily has to have an affect on cc’s capacity to maintain acceptable service delivery. Imagine a restaurant giving away half their menu for free, it would soon look like the aftermath of a Sunday afternoon potluck! IMHO, there is an argument to be made for not making so much available for free. I understand many will not be able to afford to pay, but there are other ways to enjoy chess. 

StormCentre3

But is it a bug within the app as claimed by staff- or rather app connections given a lower priority when a server reaches maximum capacity? Instead of disconnecting users  - the game simply stops - the clock freezes. Seems a bit peculiar- as closing the app and reopening the app results in the clock resuming and the game continues.

Da-Vere
BadBishopJones3 wrote:

But is it a bug within the app as claimed by staff- or rather app connections given a lower priority when a server reaches maximum capacity? Instead of disconnecting users  - the game simply stops - the clock freezes. Seems a bit peculiar- as closing the app and reopening the app results in the clock resuming and the game continues.

Valid question @BadBishopJones3. I’ll just wait it out, trying to play more daily games now anyway, it’s supposed to be good for me. I hope that CC will make an announcement to all when it is resolved, for clear communication. I’m sure they’re sweating it out too. 

Barnstorm

This is unfortunate I’ve lost several won games. But that’s not unusual for me, but normally it’s my fault not the apps fault.

StormCentre3

For certain - the issue is not simply a “bug” in the iOS App. No update in the Store as promised days ago. Our chains are being yanked. The issue has to do with server capacity. App users find their games stopped by a frozen clock. CC policy is not to comment on their issue, but to leave app users thinking otherwise. An imaginary bug or a connection issue. Fed up here. Cancellation of paid membership.

StormCentre3

Members continue to post new threads about the issue of clocks stopping - losing games.

A single response from Staff- a promised update in the store. Hasn’t happened. The issue is the demands on the servers are at capacity- and app users are the 1st to take a hit. Nothing to do with any “bug.” More likely the latest update insured iOS users to be the 1st to go ! 

StormCentre3
DeepGreene wrote:

Thanks for your patience, all. The fixed version of iOS was submitted to Apple this morning. If they are consistent with their recent turn-around time, we could see it in the Store tonight or tomorrow... They may have a bit of post-holiday-closure backlog though.

(Just as an FYI, this bug was introduced along with some changes we did to reduce back/forth between the app and the Live Chess servers, and thus to reduce demand on the servers themselves. Once we get this wrinkle ironed out, the result should be more performant Live Chess all around.)

So ... where’s the fix ?

There is not one... is there?

shaf8888

Yes, I am

MartynRowe
In recent game clock stuck and opponent didn’t see that I had reclaim my Queen and put them in check. I ended up loosing the game on time fault and opponent kept telling me to play, even though it was his move out of check
dav964

Same issue. Happening often. How to fix? 

StormCentre3

If you play on the iOS app and the clock freezes-

swipe to close the app and reopen - the game continues.

You are not disconnected. If you log out the game is recorded as a loss - due to abandonment.

 

StormCentre3

There is no fix on users end. It is a server issue.

Martin_Stahl
BadBishopJones3 wrote:

There is no fix on users end. It is a server issue.

 

Post 14 said it is an app issue that was caused by code to limit excess traffic to the servers. Thus the need for a new app version.

StormCentre3

Well where is it Martin?

That was stated 3 days ago. Claimed to be available the next day.  No update in Apple.

StormCentre3

The issue is not specific to a bug in the App. But is rather tied into server capacity. Re- Read DeepGreens post. CC is scrambling to fix the problem- which is not a simple bug in the app. Prove me wrong.