Forum

On the Web interface Archive, the Elo ratings displayed are from the end of the Game when played. But the Android app Archive displays the current ELO ratings of players and NOT the Elo ratings from when the Game was played. Web Interface: Android App:Also, when a previous Game is loaded in the Android app, the Elo ratings for both players are CURRENT Elo ratings and not the Elo ratings from the end of the Game when played.I submitted a Feedback Report regarding this back in May 2021 and also posted in a Forum. Games archive and Rating history - inconsistency? - Chess Forums - Chess.comIs this something that can be fixed?

I have platinum but i can't choose my flair, and it's showing the mod flairs too.... ?????

Title - it keeps bugging and flashing

Hi, I just noticed a new theme came out and it's called 'Sports, American Football' and it looks great, I hope to see more themes and the ultimate customizable theme. Android app does not have the board for this new theme in the list of the custom boards but it does have the pieces, so it looks like a bug. Would you guys please review this? Also, is this new theme here to stay or is it like a special theme that I see every now and then and will be removed? Derrick

I wish we could choose the amount of time left in a game when the app sends a notification. it seems to be about 6 hours which I find way too much. i'd like it to be 1 or 2 hours.

Just what it says in the subject line, I am hoping somebody already reported this, it's been like that for several days now.

And web version of forum so u can customize text on mobile

Just what the subject line says

Whenever I select the last game I played from my list of Completed Games on Android, my pieces (KingMoored), are displayed at the top of the board and my opponents pieces are displayed at the bottom of the board. Also, when I step through the moves, all captures are being credited to the wrong player. Notice the move white pawn on c4 captures black pawn on d5 (5. cxd5 ). The black pawn is credited to my opponent playing black?! Both these bugs do not occur when I look at my game directly after playing a game, nor do they occur when displayed in Game Review and Analysis. I can temporarily fix both these bugs if I go into my Android Device Settings and Clear the Chess.com Application Data, however these bugs do often reappear again for no repeatable reason. (I sometimes think the problem is the result of switching between Web Viewing Games and Android Viewing of Games, but I am not sure). I have reported this bug to support, but was told the problem is the result of En Passant.

When you go to game review and click the start button, the notation portion of the screen starts auto-scrolling, not sure if this is intentional or just a glitch.

I got a 50 point benchmark, but when I hit next, the 50 points disappeared.

When you open up the year in chess, at the top right corner, there's a X, and when you tap it, it brings you to the chess.com website in the app.

Suggestion for landscape mode: allow for the option of minimizing or eliminating notation so we can have a bigger view of the board.

Whenever i am playing a live game and move to another app with chess.com open in the background, my game auto resigns. Is this a bug or a feature?

When I analyze a chess game on the chess.com app, it shows different results than when I use the website. For example, on the app it said I had 69% accuracy in a game, but in the website it said I had 74% accuracy in the same game. Why is this?

This seems to happen randomly and I can't find any particular pattern in when it occurs, but after solving a lot of puzzles in a row, it becomes more and more frequent until you restart the app. OS version: Android 13 Device: Samsung Galaxy s21 App version: 4.5.18 (beta tester) In this first screenshot notice the black knight is obviously not centered on the square. (Took this screenshot after the computer made the next move, but it was like this the second I let go of the black knight) Now you might look at this and think that's all, but the real bug is this: The knight isn't on that square! Refer to the following screenshot showing the legal knight moves. The knight is d3 but it is showing the knight on f3. Please let me know if there is anything else I can do to help. I know how annoying it is to test mobile bugs

I just advanced to stone 3 after solving and extra hard puzzle on a streak. I was sitting somewhere around 60 points left to advance when suddenly I was awarded the advancement. I'm still 39 points away from the advancement in this screenshot. I don't think it's simply a UI glitch because I was at around 60 points and doing the math for solving that on a streak with speed bonus it doesn't add up. Maybe there was some hidden bonus that didn't get applied before this screen popped up. I'm not sure. While this bug doesn't impact your ability to solve puzzles or use the app, I stll want to bring it to the attention of the devs.

Whenever i try to read a message in the chess.com android app, the text comes up in the same color as the background (black bg).

The android app lacks very important features: You have practically no information about the game: there is no "info" tab, no link to the tournament the game is part of. The "analysis" function does not allow to save the variations you may want to study, especially in "daily" games. This is even more annoying as the "mobile view" of the corresponding web page is also very ill designed , 1/3 of the screen is filled with useless space but you can hardly see one line of the analysis. This could and would be organized much better. The Lichess app is ten times better than Chess.com in this regard. I'll add screenshots later (which is also impossible in the android app).

On the Android mobile app, in Settings > Board > Magnified Pieces I can Turn ON/OFF the Magnified Pieces for Live Play, Analysis, Practice Drills, and Learning Exercises. But the Game Review Retry Move ignores this setting and always displays the Magnified Pieces ON.I submitted an app Feedback Report in Nov 2022 and was told the Developers were aware of this bug. This seems like an easy fix, would it do any harm/good if I resubmitting a Feedback Report for this bug again?