# VST3 not recognized in existing Session after updating from JUCE 6.0.1 to current develop tip

**URL:** <https://forum.juce.com/t/vst3-not-recognized-in-existing-session-after-updating-from-juce-6-0-1-to-current-develop-tip/47157>\
**Category:** Audio Plugins\
**Created:** [August 1, 2021, 9:00pm UTC](https://forum.juce.com/t/vst3-not-recognized-in-existing-session-after-updating-from-juce-6-0-1-to-current-develop-tip/47157 "2021-08-01T21:00:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [August 1, 2021, 9:04pm UTC](https://forum.juce.com/t/vst3-not-recognized-in-existing-session-after-updating-from-juce-6-0-1-to-current-develop-tip/47157/2 "2021-08-01T21:04:26Z")

</div>

Stab in the dark - did you see this?

> [@AU Plugin Version in Logic Pro X](https://forum.juce.com/t/au-plugin-version-in-logic-pro-x/46992):
>
> Hi When I build my AU with juce CMake and validate them in logic pro I get an invalid version. [oh that AUVal screenshot is cutoff. In that picture the version of surge-xt it shows is “256.0.0” which matches the overflow from adding in the TWEAK] My CMakeLists.txt has project version “1.0.0.0” in the project declaration and it looks like that’s getting passed down with one too many turns. If I update my CMakeLists.txt to say “1.0.0” then the version …

---

_[View the full topic](https://forum.juce.com/t/vst3-not-recognized-in-existing-session-after-updating-from-juce-6-0-1-to-current-develop-tip/47157)._
