fix(spoof): guard atomicWrite errors in updateTo

writeText and Files.move can throw IOException, SecurityException,
or AtomicMoveNotSupportedException. The exception previously
propagated through updateTo into BulletinPoller.fetchAndParse's
broad catch, which mislabelled it as "network_error" in the
history. Wrap atomicWrite, log the real failure, and return
before resetprop so the on-disk file and live props stay
consistent on failure.
This commit is contained in:
Enginex0
2026-05-19 05:10:34 +01:00
parent 4e55ba4e77
commit 864c8841c1
@@ -82,7 +82,12 @@ object PatchLevelManager {
)
return
}
atomicWrite(date)
try {
atomicWrite(date)
} catch (e: Exception) {
SystemLogger.error("PatchLevelManager: atomicWrite failed for $date", e)
return
}
applyToProps(date)
SystemLogger.info("PatchLevelManager: applied patch date $date")
}