Skip to content
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

Closed
jnorris441 opened this issue Mar 26, 2015 · 12 comments
Closed

Android immediately passes success back to app? #26

jnorris441 opened this issue Mar 26, 2015 · 12 comments

Comments

@jnorris441
Copy link

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)

@dbaq
Copy link
Member

dbaq commented Mar 27, 2015

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
https://developer.android.com/reference/android/content/Intent.html#ACTION_VIEW (output: nothing)
https://developer.android.com/reference/android/content/Intent.html#ACTION_SEND (output: nothing)

@EduardoIbarra
Copy link

EduardoIbarra commented May 30, 2016

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.

@dbaq
Copy link
Member

dbaq commented May 30, 2016

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.

@mrlonnie
Copy link

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.

@dbaq
Copy link
Member

dbaq commented Mar 28, 2017

hello @pixelpuffpastry,

Yes, unfortunately nothing has changed over the years. Please refer to #26 (comment).

@mrlonnie
Copy link

Ah - thanks for the quick reply!

@Kevin-Hamilton
Copy link

@dbaq is this a possible solution?

@dbaq
Copy link
Member

dbaq commented Dec 21, 2018

That's interesting, definitely seems complex but would deserve some digging.

@umairrafiq1133
Copy link

@dbaq Any update on callback for android?

@dbaq
Copy link
Member

dbaq commented Jan 23, 2019

@umairrafiq1133 nothing on the android front.

@dshark95
Copy link

Hi @dbaq any update on the android callback?

@dbaq
Copy link
Member

dbaq commented Mar 29, 2022

hey @dshark95, as far as I know, it remains the same on Android.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants