Batarang stop working

[dengh...@gmail.com]

Hello:

   Am I the only one that find Batarang stop working yesterday after it upgrade itself? 

Nothing was displayed in the models view. Even simple example from angular.js home page not working. 

Regards. 

[vladislav...@eyetrackshop.com]

Same happened for me

[Marcin Warpechowski]

Same to me. As a workaround I installed previous version (0.2.1 works in stable way) from source, as described here: https://github.com/angular/angularjs-batarang

[Dave Merrill]

Just tried it for the first time, demo looks great, install from app store doesn't show anything in Chrome 23. This doesn't still need Chrome dev builds, does it?

I don't see a tag for 0.2.1. How are you recreating it? From the August 7 commit where the version got bumped to 0.2.1, https://github.com/angular/angularjs-batarang/commit/ec526410f5009ce86a7d7ddb0e26bf293678a23e?

Thanks,

Dave Merrill

[Marcin Warpechowski]

Yes, I get 0.2.1 from that sha1 exactly

> --
> You received this message because you are subscribed to the Google Groups
> "AngularJS" group.
> To post to this group, send email to ang...@googlegroups.com.
> To unsubscribe from this group, send email to
> angular+u...@googlegroups.com.
> Visit this group at http://groups.google.com/group/angular?hl=en-US.
>
>

[Dave Merrill]

Cloned the repo, checked out that hash, installed that, worked perfectly. Awesome!

Gotta say, Angular has some pretty great tooling, between Batarang and the whole Testacular business. At work we've got automated back end testing, but nothing on the front end. I'm working on a moving a private project to Angular, partly for its own sake, and partly to learn, and I'm so impressed with the testing tools.

Thanks again for you help,

Dave

[Michael Bielski]

Followed those steps and viola! Working Batarang! Saved my bacon!

I hope BFord gets some cycles soon to fix the current version.

[Dave Merrill]

Absent a real fix for the head revision, be helpful just to:

a) Create a tag pointing to the working revision.

b) Put a note up telling people that head is unstable, and suggesting that they use that tag.

Perhaps even better would be to create a tag for the current revision, so that work isn't lost, then roll the head back to the working one. That way the head, which is what people get by default, would be working. None of this fixes the app store version, or automatic updating.

Dave Merrill