Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloud Sync on Windows crashes upon fetching any server file other than manifest.server #17474

Open
2 tasks done
JanBaumy opened this issue Jan 26, 2025 · 2 comments
Open
2 tasks done

Comments

@JanBaumy
Copy link

Is there an existing issue for this?

  • This is a bug in RetroArch frontend
  • I have searched the existing issues

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

  1. Synchronize local files from Windows via Cloud Sync to a WebDAV server.
  2. 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).
  3. 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

@KiralyCraft
Copy link
Contributor

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?

@warmenhoven
Copy link
Contributor

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants