Menu
A framework ( . framework): is a hierarchical directory that encapsulates a dynamic library, header files, and resources, such as storyboards, image files, and localized strings, into a single package. Apps using frameworks need to embed the framework in the app's bundle.
I get rid of these by finding the target(s) that generated the error, then removing/deleting the (odd) path in the "Framework Search Paths" build setting:
What solves this for me is to create a new scheme. Click on Product-> Scheme -> New Scheme and just hit OK. Then my app seems to build and run.
After much digging, I found this is actually related to my test target of my app.
The Fix
If you select your project, and look under ‘Targets’, you should see two targets. One is your app and the other one is your test. Under ‘Search Paths’ (in my test target), I found it was including two items under ‘Framework Search Paths’:
$(SDKROOT)/Developer/Library/Frameworks $(inherited)
Deleting those entries in my older project then removed the warning. I did not have to make any changes to the other target.
Instead of deleting Framework Searh Paths (It causes other problems specially if you're using Fabric framework), you can change this line :
$(SDKROOT)/Developer/Library/Frameworks
with
$(SDKROOT)/Developer/Library/PrivateFrameworks
and it should work.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With