New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 838283 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2018
Cc:
agrieve@chromium.org
█ nyquist@chromium.org
█ wnwen@chromium.org
estevenson@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Consider compiling small targets to get rid of red underlines for android calls

Project Member Reported by wnwen@chromium.org, Apr 30 2018 
See this CL for context: https://chromium-review.googlesource.com/c/chromium/src/+/1031052

We may be able to have annotations and android methods work while having the actual ids w/red underlines by allowing certain generated targets but not the android resources ones.

Comment 1 by estevenson@chromium.org, May 2 2018 

I think the biggest problem is that we're missing the support library classes.

Ex. AsyncInitializationActivity extends AppCompatActivity but Studio doesn't know about our AppCompatActivity without passing --full, so all of the Activity methods we use in AsyncInitializationActivity show as errors.

I think this happens because prebuilts are treated as generated files? Maybe we can adjust this or even just whitelist the targets we need?

Comment 2 by wnwen@chromium.org, May 24 2018

Cc: wnwen@chromium.org
Owner: ----
Status: Available (was: Assigned)
Making this available since it is a tradeoff between fast by default and occasionally running --full.

Comment 3 by estevenson@chromium.org, May 25 2018

Status: WontFix (was: Available)
Let's just close this one off - I think that my Android Studio was in a bad state when I tested this out and it's simpler to leave it as-is.
►

Sign in to add a comment