watchOS 2 Support

[nlutsenko]

This issue is for tracking watchOS 2 support, mainly via Cocoapods.
To use the beta version of Parse SDK in your watchOS 2 app - add the following to your podfile:

pod 'Parse', :git => 'git@github.com:ParsePlatform/Parse-SDK-iOS-OSX.git', :branch => 'master'

We are aiming to get this very soon out, please comment here if you find any issues using Parse SDK with watchOS 2.

Implementation todo list:

• Add basic target for watchOS 2 SDK (compiler warnings are ok, since we are not going to add this to tests just yet)
• Decouple Reachability from PFEventuallyQueue/PFCommandCache/PFPinningEventuallyQueue (this is going to still be used for Analytics)
• Disable ability to saveEventually/deleteEventually, since it doesn't quite make sense on the watchOS
• Update PFDevice to use WatchKit APIs on watchOS
• Update PFApplication to be a no-op on watchOS
• Update PFLocationManager to use compatible APIs when running on watchOS
• Disable extensions data sharing APIs (they don't work on watchOS)
• Disable PFPush (at least for the first release)
• Disable PFInstallation (at least for the first release, unless we build PushKit support)
• Disable PFPurchase (no StoreKit support on watchOS)
• Disable PFProduct (doesn't really make sense without PFPurchase)
• Disable PFNetworkActivityIndicatorManager (no indicator on watchOS)
• Add watchOS 2 SDK to Travis-CI just for building
• Test all the things! (no XCTest for watchOS, bummer!)
• Update podspec to include only watchOS specific things
• Add watchOS starter project (optional)
• Add watchOS 2 SDK to deployment packages

Development is happening in master, though we aren't going to ship the watchOS version until this list is finished.
If you want to play with Parse SDK for watchOS - simply compile the Parse-watchOS target available in Parse.xcworkspace.

This comment is constantly updating, sometimes without you noticing

[bmueller]

Also, could we please get support for PushKit when sending push notifications? PushKit is required to update watchOS 2 complications remotely via push notification.

[nlutsenko]

As far as I can tell - there is not a whole lot of changes required between for the SDK itself to support PushKit, as we have already quite generic system to store device tokens, the only changes would be on the backend as well as in documentation.

I believe we can make it happen, though I would separate these and not block the generic release of watchOS 2 compatible SDK with PushKit.

[bmueller]

Awesome! Any chance this might happen before the final release next week?

[Perjan]

Hey @nlutsenko any news regarding watchOS2? Thanks.

[vvsokolov]

@nlutsenko, Any news ? Thanks.

[Ge0rges]

Any updates? Thank you.

[Baza207]

@nlutsenko Is this getting a feature list drawn up along with the tvOS framework target? Would be really great to have a native watchOS Parse Framework, so we don't have to use WatchConnectivity to transfer data. Though I can imagine you've got your hands full at the moment with all these new platforms to sort out frameworks for. 😊

[nlutsenko]

😁 Yup, we are in the process of compiling down a list of things we need to change/update to make watchOS 2 and tvOS versions of the framework happen.

[Baza207]

@nlutsenko awesome. Good luck and keep up the good work. Great set of tools you guys got there. 😊

[nlutsenko]

Hey everyone, I just put a list of all the things we identified so far and need to tackle before we can ship the watchOS version of the framework.
The list is going to be amended/changing as we go, but all of the pull requests are ultimately going to be attached to this issue.
The list is also serial, so we don't intend to tackle the problems at the end of the list, before the problems on the top are resolved.