KV == Kostya Vasilyev kmans...@gmail.com writes:
KV Two things.
KV Calling putExtra twice with the same key is worthless, as only
KV the latest will be kept (you can think of intent extras as a hash
KV map). Don't remember if extra_email is supposed to be an array.
Good point. I
T == TreKing treking...@gmail.com writes:
T On Wed, Mar 23, 2011 at 3:43 PM, Jake Colman col...@ppllc.com wrote:
Apparently the application will force close when sending the file
if the logging had been on for an extended period of time before
they tried to send it.
T
On Wed, Mar 23, 2011 at 4:33 PM, Jake Colman col...@ppllc.com wrote:
That's what I'm trying to find out! He claims that my app is force closing
and I'm trying to figure what might cause that.
Oh, well, in that case ... a bug in the bug reporting, classic (I had one of
those).
Since it
Kostya,
I _think_ the intent is well-formed. Here is the code I am using:
Intent emailIntent = new Intent( android.content.Intent.ACTION_SEND );
Resources res = getResources();
String emailTo[] = { AppMetaData.DEVELOPMENT_EMAIL_ADDRESS };
String emailSubject = res.getString(
T == TreKing treking...@gmail.com writes:
T On Wed, Mar 23, 2011 at 4:33 PM, Jake Colman col...@ppllc.com
T wrote:
That's what I'm trying to find out! He claims that my app is force
closing
and I'm trying to figure what might cause that.
T Oh, well, in that case ... a
Two things.
Calling putExtra twice with the same key is worthless, as only the latest
will be kept (you can think of intent extras as a hash map). Don't remember
if extra_email is supposed to be an array.
Your code calls collectDeviceInfo - if it crashes, your code will not send
email. Or one of
On Wed, Mar 23, 2011 at 4:55 PM, Jake Colman col...@ppllc.com wrote:
If I specify it then shouldn't that catch the Out of Memory exception
or whatever it is that caused the force close?
Yup.
-
7 matches
Mail list logo
