Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add cocoapods' static_framework support #92

Closed
1 task
toby1991 opened this issue Mar 21, 2019 · 1 comment
Closed
1 task

Add cocoapods' static_framework support #92

toby1991 opened this issue Mar 21, 2019 · 1 comment

Comments

@toby1991
Copy link

馃殌 Feature Requests

add cocoapods' static_framework support
CocoaPods/CocoaPods#6811

Contextualize the feature

We must add use_frameworks! at Podfile, but after add these configurations, will cause many problems such as below:

error: exportArchive: permission_handler.framework does not support provisioning profiles.

Error Domain=IDEProvisioningErrorDomain Code=10 "permission_handler.framework does not support provisioning profiles." UserInfo={NSLocalizedDescription=permission_handler.framework does not support provisioning profiles., NSLocalizedRecoverySuggestion=permission_handler.framework does not support provisioning profiles, but provisioning profile match AdHoc com.xxx.app has been manually specified. Remove this item from the "provisioningProfiles" dictionary in your Export Options property list.}

and that will cause the Archive success but Sign failed error.

Describe the feature

CocoaPods version 1.3.1 and earlier do not support static framework
dependencies.CocoaPods 1.4.0 adds thestatic_framework option in #6811 that enables you
to specify building a pod as a static_framework, which unlike dynamic frameworks, can have static framework dependencies.

add s.static_framework = true to .podspec

Platforms affected (mark all that apply)

  • 馃摫 iOS
@mvanbeusekom
Copy link
Member

@toby1991 we just published version 3.0.1 of the Permission Handler plugin which implemented this feature. Thank you for you suggestion and clear explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants