3 ms·

This is how to use this on iPhone - https://gist.github.com/xuki/f66e4d77b682dbb0960d https://gist.github.com/xuki/f66e4d77b682dbb0960d This won't pass Apple's

by xuki 12y ago

This is how to use this on iPhone - https://gist.github.com/xuki/f66e4d77b682dbb0960d https://gist.github.com/xuki/f66e4d77b682dbb0960d This won't pass Apple's automatic check for private API, but you could do some clever swizzle. IMO it's ok to use this in production (if you can get pass the app review), Apple is using them in their app anyway.

k-mcgrady 12y ago
>> "This won't pass Apple's automatic check for private API, but you could do some clever swizzle. IMO it's ok to use this in production (if you can get pass the app review), Apple is using them in their app anyway" Private API's shouldn't be used in production. When Apple changes them they can update their apps to support the changes. They won't document these changes, you won't know about them, and your app is now broken for your users. You have to work out how to fix it, then submit it for review, and if they catch your private API use this time around you've screwed your users.