-
Notifications
You must be signed in to change notification settings - Fork 1.9k
release-5.8 WatchCommonWatch/WatchCommonWatch.h not found #76
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
Comments
The selected configuration in sub projects are wrong, maybe you should chose a right one by yourself |
Can you be more specific? I double checked, they are almost identical as their release-5.7 counterparts. |
Same problem, is there any one know how to fix this problem ? |
for example, you can chose the "DebugFork" for all projects in the workspace, some sub project don't have this configuration, so, just create a new configuration named like that. only if all projects have same build configuration, then those frameworks can be found in right path |
i'm using the AppStoreLLC scheme and work well. |
By creating a configuration named "DebugFork" in all projects (by duplicating "DebugAppStoreLLC"), the workspace can be built without errors. Thanks @xianhe92 ! |
* Обновил прокси Даль * Обновил конфиги --------- Co-authored-by: Lenar Gilyazov <lenar@tusco.ru>
Uh oh!
There was an error while loading. Please reload this page.
In the
release-5.8
, I'm unable to compile the source, as Xcode claimsWatchCommonWatch/WatchCommonWatch.h
cannot be found when I'm compiling theTelegram-iOS-Fork
's Watch Extension submodule, though the 2 targets in the newly introducedWatchCommon
project can be successfully built.Did I missing something important? I have already changed the entitlements, bundle IDs, and Developer identity as usual.
p.s. I just checked that the structure of
release-5.8
is quite different than the previous ones. Why?p.s. I think this issue list should make good use of the labels (sadly the repo owner didn't reply anything)
The text was updated successfully, but these errors were encountered: