Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Android Build a Weather App (2015) Concurrency and Error Handling Making Our Code Asynchronous

Ki Bum Kim
Ki Bum Kim
1,520 Points

I/Choreographer: Skipped 37 frames! The application may be doing too much work on its main thread.

Hi,

I was following the video and I could have retrieved the data from the forecastUrl. But after retrieved data was shown on the log, "I/Choreographer: Skipped 37 frames! The application may be doing too much work on its main thread." statement was followed. I tried to figure out the problems but couldn't find any solution.

If you need more info, I will definitely post rest of the code.

Thank you.

1 Answer

Hi there,

Don't worry about messages like that - they aren't related to you app.

The emulator is emulating being a phone so there are all sorts of messages being generated. If you filter to those that are to do with your app, those are the ones you ned to worry about! THe others will constantly appear even if you have no app running - it is just doing what a phone does!

I hope that helps.

Steve.

Ki Bum Kim
Ki Bum Kim
1,520 Points

Wow... Thank you very much for your help. I was very frustrated when I saw those errors and googling didn't get me any solution. I appreciated it, Steve Hunter

Ha! Yes, I remember doing the same.

I generate enough errors of my own without needing to worry about stuff the phone did by itself! :-)