The application may be doing too much work on its main thread - Android

Question

Hi I am developing an android application where I face this error when I try to send Email from my app. I am sending mail at the background without using intent based on this link

My program:

String em[] = {gete(u, e)};

MailSender sender = new GMailSender(
                "email id",
                "password");


                           sender.sendMail("Sub", "Body", "from address",""+em[0]);

                           move();
                        }

                    } catch (Exception e) {

                        Toast.makeText(getApplicationContext(), "Error", Toast.LENGTH_LONG).show();
                    }

                }

            }).start();
        }
    });

Application works fine when I specify the recipient's email address directly. Problem comes when I specify it as string array where I stored recipients email addresses.

Logcat shows :

Skipped 222 frames! The application may be doing too much work on its main thread.

Can anyone tell me what is the exact problem ?

Yes, I found by using AsyncTask this can be solved. I don't have any idea how that should be used here — user3688536, Jul 24 '14 at 12:05

score 7 · Accepted Answer · edited Sep 04 '15 at 18:33

7

As it is said to you, you're doing too much things. So use a thread to execute your send action:

new Thread(new Runnable() {
    public void run() {
        try {
            sender.sendMail("Sub", "Body", "from address",""+em[0]);
        } catch (Exception e) {
           Toast.makeText(getApplicationContext(), "Error", Toast.LENGTH_LONG).show();
        }
    }).start();

edited Sep 04 '15 at 18:33

ssi-anik

2,998
3
23
52

answered Jul 24 '14 at 12:05

odiiil

276
1
2
9

Thanks I tried this and still same thing shows in logcat, unable to send mail – user3688536 Jul 24 '14 at 12:23
Hey sorry its working.. Thank you so much. I was checking the wrong mail id – user3688536 Jul 24 '14 at 12:34
I sure would like to see the .start(); – danny117 Nov 21 '14 at 23:43

The application may be doing too much work on its main thread - Android

1 Answers1

Linked