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 am facing an issue where the callback is executed right after the SMS is triggered to be sent. This means that if I use "sendDirect" option, then the callback always returns success even though the SMS might have failed to be sent in the background, and if I use "sendIndirect" option, then the callback is executed even when the SMS app is open and the user hasn't hit the Send button. Doesn't the module wait for the SMS app/intent to return before the callback is executed? If not, then what's the difference between using Linking.openURL() vs using this module? The main reason for using this module was to have my app wait for the SMS to be sent before it displayed confirmation or error response to the user.
The text was updated successfully, but these errors were encountered:
I am facing an issue where the callback is executed right after the SMS is triggered to be sent. This means that if I use "sendDirect" option, then the callback always returns success even though the SMS might have failed to be sent in the background, and if I use "sendIndirect" option, then the callback is executed even when the SMS app is open and the user hasn't hit the Send button. Doesn't the module wait for the SMS app/intent to return before the callback is executed? If not, then what's the difference between using Linking.openURL() vs using this module? The main reason for using this module was to have my app wait for the SMS to be sent before it displayed confirmation or error response to the user.
The text was updated successfully, but these errors were encountered: