Easy Mode Theme Not Successfully Rendering Community In Editor

[Andashd]

Hey there!

Brand new to the platform and currently playing around with the theming capabilities. Using the manual editor seems to work fine, but if I try to create a new theme and hit the 'magic wand' icon, the editor will load on the right but on the left, the community seems to have an issue rendering successfully: 

 

If I change some colors and then build the theme, those changes will be visible on the live community, but not seeing my changes live makes the editor very difficult to use. I've checked out a few of the videos of Easy Mode in use, and I don't appear to be forgetting to fill in an option - steps seem to be to create a new theme, hit the Magic Wand and then start tinkering. 

Only errors in dev tools that I'm seeing is:

root_library.js.gz?v=d815db93211729600800:2  jQuery.Deferred exception: $(...).spectrum(...).toRgb is not a function TypeError: $(...).spectrum(...).toRgb is not a function
    at https://content.invisioncic.com/mysite#/javascript_core/front_front_vse.js.gz?v=d815db93211729600800:22:2518
    at Function.jr (https://content.invisioncic.com/mysite#/javascript_global/root_library.js.gz?v=d815db93211729600800:1:9626)
    at baseController._getVarValues (https://content.invisioncic.com/mysite#/javascript_core/front_front_vse.js.gz?v=d815db93211729600800:22:2411)
    at https://content.invisioncic.com/mysite#/javascript_core/front_front_vse.js.gz?v=d815db93211729600800:22:1896
    at e (https://content.invisioncic.com/mysite#/javascript_global/root_library.js.gz?v=d815db93211729600800:2:26990)
    at t (https://content.invisioncic.com/mysite#/javascript_global/root_library.js.gz?v=d815db93211729600800:2:27292) undefined

I'm using Microsoft Edge for testing, which seems to be supported. I've only made OOTB changes to the site - nothing custom added and no integration set up yet. 

Not sure what I'm missing. Any guidance would be appreciated!
-Andrew

[Marc]

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.