Skip to content

ChessComGames.py - only pulls game records from "daily_games" table #960

Description

@mohara-1

ALEAPP Version = 2026.1.0
Android Version = 16
Build Number = BD6A.251031.001.A4
Device Info = Google Pixel 10a
Additional Notes = Device rooted with Magisk
Data Collection Method = collected com.chess to a tar.gz file and then used adb pull to collect file for ALEAPP use. I did upzip that and rework the folder structure so that com.chess would be under a folder named data and then rezipped. Otherwise the regex search was not seeing the session preferences file.
Module with issue = ChessComGames.py
App = Chess.com app
App Version = v4.10.2-googleplay-268270

Issue: The module is currently only set up to check the "daily_games" table and not also the "bot_games", "coach_games", or "live_games" tables.

Testing: In testing, I played 19 games. This was a mix of rapid, daily, bot, coach, offline, and tournament games. Currently and from what I can tell, the ChessComGames.py module only collects data from the "daily_games" table. Daily games are games where you have 24 hours to make a move. Other game types have various time constraints. You can also play a "coach" (bot) or just play one of the computer profiles. Just from my own use of the app, its probably much more common that you would see bullet/blitz/rapid games vs. daily games because of the 24 hour time limit for moves. For this reason, I would mostly expect the daily_games table to not have a lot of activity on user devices. The one daily game I played was the only game that appeared in the ALEAPP report and not the others. ALEAPP did successfully find the files necessary for processing:

Image

In looking at the database itself, I was able to account for 17 of the 19 games by referencing the "daily_games", "bot_games", "coach_games", and "live_games" tables. I could not find the offline game in the database and oddly, the first game I played online was also not listed in the live_games table where it should have been but I'm not sure what was the reason for that was. It was a very short game due to resignation so they may not have listed it in the table but I can't confirm the exact reason. The "tournament_games" table did not contain any useful data that I could see related to the test games that were played.

Recommendation: Have module also check the "bot_games", "coach_games", or "live games" tables to provide a more complete record of the game history vs. just games where only a "daily" game type is played.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions