[git] is not triggering a rebuild when code is updated about build HOT 3 CLOSED

6/28/12: BTW, I can't seem to use the manual "update code" then "rebuild" or "re-build all" suggested work-around. I'm having to create new apps. ugly.

As long as you are looking at this update/rebuild workflow, I'd like to humbly suggest some somewhat related enhancements:

• a text area to receive log/diagnostic info would be useful
• you might increase throughput if compiles for certain platforms could be disabled on the fly
• a general "highway status board" would be great ("everything is cool, bring it on!"; "infrastructure outage; we know the problem, and its being fixed" ; "infrastructure outage, we're investigating")

You guys are awesome, keep up the good work!

-Cord

7/17/12 regarding the 'status board' idea; please see the TestFlight twitter feed for great best practices....

from build.

7/4/12: I have a lingering suspicion that the browser (chrome in this case) is concealing some hints that might be useful. The presentation (or not) of QR codes is often awkward. The best example that I can describe is from the main app page where we see rectangles for each platform; these appear gradually during the build process. However, often, when there is no iOS rectangle, I select the drill-down link for my app anticipating that the QR code is nearly complete. As soon as that new page is rendered, the iOS QR code is available. Coincidence? It happens very frequently.

from build.

Issue has been resolved.

from build.