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 Blog Reader Android App Using Intents to Display and Share Posts Adding a Different Icon for Older Menus

Blog Reader say Oops! Sory! Cant connect blog at my mobitel by WiFi

My Blog Reader say Oops! Sory! Cant connect blog at my mobitel by WiFi and yours Blog Reader from Google Play say it on my mobitel. What I must setup on my Android 2.3.3?

2 Answers

Ben Jakuben
STAFF
Ben Jakuben
Treehouse Teacher

When you run the app from Eclipse, do you get any kind of error in the logcat console? If so, please paste them in here and we can help you troubleshoot.

When I run the app from Eclipse, I do not get any kind of error. Console: Installing KarteloBlogCitac2.apk... [2014-05-02 18:33:06 - KarteloBlogCitac2] Success! [2014-05-02 18:33:06 - KarteloBlogCitac2] Starting activity org.kartelo.karteloblogcitac2.MainListActivity on device 0123456789ABCDEF Only error: when I install and start the app from my mob by WiFi: progressBar run, run, run and after runing I see Items n find. But, when I dowmload your app Blog reader from Google Play at my mob, I have same problem: progressBar run, run, run and after that I have No items found.

Ben Jakuben
Ben Jakuben
Treehouse Teacher

I think you may be running into a known issue. If you run the app from Eclipse, can you switch to the logcat tab on the bottom and see if you get an error message there?

I think the issue is the one in the Teacher's Notes of this video. The solution is to use some alternate code included in that link. But we won't know for sure until you see if there are any errors in the logcat or not.