You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Cloud Sync functionality on Windows will cause RetroArch to crash entirely upon trying to fetch a file from the server, other than manifest.server (which works fine). The crash does not occur on iOS or tvOS.
Expected behavior
The server file should be fetched and overwrite the local file without crashing the application.
Steps to reproduce the bug
Synchronize local files from Windows via Cloud Sync to a WebDAV server.
Change any file and update the manifest.server file with the new corresponding hash values (for example by updating the save on the iOS version and letting Cloud Sync run).
Start RetroArch on Windows again, causing Cloud Sync to run.
Version/Commit
1.20.0
Bisect Results
No response
Present in the nightly version
No, looks like this is already resolved
Platform & operating system
Windows 10
Affected Cores
No response
Environment information
No response
Relevant log output
The text was updated successfully, but these errors were encountered:
Hello! I tested Cloud Sync with Android sync, and it seemed to perform fine. Would it be possible for you to download a debug version of RetroArch and fetch a backtrace for the crash?
I'll look into it as soon as possible, but time seems a bit scarce for now, unfortunately. Maybe @warmenhoven might be able to take a look?
Yeah this was a known issue after 1.20 got released with not dealing with path separators correctly. It's fixed in the latest nightly (as mentioned in the description above).
Is there an existing issue for this?
Description
The Cloud Sync functionality on Windows will cause RetroArch to crash entirely upon trying to fetch a file from the server, other than manifest.server (which works fine). The crash does not occur on iOS or tvOS.
Expected behavior
The server file should be fetched and overwrite the local file without crashing the application.
Steps to reproduce the bug
Version/Commit
1.20.0
Bisect Results
No response
Present in the nightly version
No, looks like this is already resolved
Platform & operating system
Windows 10
Affected Cores
No response
Environment information
No response
Relevant log output
The text was updated successfully, but these errors were encountered: