Memory leak detected by LeakCanary (Edit: needed to call .reset() to clear resources)

[hcaptcha]

Memory leak detected by LeakCanary (Edit: needed to call .reset() to clear resources)

[CAMOBAP]

Thanks for reporting this. This is expected behavior. We cache the fragment instance inside SDK to speed up the next HCaptcha.verifyWithHCaptcha calls.

Once you are done with verification, you can call HCaptcha.reset() to release all allocated resources including the strong reference to com.hcaptcha.sdk.HCaptchaDialogFragment

HCaptcha.reset() available since 3.8.0 version

@GersomR-afk any feedback is appreciated, please let us know if proposed solution works for you

[GersomR-afk]

Hello @CAMOBAP! Thank you for getting back to me so quickly and providing a solution to the memory leak issue. I apologize for not mentioning earlier that I wasn't using the 3.8.0 version of the hCaptcha SDK.

I really appreciate your help and the suggested solution of calling HCaptcha.reset() to release all allocated resources. It's great to know that this function is available in the 3.8.0 version.

However, I have a suggestion for improvement. It would be beneficial if this information about using HCaptcha.reset() to prevent memory leaks were made more explicit in the documentation, particularly in the README file. Clarifying this point would help developers like me who might overlook it and face similar memory leak issues.

Once again, thank you for your prompt assistance and the recommended solution. The issue's been resolved now. If I encounter any further issues or have additional feedback, I'll be sure to let you know.

[CAMOBAP]

@GersomR-afk thanks for the feedback, we add this information to README to improve our documentation