Yes I did. My solution is to launch the tool from a canvas instance that is being served over https and not http.

My theory is that the problem was caused by the browser blocking Canvas's cookies because it's being served over http and the cookies weren't configured for http.

We have a canvas instance served at https://canvas-dev.asu.edu. When I launch it there I don't have any problems. I only get this problem in my local instance which is served at http://canvas.docker.

The attached video shows our tool working. The only thing different is that it's being launched from https://canvas-dev.asu.edu and not http://canvas.docker.  http://canvas.docker was the url used in videos attached in the problem post.