+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: Support & Issues (https://forums.rpcs3.net/forumdisplay.php?fid=17)
+--- Forum: Support (https://forums.rpcs3.net/forumdisplay.php?fid=18)
+--- Thread: Issue with updating RPCS3 (/showthread.php?tid=206831)
Issue with updating RPCS3 - futos - 11-10-2023
Started RPCS3 for the first time in 10 days. Saw this message in the log "E UPDATER: Some information seems unavailable".
I made a POST to https://update.rpcs3.net/?api=v2&c=e26d4e17, I got the JSON below and windows latest build is null.
This is probably what's preventing RPCS3 from updating as the code in github shows:
// Check that every bit of info we need is there
if (!latest[os].isObject() || !latest[os]["download"].isString() || !latest[os]["size"].isDouble() || !latest[os]["checksum"].isString() || !latest["version"].isString() ||
!latest["datetime"].isString() ||
(hash_found && (!current.isObject() || !current["version"].isString() || !current["datetime"].isString())))
{
update_log.error("Some information seems unavailable");
return false;
}
{
"return_code": 1,
"latest_build": {
"pr": 14813,
"datetime": "2023-11-10 16:40:18",
"version": "0.0.29-15723",
"windows": {
"download": null,
"size": null,
"checksum": null
},
"linux": {
"download": "https:\/\/github.com\/RPCS3\/rpcs3-binaries-linux\/releases\/download\/build-8c0debfe650712fd9f8830978b67b2e08d8a7a91\/rpcs3-v0.0.29-15723-8c0debfe_linux64.AppImage",
"size": 92419264,
"checksum": "35B29EBCD0721976907E274FE809B5C4D0657D5DAAFFE1789784E588075A8554"
},
"mac": {
"download": "https:\/\/github.com\/RPCS3\/rpcs3-binaries-mac\/releases\/download\/build-8c0debfe650712fd9f8830978b67b2e08d8a7a91\/rpcs3-v0.0.29-15723-8c0debfe_macos.dmg",
"size": 97155001,
"checksum": "4A9AF342FA416AAD106D387BDB4B9C75AD3C7C558FD85B80C0EB0C14A20C6CC0"
}
},
RE: Issue with updating RPCS3 - Ani - 11-11-2023
Yes, the Windows build wasn't built, so the updater didn't return anything and prompt the update, that's intended. It's available now.
RE: Issue with updating RPCS3 - futos - 11-13-2023
Thank you for replying! Now I know it's a temporary issue and will wait if I see it again