Sorry, I used the wrong language. The mail intent works in response to a user button press. When the button is pressed, the entries are supposed to be mailed immediately. That is the way it previously worked.
Now, when the button is pressed, the code (with createChooser and without) runs through the mail intent with no error; but the e-mail accounts do not come up and nothing is sent. When I replace createChooser with the mail intent, the code still runs without error and no e-mails accounts come up; however, when I shut the entire program down, then the e-mail accounts come up and the information can be e-mailed as intended. It is as though the email intent is somehow "saved" and does not function until the entire program is stopped. On Mar 13, 10:50 am, Mark Murphy <mmur...@commonsware.com> wrote: > On Tue, Mar 13, 2012 at 10:47 AM, JFS <j...@sheagermain.com> wrote: > > When I drop createChooser and replace it with the emailintent > > (ACTION_SEND), nothing happens immediately. But when the service > > stops, I am then prompted with the expected set of e-mail accounts and > > can send the message. > > Why is a service using ACTION_SEND? That seems unusual. After all, you > have no idea if the user is even around to handle the ACTION_SEND > request. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android Training...At Your Office:http://commonsware.com/training -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
