-
Notifications
You must be signed in to change notification settings - Fork 49
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
don't include Frameworks into DTTableViewManager.framework #28
don't include Frameworks into DTTableViewManager.framework #28
Conversation
Current coverage is
|
don't include Frameworks into DTTableViewManager.framework
Yep, it seems like Apple knows about this stuff. Thanks, @etataurov! |
I removed this build setting from all three repos, DTTableViewManager, DTModelStorage and DTCollectionViewManager. Can you try building from master branch and tell me if submission worked? |
@DenHeadless Thanks a lot! I'll try it |
I've only tried DTTableViewManager's master branch, but DTModelStorage was 2.3.0, because there is strict version in DTTableViewManager's Cartfile unfortunately DTTableViewManager.framework in my Carthage/Build/iOS still contains Frameworks directory. Even after clean. Is DTModelStorage 2.3.0 a cause of it? |
It might. Please try building from master again, i added 2.3.1 tag to DTModelStorage, and refer to it in Cartfile. |
Oh, actually it worked, after I removed ModuleCache. My fault. DTModelStorage from master branch doesn't contain Frameworks dir in *.framework. So everything is fine. Thank you! |
Build with DTTableViewManager from master & DTModelStorage = 2.3.1 was accepted by iTunes Connect |
No problem! 🍻 |
Aaaand now DTTableViewManager and DTCollectionViewManager tests are failing, because apparently DTModelStorage has to have this setting turned on. Oh Apple, you are making me sad. I will probably need to reconfigure all CI setup because of this. Possibly related links: CocoaPods/CocoaPods#2894 |
Otherwise iTunes Connect rejects app that embeds DTTableViewManager.framework
I'm using Carthage, but seems like CocoaPods might complain about EMBEDDED_CONTENT_CONTAINS_SWIFT = NO;
There is an ongoing discussion in CocoaPods CocoaPods/CocoaPods#4515