Hi,
We've investigated the issue. We're incorrectly setting an error when this function is called outside of a debug context. If you create a debug context, it should work. We have fixed the problem in the driver and will include the fix in a future release.
Thanks,
Graham