No solution here either:
I haven’t seen this problem yet with the development/security version of the binding …