Apps Noob going insane

[Crowposse]

To start, please forgive me if I'm in the wrong place to post this rant/question!

I'm a microsoft c# guy normally but have been tasked with creating an android app for tablets. I have no problem with Java as a language as I can read it and follow it simple enough.

I have downloaded the android adt built over eclipse and created and run a HelloWorld app. all good.

BUT.....I cannot debug at all. I can set a breakpoint and when it stops and i step into it it keeps asking for source. I'm presuming it wants the Android.jar file so i give it to it, no joy, i give it the whole folder, no joy, I give it every conceivable iteration of android I can find, no joy!

I set step filtering, no joy, I have set the manifest to debuggable, no joy.

I have read 20000 (possible exaggeration) pages on forums, some of which i have translated from Japanese, no joy.

What bloody source does it want!!!! What am I doing wrong?

This is my sixth day of trying to solve this and on the seventh i will rest! I am starting to detest android with a vengeance and all who sail in her! Learning curve issues, I know, but surely there must be someone out there that can cast some light on what i can do?!

Your humble noob
Paul

 

[out of ideas]

you cant check the regular logcat view?

 

[Crowposse]

you cant check the regular logcat view?

Sorry for delay. I've been reading another 20000 pages.

my logcat shows nothing after launching the emulator!

I've decided to give up. Android and java development is so stupidly difficult to set up! I have no problem with the code or the general logic but trying to get an IDE set up is ridiculous.

I get the impression it's like this to make people feel clever as some of the arrogant and childish responses on forums i've seen are beyond belief

"Out of Ideas", I dont include you in that remark as you had the courtesy to reply for which I thank you.

 

[alostpacket]

Yep, that's confusing at first for sure. What is probably happening is that when you "step into" code you are probably stepping into the Android OS source code.

The SDK doesnt actually come with this code (only stubbed version of it with javadocs)

99% of the time you wont need to see those classes, so you can use the "step return" button on the debugger.

Also to avoid stepping into something, you can always use the "step over" button

If you really want to see the Android source code, you need to download it from AOSP and point to that, but I have never in all my Android dev years needed to do this to use the step debugger effectively.

 

[alostpacket]

Also If the log cat disappears, go to the device/emulator tab and make sure the device or emulator you are using is selected.

there is also a dropdown for resetting adb, but that shouldnt be needed.

 

[Crowposse]

Thx for the info "alostpacket".

After my primal rant I'll get back into it and have another go.

For the past week my app dev has been akin to a shooting range...take a shot.....walk 100 yards to see what happened...walk back again... take another shot!!

Anyhow, thx again, I'm going in!!!