My RubyMotion app is almost complete. I spent a lot of time today getting ShareKit to work correctly in it; while Motion Cocoapods generally work pretty well out of the box, ShareKit was obstinate and unpleasant and it took me most of the day to get it working correctly. So, to save someone else some time, I documented the steps I took to get it working.
Just a small caveat first, though; this is not simple and elegant like the rest of the code here. (Generally.) I could’ve done this in a better way – by extracting the changes out into a new Cocoapod spec repository – and maybe in the future when I have some time I will. But until then, I hope this somewhat ugly hack helps out someone else!
1. Set up the Rakefile
First, you need to add the ShareKit sharerers you want into your Rakefile.
1 2 3 4 5 6 7 8 9 10
I couldn’t get this working with ObjectiveFlickr because of BridgeSupport duplicate symbol errors; if you want Flickr sharing, you’ll have to manually edit the conflicting symbols out of either ShareKit or ObjectiveFlickr. For my app – and the rest of this walkthrough – I’ll assume the only sharers you’re using will be Facebook and Twitter.
2. Create a ShareKit Configuration File
I put mine in
app/extensions/sharekit_configuration.rb, and it looks like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
After you create the file, you need to load it in your
1 2 3 4 5 6 7 8
SHK.flushOfflineQueue will try to send stored shared content, if there is any, so make sure to include it.
3. Alter your Cocoapod Sources
This is the ugly hack. The Cocoapod version of the Facebook iOS SDK is not the correct one; the ShareKit people provide their own fork that includes the functionality you need. (If you don’t use it, the Facebook login won’t work at all.) But also the version of ShareKit is old and the Facebook sharing functionality appears to be broken in it anyway, so you might as well update that to the most recent version as well.
All Cocoapod spec information is stored in
~/.cocoapods/master. The first file we’ll change is the Facebook iOS SDK pod spec. It’s located at
~/.cocoapods/master/Facebook-iOS-SDK/1.2/Facebook-iOS-SDK.podspec, and you want to change the line of it that defines the source to look like this:
1 2 3 4 5
This points to the most recent commit of the ShareKit Facebook iOS SDK fork. And similarly, we should update the ShareKit pod as well, which is located at
1 2 3 4 5
4. Manually Copy Resources
ShareKit expects that its bundle and plist will be present in the resources directory, and you’ll have to manually move them there for it to work.
1 2 3
For some inexplicable reason ShareKit seems to want the bundle both in the resources directory and as a subdirectory in its own bundle. I have no idea why this is but I couldn’t get ShareKit working without this step.
5. Hook up the Share Action
This is the simplest, most straightforward step. In your view:
1 2 3 4 5 6 7 8 9
And in your controller:
1 2 3 4 5 6 7 8
That’s all there is to it! When you touch the ‘Tap to Share’ button, you should see the ShareKit action sheet pop up with all of the functionality you’d expect ShareKit to have. Twitter and Facebook sharing are yours to leverage!
As I said, this is sort of ugly, especially manually editing Cocoapod sources. But hopefully this guide will help someone else integrate ShareKit into their RubyMotion project quickly and easily. I sure wish I had known all this earlier this morning!