I have a suspicion that a macOS specific API behaviour (or even a bug perhaps) could be interfering here. Could you try this updated build to v3.0.2 and let me know if this version fixes the issue for you?
Yep that worked, TYSM !!
