Add Hockeyapp as a distribution channel about shenzhen HOT 4 CLOSED

+1

from shenzhen.

I just pushed a working version of a HockeyApp plugin to our fork. For now it only uploads the .ipa.

We always recommend uploading the dsym with a build so symbolication will work as soon as the first crash is send to us. I'm not sure how we should accomplish that. Changing build.rb so it would put the .dsym in the project root too (so the distribute script could find the dsym) would be the easiest way. But then there is a another file laying around in the project root.

Right now you will loose the dsym of you last build since the new build will overwrite it (if you don't upload it automatically). So maybe the best way would be to create an .xcarchive and generate the .ipa from that. So the developer will still have the build in his organizer and the second script could just look for the newest archive and generate the .ipa and upload it together with the .dsym. (Here is an example to create the .xcarchive via a shell command: http://stackoverflow.com/questions/2664885/xcode-build-and-archive-from-command-line/7908397#7908397)

In our mac uploader application HockeyMac we create the .ipa from an existing xcarchive (https://github.com/bitstadium/HockeyMac/blob/develop/Classes/CNSArchive.m#L301) This should be easily portable to ruby.

@mattt what do you think?

from shenzhen.

So I created a pull request with a basic HockeyApp plugin which will upload .ipa and dsym. (If I could have added the pull request to this issue: Sorry, didn't know how and started thinking about it after I created the pull request)

Now the symbolication will work with HockeyApp too. But we still think it would be better to create an .xcarchive so the developer has all data available and doesn't need to rely on any third party service to keep his dsym available.

from shenzhen.

Really happy to see HockeyApp added for 0.2.0, thanks to @Soph.

@Soph: In ef569f3, I specified xcodebuild to do clean, build & archive (with options to turn clean and archive off). Doing xcodebuild archive generates a .xcarchive file and saves it to the Xcode organizer. I think this is great behavior to encourage as the default, to keep a paper trail of releases (again, with the option to turn that off, if needed).

from shenzhen.