-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android immediately passes success back to app? #26
Comments
Hi @jnorris441, Unfortunately, this is a limitation of Android right now, we can't get the result after starting the new activity. We are using ACTION_SEND or ACTION_VIEW and these intents won't return results. see |
It's been more than a year, has this got any fix yet? I'm facing this issue and my app cannot work properly without this callback triggering correctly on iOS. |
This issue is about Android. Android did not change it is way of handling callback. If you are having an iOS issue, feel free to open a new one. |
So is this issue considered working as intended/not going to fix/only Android OS can fix? Running into the same issue with immediate success callback on the Android platform. |
hello @pixelpuffpastry, Yes, unfortunately nothing has changed over the years. Please refer to #26 (comment). |
Ah - thanks for the quick reply! |
That's interesting, definitely seems complex but would deserve some digging. |
@dbaq Any update on callback for android? |
@umairrafiq1133 nothing on the android front. |
Hi @dbaq any update on the android callback? |
hey @dshark95, as far as I know, it remains the same on Android. |
The iOS composer waits to see if the message was sent or cancelled and fires the right callback. The Android version immediately fires success whether they end up sending or not.
There is not a way to make Android behave like iOS correct?
(this is using INTENT)
The text was updated successfully, but these errors were encountered: