Add watchOS and tvOS support

[cbaker6]

• Add watchOS and tvOS support
• Add cache to travis and circle for faster builds
• Move Carthage build to last in circle since it's the slowest and more important to see if iOS, macOS, and demo builds
• Update project versions to prepare for release, updated the versions to 2.7.3
• Update jazzy docs to newer version

This PR should probably be a release.

[cbaker6]

Note that Travis seems to be having some issues with Xcode builds, but I don't see the issue listed on travis. You may have to rerun the travis build if it fails to start

[drdaz]

Looks great.

[drdaz]

Actually... the changelog needs an entry

[cbaker6]

@TomWFox @drdaz can one of you push the pods? It looks like it failed to deploy and didn't give much info about the failure.

[cbaker6]

@TomWFox do you if the COCOAPODS_TRUNK_TOKEN is set? Travis us giving this “ [!] You need to run pod trunk register to register a session first.”

[TomWFox]

It is set, it has probably just expired - they do that periodically

[TomWFox]

Fairly sure the deployment is broken anyway because it work for the last release either

[cbaker6]

I tried a few different things in travis, but couldn't get it to go. I agree that the deployment seems broken.

I add this branch to push the pod manually for 2.7.3, https://github.com/parse-community/ParseLiveQuery-iOS-OSX/tree/2.7.3-pod

[cbaker6]

I found the problem...

During PR's to the master branch travis shows the following environment vars setup in the travis build log:
https://travis-ci.com/github/parse-community/ParseLiveQuery-iOS-OSX/jobs/441210418#L121

Setting environment variables from repository settings
120$ export GITHUB_TOKEN=[secure]
121$ export COCOAPODS_TRUNK_TOKEN=[secure]

I think the In the COCOAPODS_TRUNK_TOKEN isn't enabled for tags as it doesn't show in the logs anymore, the environment variable is missing. @TomWFox can you try to completely delete it and add it back enabling it for tags?
https://travis-ci.com/github/parse-community/ParseLiveQuery-iOS-OSX/jobs/441073847#L134

Setting environment variables from repository settings
134$ export GITHUB_TOKEN=[secure]

[cbaker6]

I think the Only available to the master branch is what's blocking it from tags. Setting it to Available to all branches should fix it

[TomWFox]

Sorry for the lack of response here, I've been having all sorts of issues with my shell since updating to Big Sur 🤦

@drdaz Can you get a new trunk token and put it in travis?

[drdaz]

I'll see if I can figure that out later today 😃

[drdaz]

I've updated the Cocoapods token in Travis and made it 'Available to all branches'.

[TomWFox]

Thanks!

[cbaker6]

I was able to deploy 2.7.3 and 2.8.0 via Travis by re-running the respective builds. The good thing about Travis is it can rerun the exact same build while pulling the latest env vars. We shouldn’t have an issue pushing via tags and Travis as long as the token doesn’t expire.

Also, the docs are deploying again via Travis and jazzy. Only thing is, the code in this repo is currently undocumented. I made the web link align with the iOS and Swift repos, http://parseplatform.org/ParseLiveQuery-iOS-OSX/api/

[TomWFox]

Awesome. The token expires after some period (a couple months roughly) if not used which is likely on this repo. I believe all that is needed is to run pod trunk me periodically which could be done with a Cron job.

[cbaker6]

I’ve seen cron in Travis, but I’ve never tried it. I wonder if setting the pod token to the same value as the iOS SDK (and eventually the Parse-Swift SDK) will fix the expiration problem since at least 1 of these should release within a 2 month period?

[TomWFox]

Thats definitely a good idea. I think it would still be reasonably conceivable for the token to expire but with the same token in each we could have one Cron job as an insurance.