Glad to hear it was all fixed.
Would you be able to share some details of the fix?
- e.g. the build number the issue was with an the build number that fixed the issue.
That way if someone else has a similar problem it may help them identify the solution a bit quicker.
Regards,
Stephen.
