Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
CocoaPods, Reachability, and use_frameworks! #95
With CocoaPods 0.36, they added the capability to generate frameworks for pods. For Swift projects, using frameworks eliminates the need for a Objective-C bridge.
Reachability works great as a Framework, however when submitting the app to Apple, Apple incorrectly identifies Reachability as being a private API (it looks like there is a private API class called Reachability), which causes the app to be rejected.
None of the other Pods in my project caused this issue.
I was able to work around the issue by removing the
I'm not sure what the solution would be, but it sounds like there is a collision occurring with Apple's private frameworks due to the naming of your project.
Why not just TMReachability? We'll know it's still Reachability under the
On Mon, Apr 20, 2015 at 11:09 AM, Tony Million firstname.lastname@example.org
referenced this issue
May 1, 2015
@cpatterson I forked and use this regularly to get my app into the app-store. It might be a few fixes behind. I was planning on bringing it up-to-date soon™ (if needed): https://github.com/albertbori/Reachability
@tonymillion I recommend renaming the items in question to
I'm struggling a bit with this. I renamed Reachability's files and classes and successfully submitted to Apple but after a