Error in player game archive

Probably not an API error but translates through to incorrect status for player in games archive.

@risinghelios-inactive (renamed account)

Shown as FPV in web page profile header, Games archive shows 'Account closed'. Wrong flag when renamed.

API match results show status as 'closed'

Example https://api.chess.com/pub/match/1564193

Bug report submitted 9th Oct.

Three days gone. No response to bug report. Archive flag still wrong.

5 days. No contact from support. Error still there.

what was the error and ill contact support, im learning networking and ethical hacking

plus, where is the developers support contact

6 days. Still waiting.

do u see my comments?

I did. Did you read the OP? I have alreay submitted a bug report. As shown above,

yes. and if they fix it, then good for you.

sorry for wasting 9 hours i had to get vaccination cuz of my high fever and extreme sore throat that did not let me eat for 3 days since i got the fever

here's a message from chatgpt,

It seems that you're dealing with an API issue related to the player game archive on Chess.com. From the image, the error appears to stem from renamed accounts being incorrectly shown as "Account closed" in the game archive, and the API match results also incorrectly show the status as "closed."

If you're familiar with the Chess.com API, you could troubleshoot by:

1. **Verify the API Response**: Check the API response for renamed accounts. You can do this by making an API call to the same endpoint you shared in the forum post (`/pub/match/1564193`) and verifying if the status code and data reflect the correct information.

2. **Check Documentation**: Ensure that the response you’re expecting aligns with the latest version of the Chess.com API. Sometimes endpoints or returned data formats change with updates.

3. **Handling Renamed Accounts**: It seems the issue arises specifically with renamed accounts. If the API returns renamed accounts as "closed," you might need to create a logic check to differentiate between truly closed accounts and renamed ones, perhaps by cross-referencing the player’s account details.

If you don't have access to Chess.com's backend but are a player encountering this issue, you may want to follow up with Chess.com support or developer forums again to get their attention, especially if it's been more than 5 days since you last reported the bug.

Let me know if you'd like help with any specific steps or if you want to analyze API responses further!

at 10:00PM Cairo Time, i will get another vaccination. which means im unavaliable

for tomorrow*

Day 7. Nothing

Day 9. No change. No response.

day 10. Nothing changed

https://api.chess.com/pub/player/risinghelios-inactive still shows status as 'closed'

2nd bug reported submitted.

Day 12. It's changed. Sadly it's still wrong. The games archive icon now shows 'self closed' despite popup still showing 'Account closed' and the account profile header still showing 'FPV'.

Day 13 still wrong. No response from support.

Day 14.

Day 18. Still wrong. Still no response. 3rd bug report sent.