Hi @rishikapadia7, good news! We have correctly reproduced and identified this bug within the Core SDK and will include the fix in the forthcoming release. Please Be Sure to check back on the SDK page regularly to be sure of getting the latest version. 🙂