james75

As it happens I just came across this myself. Your implementation looks good to me.

I'm also experiencing this, any solution?

I got the same. Rolled back to v1.0.0 and its working.