-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
[Questions] How can I resolve this "framework 'Preferences' not found" error during linking libcolorpicker when building with theos? #1580
Comments
Use the code from the |
Thank you! That worked, unsure if I can post a follow up error here, its most likely unrelated:
|
@fenwulf I have the same issue. Have you found a solution? |
Not yet. Unfortunately not super familiar with theos but I refuse to build with GitHub for some reason :) |
I suggest using iOS 16.5 SDK. |
I am using that (the recommended) SDK. |
Have you read the FAQ?
Is there an existing issue/question for this?
Do you think this is a bug?
❌ No, I don't think this is a bug. I will explain below
My question
Disclaimer: I did not read the FAQ, as when I click it I get this popup:
I did search for the error, and did not find the issue in open issues, and searched several closed ones as well. I found it in a closed issue, however it was resolved with a commit.
I have a feeling I am doing something wrong, although I have installed all required packages for building with theos. I am following method 2 on this page. I have placed the sdk within
theos/sdks
. I even double checked that something was in~/theos/sdks/iPhoneOS16.5.sdk/System/Library/PrivateFrameworks/Preferences.framework
. I have actually revisited this over the course of 2-3 months hoping a commit would fix it for me. I am just lost as to what I am doing wrong. I am using (from the linked patched ipa onedrive within this repo) YouTube 19.34.2.I have followed the steps exactly. Here is my error, I can post the entire log if necessary but figured this is the important snippet:
Any help is welcome, thanks!
Additional context
No response
The text was updated successfully, but these errors were encountered: