Mac OS 15 - Rsync issues

[kleinmaetschke]

Updating with some progress. As of the latest version of Local (Version 9.0.5+6706) and the latest MacOS 15 beta (24A5309e). The app can now show the files needing syncing so rsync issues seem resolved. Now this is the only thing standing in the way:

The error appearing on the site after pulling is:

Warning : require(/Users//Local Sites//app/public/wp-includes/class-wp-token-map.php): Failed to open stream: No such file or directory in /Users//Local Sites//app/public/wp-settings.php on line 110

Fatal error : Uncaught Error: Failed opening required ‘/Users//Local Sites//app/public/wp-includes/class-wp-token-map.php’ (include_path=‘.:/usr/share/php:/www/wp-content/pear’) in /Users//Local Sites//app/public/wp-settings.php:110 Stack trace: #0 /Users//Local Sites//app/public/wp-config.php(116): require_once() #1 /Users//Local Sites//app/public/wp-load.php(50): require_once(‘/Users/…’) #2 /Users//Local Sites//app/public/wp-blog-header.php(13): require_once(‘/Users/…’) #3 /Users//Local Sites//app/public/index.php(17): require(‘/Users/…’) #4 {main} thrown in /Users//Local Sites//app/public/wp-settings.php on line 110

[Nick-B]

We think that the MacOS 15 issues might still be interrupting the pull. After you have an unsuccessful pull could you do the following?

1. Take a full backup of your local site and make sure it’s running.
2. In Local, click “Site Shell”, then run:

wp core download --version=latest --skip-content --force

This should ensure that any missing WP files are restored locally. Then you could then try the pull again.

[kleinmaetschke]

I figured that might be the case. But thought it was worth updating the progress it seems to have made.

Following your instructions makes the local site functional after pull, but it appears the database domain changes are never made. (The local site, once pulled, redirects to the live .com site.)

We’re closer, but looks like there’s still issues.

[nickc]

Thanks, @kleinmaetschke. Could you share Local logs and PHP logs after the failed pull, please?

[kleinmaetschke]

I went to make another pull, today, to get you some fresh logs. But I’m no longer getting an error. Tried on other environments, pulled a fresh one, pulled one I already had setup locally. All returned no errors.

I’m gonna go ahead and say y’all fixed something on the backend. And if you didn’t, lie to me and take the credit anyways!

I think this one can be marked a “Solved” now.

[Nick-B]

Thank you for all of your patience with us @kleinmaetschke!