[BUG]: Prevent false-positive share success events in Discord fallback

[aniket05singh]

Bug Description

Description

The current Discord fallback share flow emits social_share_success and triggers the onShare callback immediately after calling copyLink() and window.open().

If clipboard access fails or the popup is blocked by the browser, the library can still report a successful share even though the fallback action did not complete successfully.

Expected Behavior

Only emit social_share_success and invoke onShare after confirming that the fallback action has completed successfully.

Possible Solution

• Return a success/failure result from copyLink().
• Verify that window.open() succeeds.
• Emit the success event only when the fallback action completes successfully.

I'd be happy to work on this Issue

Steps to Reproduce

No response

Logs and Screenshots

No response

Environment Details

No response

Impact

Critical - Application is unusable

Code of Conduct

• I agree to follow the Code of Conduct
• I have joined the Discord server and will post updates there
• I have searched existing issues to avoid duplicates

[kpj2006]

thanks for reporting bug
@aniket05singh could you show as some ss or video to reporoduce it?

[aniket05singh]

@kpj2006 Thanks for checking!
I couldn't reliably reproduce it with a screenshot/video since it depends on browser behavior (clipboard permissions or popup blocking). The issue is based on the current code flow, where success is emitted without verifying that copyLink() or window.open() actually succeeded.

[kpj2006]

@amankv1234

[amankv1234]

@kpj2006 ,I will check it