I believe that this restriction has been in effect on mobile for quite some time (in fact, I don't think mobile Safari ever had WebAudio without this limitation.)

So, if your code works on mobile right now, it should also work in Chrome 70.

As a developer, it's kind of a PITA. But as a user, I appreciate the fact that websites won't be able to just start playing audio without some interaction from me.

Also, to clarify the fix, the WebAudio context must be either created or resumed in response to a click/tap/etc. I usually just provide some "Go" button and then create the context in the click handler.