-
Notifications
You must be signed in to change notification settings - Fork 53
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
Error message and crashes after applying the Sidecar patch #4
Comments
Question 2:
If you didn't make a backup and already patched... then
Question 1 and Crashing many apps: I know that issue, but I don't have Sidecar-unsupported Mac as I said. So I don't know exactly why it happens, and how to fix it. My assumption is: If SidecarCore isn't signed, occurs issue you said. Could you try Question 2's answer and give me the result? |
Hello back,
Thank you very much for your help - very much appreciated!
I followed your instructions and it worked this time, I am able to connect the iPad with Sidecar, without app crashes.
Turns out, that in Sidecar modus the iPad screen is flickering, especially when changing programs on the Mac, and the view is not sharp in general. Not really usable.
So I think now that there was a real reason, why Apple is not supporting a Late 2103 MacBook Pro - and not only because they just want to make more money by pushing people to buy new machines;))
Or do have an idea how to tackle the flickering?
Kind regards from Switzerland
Mario
Am 27. September 2019 um 19:01:50, Jinwoo Kim (notifications@github.com) schrieb:
Question 2:
Install Command Line Tools: xcode-select --install
Replace /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore to original you backed up.
Run SidecarPatcher again.
If you didn't make a backup and already patched... then
Install Command Line Tools: xcode-select --install
Sign patched SidecarCore: sudo codesign -f -s - /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore
Set permission as 755: sudo chmod 755 /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore
Question 1 and Crashing many apps: I know that issue, but I don't have Sidecar-unsupported Mac as I said. So I don't know exactly why it happens, and how to fix it. My assumption is: If SidecarCore isn't signed, occurs issue you said. Could you try Question 2's answer and give the result?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I have no idea about it. Anyway, thanks for giving the result. |
Same flickering result here on Mid-2014 MacBook Pro with iPad Pro 1st gen, thanks for the patch anyway! 👍 |
@coodoo Does it work on 10.15 official release? |
for me, it works but only in wired mode. |
@pookjw Yes, it worked with the official release (wirelessly), but the screen was flickering so bad that it's barely usable, guess there's indeed a good reason for Apple to disable support for older macs 😅 |
how can we connect with wired mode nothing happening when i connect with wired :( |
Hi,
I just tried to apply the latest SidecarPatcher version on my late 2013 Macbook pro.
Something went wrong, I received an error message. Still, after patching, I was able see the Sidecar symbol in settings, and it also showed my iPad Pro as option, but it did not work, no reaction on the iPad. Instead many other programs crashed, because - according to error log messages - SidecarCore was causing Notes and Airmail to crash.
So I did a rollback.
Now I have two questions:
Marios-Macbook:~ n$ chmod +x /Applications/SidecarPatcher
Marios-Macbook:~ n$ sudo /Applications/SidecarPatcher
Password:
/System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A//SidecarCore: replacing existing signature
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
/System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A//SidecarCore: the codesign_allocate helper tool cannot be found or used
Reboot your macOS.
Thanks in advance for your reply!
Best regards
Mario
The text was updated successfully, but these errors were encountered: