# Live build weirdness, could be user error...?

**URL:** <https://forum.juce.com/t/live-build-weirdness-could-be-user-error/36357>\
**Category:** General JUCE discussion\
**Created:** [November 26, 2019, 2:56pm UTC](https://forum.juce.com/t/live-build-weirdness-could-be-user-error/36357 "2019-11-26T14:56:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anoesisaudio](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/anoesisaudio/32/1132_2.png) [@anoesisaudio](https://forum.juce.com/u/anoesisaudio)\
**Post date:** [November 26, 2019, 2:56pm UTC](https://forum.juce.com/t/live-build-weirdness-could-be-user-error/36357/1 "2019-11-26T14:56:27Z")

</div>

I built the Projucer today (using Dev branch) and found that Live Build was no longer working (see screenshot below).

Just to make sure i was not doing something wrong during the build, I rebuilt it using the Master branch and got the same result.

Just to make sure that I did not make another mistake during the build (which is rather simple), I downloaded the Projucer pre-built for mac and got the same result.

Has anyone ever seen this before & fixed it?

 ![live-build](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/5/5c9b77ae78dd092cc07cddff192db7ea0900f358.png)

---

<div class="post-metadata">

**Author:** ![anoesisaudio](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/anoesisaudio/32/1132_2.png) [@anoesisaudio](https://forum.juce.com/u/anoesisaudio)\
**Post date:** [February 13, 2020, 1:28pm UTC](https://forum.juce.com/t/live-build-weirdness-could-be-user-error/36357/2 "2020-02-13T13:28:37Z")

</div>

This was fixed recently. Thank you very much!

---

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [February 13, 2020, 7:00pm UTC](https://forum.juce.com/t/live-build-weirdness-could-be-user-error/36357/3 "2020-02-13T19:00:44Z")

</div>

Yes, this was fixed in the 5.4.6 release. Thank you for updating this thread!
