Re: Android Studio Debugger doesn't work on private libraries

2,469 views
Skip to first unread message

Xavier Ducrohet

unread,
May 28, 2013, 3:33:11 PM5/28/13
to adt...@googlegroups.com
It's likely due to the fact that the source code of the library isn't properly setup to be the source of the jar file using in the main project. If you step through the code from your main app into your library, it's probably going to show you that there's no source attachement.

We need to fix this.


On Tue, May 28, 2013 at 11:17 AM, Kevin Smith <respect...@me.com> wrote:
I finally got my project building in Android Studio with gradle. When I debug my project breakpoints in the "application" module work, but breakpoints inside of the "library" module do not. The strange thing is that if I run the project and then attach the debugger after the application has started everything works as it should. Is this a bug or do I have something configured wrong?

--
You received this message because you are subscribed to the Google Groups "adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
http://developer.android.com | http://tools.android.com

Please do not send me questions directly. Thanks!

Kevin Smith

unread,
May 29, 2013, 6:18:56 AM5/29/13
to adt...@googlegroups.com
Thanks for the reply Xavier. Great session at Google IO.

If I attach the debugger after the app has been started the breakpoints do work and it links up with the code as it should. It is only when I start the app by clicking Debug from Android Studio that the breakpoints are ignored.

Nathaniel Waggoner

unread,
Nov 14, 2014, 1:44:56 PM11/14/14
to adt...@googlegroups.com
Did this ever get resolved?  I am encountering this issue on 8.14

Kevin Smith

unread,
Nov 15, 2014, 6:19:00 AM11/15/14
to adt...@googlegroups.com
This has been fixed for quite a while and I haven’t had any problems since.

Kevin

You received this message because you are subscribed to a topic in the Google Groups "adt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adt-dev/PhsHqkapSIQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adt-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

VegeChou

unread,
Dec 2, 2014, 4:20:09 AM12/2/14
to adt...@googlegroups.com
I had found the same problme in Android Stuido 1.0 RC 2, how can I solve this?


Kevin Smith <respectthecode <at> me.com> writes:

>
> This has been fixed for quite a while and I haven’t had any problems since.
> Kevin
> On Nov 14, 2014, at 1:44 PM, Nathaniel Waggoner <waggonernathaniel <at>
gmail.com> wrote:
>

Hovhannes Terteryan

unread,
Dec 18, 2014, 7:14:58 AM12/18/14
to adt...@googlegroups.com
I had the same problem with Android studio 1.0.1

Clive Jefferies

unread,
Jan 12, 2015, 8:28:32 AM1/12/15
to adt...@googlegroups.com

 found a solution that may help someone with this. If your project is using fragments that are in the library project, then you must include the fragment in the library project manifest: <activity android:name="[name of fragment]"/>

Reply all
Reply to author
Forward
0 new messages