Glad your issue is fixed.
I can give you a little explanation why the cache is the issue now with 2.2.x. In previous versions there were two scripts, one to create the simple banner <div> and one to insert text into that <div>. That first script was impervious to a cache due to the way it was created using WordPress hooks. The second script just added the text, so even if it was cached, it would just replace the inner html of the banner twice. Now everything happens in one script that is able to be cached, so if two versions are cached they will create two banners. This solved an issue that a lot of users were experiencing where different plugins optimized the javascript at different times and caused the banner to not show. Caching is good for your website, it causes your website to load quicker for users, however it can cause this issue when you’re making changes or upgrading. There are ways i could avoid the issue entirely, but it may cause a slight slowdown of the website since the javascript would need to be loaded new every time the page loads. I would rather take advantage of the users cache plugins and help debug when stuff like this occurs.