-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Apple rejected build because it links against MapKit and not uses it #3521
Comments
You can build RAC without the MapKit bindings, which is all covered by If you use CocoaPods, you may clone the podspec to exclude the said file, while still pointing to this repo. Apparently we would have to offer these bindings separately if Apple tightens the rules. We cannot workaround it without a new framework target or subspec given how Swift module import works. |
Yep, Regarding the solution, separating MapKit into ReactiveMapKit is definitely a neat approach. Alternatively we could use ianbytchek@ibmbp:dependency$ carthage build reactivecocoa --platform mac
ianbytchek@ibmbp:Mac$ otool -L ReactiveCocoa.framework/ReactiveCocoa
ReactiveCocoa.framework/ReactiveCocoa:
…
@rpath/libswiftIOKit.dylib (compatibility version 1.0.0, current version 802.0.53)
@rpath/libswiftObjectiveC.dylib (compatibility version 1.0.0, current version 802.0.53)
…
ianbytchek@ibmbp:dependency$ RC_SWIFT_FLAGS="-DMAPKIT" carthage build reactivecocoa --platform mac
ianbytchek@ibmbp:Mac$ otool -L ReactiveCocoa.framework/ReactiveCocoa
ReactiveCocoa.framework/ReactiveCocoa:
…
@rpath/libswiftIOKit.dylib (compatibility version 1.0.0, current version 802.0.53)
@rpath/libswiftMapKit.dylib (compatibility version 1.0.0, current version 802.0.53)
@rpath/libswiftObjectiveC.dylib (compatibility version 1.0.0, current version 802.0.53)
… |
I think we would go after this path. Probably subspecs for CocoaPods users. |
Apple spared me, but said punishment is inevitable next time. |
Glad to know. Will push this forward ASAP. |
Turns out the lucky framework is ReactiveCocoa with MapKit extensions, which are available since 2016…☹️
For some reason this issue wasn't flagged before. I explained the situation and waiting for response, but it seems like a legit case – the app doesn't need MapKit and it doesn't need entitlements without users actually needing this functionality. Any easy workarounds?
The text was updated successfully, but these errors were encountered: