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

Premise of EmailIntentBuilder no longer valid? #10

Open
xrad opened this issue Mar 21, 2020 · 4 comments
Open

Premise of EmailIntentBuilder no longer valid? #10

xrad opened this issue Mar 21, 2020 · 4 comments

Comments

@xrad
Copy link

xrad commented Mar 21, 2020

AFAIU, one of the premises EIB was built for was the lack of documentation of the various commonly used extras and ACTION_SENDTO. However, I just stumbled across this:

https://developer.android.com/guide/components/intents-common.html#Email

What do you think?

@cketti
Copy link
Owner

cketti commented Mar 21, 2020

The documentation for ACTION_SENDTO does not contain information about any extras.

You can of course follow the approach in the link you posted. But you'd be gambling that all the email apps used by your users support these extras.

@xrad
Copy link
Author

xrad commented Mar 21, 2020

I understand what you're saying and I'm not saying EIB is obsolete. However, given the offical(!) information at the link I posted I'd be inclined to argue that lack of any(!) extras being mention with ACTION_SENDTO documentation is just a major docbug. Probably since they never cared much about email in the first place, otherwise we'd not have THREE different actions for the basically just variations on the theme.

Admittedly I'm a bit worried atm because of the other issue I brought up, but I must say the official snipped in the guide got me thinking.

@cketti
Copy link
Owner

cketti commented Mar 21, 2020

You could do some compatibility testing. I'd say the chances are pretty high that most email apps support ACTION_SENDTO with the email extras.

But I wouldn't bet on the documentation getting changed anytime soon. See https://issuetracker.google.com/issues/36946106

@xrad
Copy link
Author

xrad commented Mar 21, 2020

Thanks. I left a comment there. Closing this as obsolete is ridicoulous, even though this was maybe just janitorial since the issue is too old for them to care.

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

2 participants