-
Notifications
You must be signed in to change notification settings - Fork 4
Won't be able to submit to AppStore #1
Comments
I have been able to verify applications that include frameworks and target earlier versions of iOS using Xcode and iTMSTransporter. IIRC, early versions of Xcode 6 had several issues with verifying and uploading applications that included frameworks. The stack overflow post you refer to is from that time period, so it is possible the author was stimulating those issues. |
Also keep in mind, from the README: "Publically, dynamic frameworks are only supported on iOS 8 and later. " That is still the case. Apple has expanded some of the documentation regarding the use of |
None of the errors or warnings in the message you have posted have anything to do with weak linking frameworks, so I'm not sure how I can help here. The first and second messages in your screenshot are IIRC particular to a pre-release version of Xcode. Pre-release versions of Xcode should not be used for iTC submissions. I'm also not sure why you are submitting this sample project to iTC as your own? |
@quellish Can you confirm that an application has been successfully released on the App Store using this method, with iOS 7 frameworks? Apologies if I missed the confirmation. |
Hi quellish,
Thanks for sharing what looks like a potentially great solution to the problem of dynamic frameworks on iOS 7.
I'm unsure whether you've seen or you're subscribed to the stackoverflow thread below but apparently if you use this approach you WON'T be able to submit your application to iTunes Connect / the AppStore.
You'll get errors for the Minimum Required Version:
Please see here for more information and discussion...
http://stackoverflow.com/questions/25909870/xcode-6-and-embedded-frameworks-only-supported-in-ios8/25910262#25910262
Please note I haven't personally experienced this, I'm just passing on the information. If this is the case then at the very least I would suggest you update your README including this vital information.
HTH
The text was updated successfully, but these errors were encountered: