Fixed
Status Update
No update yet.
Comments
tn...@google.com
Thanks for the feedback. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information when it applies if you haven’t already:
1. Android Studio version and OS type and version
2. Screenshots or videos of the issue
3. idea.log file (select Help > Show Log in Finder / Explorer)
4. Thread dumps if the issue is a freezing or non-responding UI.
For more information on what’s needed and how to obtain this information please read the guide athttps://developer.android.com/studio/report-bugs#studio-bugs
1. Android Studio version and OS type and version
2. Screenshots or videos of the issue
3. idea.log file (select Help > Show Log in Finder / Explorer)
4. Thread dumps if the issue is a freezing or non-responding UI.
For more information on what’s needed and how to obtain this information please read the guide at
sp...@google.com
1) See in my original post
2) See attached screen recording
Opened a scratch file and tried to type an "@" symbol. You can see that in the keyboard viewer
Btw this issue only occurs in text editor
3) See attached log file
How to reproduce:
- Open any project
- Open a source file
- Try to type "@"-Symbol
4) There is no freeze or stuck UI/process in AS
2) See attached screen recording
Opened a scratch file and tried to type an "@" symbol. You can see that in the keyboard viewer
Btw this issue only occurs in text editor
3) See attached log file
How to reproduce:
- Open any project
- Open a source file
- Try to type "@"-Symbol
4) There is no freeze or stuck UI/process in AS
sp...@google.com
I found out that if you remove the following shortcut, it works again. Does it make sense to set a different shortcut ?
[Deleted User] <[Deleted User]>
Comment has been deleted.
ru...@gmail.com
Comment has been deleted.
Description
Currently, with
android.lintOptions.textReport true, lint will output results to stdout when theAndroidLintTask(e.g.,lintDebug) runs, but there will be no such output if the task is up-to-date, which might mislead users to think that there are no lint issues.The desired behavior is for lint to output issues to stdout even if the task is up-to-date (or not to output anything if there are no issues - see
A possible fix would be to add a new lightweight task which would never be up-to-date and would only print the text report. I.e., change the lint build flow from this:
lintAnalyzeDebug->lintDebugto this:
lintAnalyzeDebug->lintReportDebug->lintDebugwhere the new
lintReportDebugtask is the oldlintDebugtask, and the newlintDebugis the lightweight task that is never up-to-date.Rejected alternative:
I considered modifying
AndroidLintCopyReportTaskto print out the text report, but that task will not run ifAndroidLintTaskis up-to-date. In fact, we can consider adding that task's functionality to the new lightweight lint task to properly fixPS - Thanks to Tor for noticing this issue :)