Debug sources default to compileSdkVersion instead of the emulator version [74128300]

Fixed

Bug

Reviewed (L1)

Status Update

No update yet.

Description

jo...@gmail.com

created issue #1

Mar 4, 2018 05:41AM

Occurs with both:

Android Studio 3.0.1
Build #AI-171.4443003, built on November 9, 2017
JRE: 1.8.0_152-release-915-b08 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.2

and:

Android Studio 3.1 Beta 4
Build #AI-173.4615496, built on February 21, 2018
JRE: 1.8.0_152-release-1024-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.2

Emulators:

Nexus 5X API 23
Nexus 5X API 25

When debugging an app, the SDK source used should be the version of the device or emulator that is running. Instead, the source from compileSdkVersion is used, making it difficult to effectively debug.

In the attached images, I set a breakpoint in the first line of ViewRootImpl#performTraversals

private void performTraversals() {
final View host = mView; // breakpoint set to this line.

In API 23, this maps to 1284.
In API 25, this maps to 1446.

The attached screen captures show how the actual and expected behavior differ.

Per the advice given here:

https://issuetracker.google.com/issues/37058409#comment7
I've also attached my idea.log.

API23_Actual.png

291 KB

View

Download

API23_Expected.png

267 KB

View

Download

API25_Actual.png

347 KB

View

Download

API25_Expected.png

288 KB

View

Download

emulator_specs.png

62 KB

View

Download

idea.log

485 KB

View

Download

Comments

jo...@gmail.com <jo...@gmail.com> #2Mar 4, 2018 05:44AM

Also, I have SDKs installed for APIs 22-27.

installed_sdks.png

89 KB

View

Download

uc...@google.com <uc...@google.com> #3Mar 7, 2018 08:06PM

Assigned to rp...@google.com.

Thanks for your request. We will investigate this issue and see if we can implement the behavior you've requested.

jo...@gmail.com <jo...@gmail.com> #4May 30, 2018 08:41PM

As an additional alternative, it should be possible to specify a label in the options for GmailApp.sendEmail().

A work-around is proposed in StackOverflow:

http://stackoverflow.com/a/18727687/1677912

jo...@gmail.com <jo...@gmail.com> #5Feb 22, 2019 05:19AM

Are there any news on adding the ability to archive and add a label to specific emails (not threads)? From a corporate shared mailbox perspective auto threading emails by subject is a serious issue (eg. we recive two emails from the same person with same subject but with different description).

Since it's available in pure mailbox view is that such a big effort to make it available also in Google Script?

sy...@gmail.com <sy...@gmail.com> #6Mar 21, 2019 04:25PM

Looking forward to having this implemented. As has been mentioned automatic threading based on subject is a big no-no for our enterprise. We get automated reports and other documents sent to us by customers and suppliers and they are lumped together in threads making it very difficult for me to let Apps Script process them automatically since labels (i.e. outlook folders) have to be applied to entire threads (even though the messages in these threads often need to be treated differently).

th...@gmail.com <th...@gmail.com> #7Apr 8, 2019 06:25AM

Please add this function (and message.getlabel too) we need to scan message not only the thread.

sa...@saket.me <sa...@saket.me> #8Aug 14, 2019 05:55PM

Will there be any progress on this issue? Threading is great for humans, but if you are scripting, accessing and manipulating individual messages is MUCH more important, especially if it can be done from the normal user interface. Anything you can do to the thread you should be able to do at the message level.

xa...@google.com <xa...@google.com> #9Oct 11, 2019 06:15PM

Unassigning

sa...@saket.me <sa...@saket.me> #10Jun 18, 2020 05:47PM

Activate advanced google services/gmail api and use the gmail api functions.
I have resolved the same issue :)

jr...@squareup.com <jr...@squareup.com> #11Jul 9, 2020 12:45AM

Thanks!

mr...@gmail.com <mr...@gmail.com> #12Jul 9, 2020 12:34PM

The advanced service provides this functionality.

rp...@google.com <rp...@google.com> #13Aug 21, 2020 10:01PM

See b/149629363#comment6 for a workaround (i.e. download the SDK corresponding to the device API level, and Android Studio should show the correct source from that API level).

Message last modified on Aug 21, 2020 10:01PM

jr...@squareup.com <jr...@squareup.com> #14Aug 21, 2020 10:14PM

I can confirm the workaround suggested in #13 does not work as of Android Studio 4.0.1.

In the attached screenshots, I use a Pixel 2 emulator running API 25 and set a breakpoint in the four-arg constructor of TextView which in API 25 sources maps to line 710.

Note that the breakpoint hit on line 710 in API 29 sources, which maps to the mAllowTransformationLengthChange field.

I just noticed

https://issuetracker.google.com/issues/149629363#comment10. Will now try with a non-Pixel 2 emulator running API 25.

Screen Shot 2020-08-21 at 6.11.09 PM.png

246 KB

View

Download

Screen Shot 2020-08-21 at 6.11.15 PM.png

75 KB

View

Download

Screen Shot 2020-08-21 at 6.11.22 PM.png

18 KB

View

Download

jr...@squareup.com <jr...@squareup.com> #15Aug 21, 2020 10:20PM

Non-Pixel 2 emulator also exhibits the same problem.

sp...@google.com <sp...@google.com> #16Feb 4, 2022 04:46AM

Is this problem still reproducible in Studio Bumblebee?

th...@gmail.com <th...@gmail.com> #17Feb 4, 2022 04:56AM

why dont you try to reproduce it.

an...@crowdstrike.com <an...@crowdstrike.com> #18Mar 10, 2022 02:26PM

Yes, it is still reproducible in Bumblebee 2021.1.1 Patch 2

an...@google.com <an...@google.com> Sep 8, 2022 05:40PM

Reassigned to an...@google.com.

an...@google.com <an...@google.com> Sep 12, 2022 11:42PM

Accepted by an...@google.com.

an...@google.com <an...@google.com> #19Sep 28, 2022 05:28PM

Marked as fixed.

A fix has been made for this and is available in Flamingo 2022.2.1 Canary 2.

lo...@gmail.com <lo...@gmail.com> #20Sep 29, 2022 10:30AM

Pretty cool that you managed to pull this off, I thought it'd be almost impossible to implement. I'm curious about how you made it work, and if it changes anything for us besides providing the matching sources for debugging… any requirements to use it?

an...@google.com <an...@google.com> #21Sep 29, 2022 06:03PM

There are no special requirements to take advantage of this. Messaging in the editor should now let you know when you're missing AOSP sources for the API level of the device being debugged, and offer to download them in that case. Additionally, debug sources that do not match the debug device's API level will no longer be opened at all when debugging into the SDK, to reduce confusion.

Issue 74128300

Description

Issue summary

Comments

jo...@gmail.com <jo...@gmail.com> #2Mar 4, 2018 05:44AM

uc...@google.com <uc...@google.com> #3Mar 7, 2018 08:06PM

jo...@gmail.com <jo...@gmail.com> #4May 30, 2018 08:41PM

jo...@gmail.com <jo...@gmail.com> #5Feb 22, 2019 05:19AM

sy...@gmail.com <sy...@gmail.com> #6Mar 21, 2019 04:25PM

th...@gmail.com <th...@gmail.com> #7Apr 8, 2019 06:25AM

sa...@saket.me <sa...@saket.me> #8Aug 14, 2019 05:55PM

xa...@google.com <xa...@google.com> #9Oct 11, 2019 06:15PM

sa...@saket.me <sa...@saket.me> #10Jun 18, 2020 05:47PM

jr...@squareup.com <jr...@squareup.com> #11Jul 9, 2020 12:45AM

mr...@gmail.com <mr...@gmail.com> #12Jul 9, 2020 12:34PM

rp...@google.com <rp...@google.com> #13Aug 21, 2020 10:01PM

jr...@squareup.com <jr...@squareup.com> #14Aug 21, 2020 10:14PM

jr...@squareup.com <jr...@squareup.com> #15Aug 21, 2020 10:20PM

sp...@google.com <sp...@google.com> #16Feb 4, 2022 04:46AM

th...@gmail.com <th...@gmail.com> #17Feb 4, 2022 04:56AM

an...@crowdstrike.com <an...@crowdstrike.com> #18Mar 10, 2022 02:26PM

an...@google.com <an...@google.com> Sep 8, 2022 05:40PM

an...@google.com <an...@google.com> Sep 12, 2022 11:42PM

an...@google.com <an...@google.com> #19Sep 28, 2022 05:28PM

lo...@gmail.com <lo...@gmail.com> #20Sep 29, 2022 10:30AM

an...@google.com <an...@google.com> #21Sep 29, 2022 06:03PM

Add comment

Issue metadata