You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered an issue when working with react-native-signature-canvas. In my use case, I have two signature canvases that need to be signed and validated simultaneously.
Occasionally (about 1 in 4 times), when saving both signatures, the same signature gets saved for both canvases, even though they are distinct.
I suspect the issue might be related to how the component handles unique identifiers for the saved signature data (e.g., filenames or temporary storage paths). Could you confirm if this is a known issue, or if there’s a workaround to prevent this conflict?
Steps to Reproduce:
Render two signature canvases simultaneously in a screen.
Sign both canvases with different signatures.
Save both signatures (e.g., using onOK callback or similar).
Observe that, in some cases (approximately 1/4 times), the saved signatures are identical.
Expected Behavior:
Each signature canvas should save its unique signature without overwriting or duplicating the other.
Thank you for your help and for maintaining this library!
The text was updated successfully, but these errors were encountered:
Description:
Hello,
I encountered an issue when working with react-native-signature-canvas. In my use case, I have two signature canvases that need to be signed and validated simultaneously.
Occasionally (about 1 in 4 times), when saving both signatures, the same signature gets saved for both canvases, even though they are distinct.
I suspect the issue might be related to how the component handles unique identifiers for the saved signature data (e.g., filenames or temporary storage paths). Could you confirm if this is a known issue, or if there’s a workaround to prevent this conflict?
Steps to Reproduce:
Render two signature canvases simultaneously in a screen.
Sign both canvases with different signatures.
Save both signatures (e.g., using onOK callback or similar).
Observe that, in some cases (approximately 1/4 times), the saved signatures are identical.
Expected Behavior:
Each signature canvas should save its unique signature without overwriting or duplicating the other.
Thank you for your help and for maintaining this library!
The text was updated successfully, but these errors were encountered: