Issue Checklist
Additional terms
Feature description
Currently, build output logs in AndroidIDE (Code On The Go) display errors and warnings as plain text. These logs often include file paths, line numbers, and error types, but they are not interactive.
Example:
/path/to/file/MediaRepository.java:67: error: incompatible types
The proposed feature is to automatically detect such patterns in build logs and make them clickable. When a user taps on a log line:
- The IDE should open the corresponding file
- Navigate to the exact line number
- Place the cursor on that line (optionally highlight it)
This behavior should work for both errors and warnings, and support common compiler outputs (javac, kotlinc, Gradle).
Use Case
When developing on mobile:
- A user runs a build and gets multiple errors/warnings
- Instead of manually locating files and lines, the user taps directly on a log entry
- The IDE instantly opens the file at the exact location of the issue
Example flow:
- Build fails with:
QueueAdapter.java:83: warning
- User taps the line
- IDE opens "QueueAdapter.java" at line 83 with cursor focused
This is especially useful on small screens where navigation is slower and less precise.
Suggested Implementation Ideas
Use regex like:
(.+.java):(\d+):\s+(error|warning):
- Attach click spans to matched lines
- Integrate with editor navigation API:
- openFile(path)
- goToLine(line)
Additional Enhancements (Optional)
- Error panel with grouped issues
- Filter: Errors / Warnings
- Tap to cycle through errors
- Inline annotations in editor
(Reference or example images creating by ai)
Benefits
- ⚡ Faster debugging – No manual searching for files and line numbers
- 📱 Mobile-friendly workflow – Reduces friction on small screens
- 🎯 Improved accuracy – Direct navigation to exact issue location
- 🧠 Better developer experience – Similar to Android Studio / VS Code
- 🚀 Productivity boost – Quickly jump between multiple errors
🙏 Summary
Making build log errors clickable with automatic navigation will significantly enhance the usability of AndroidIDE for on-device development.
Issue Checklist
Additional terms
Feature description
Currently, build output logs in AndroidIDE (Code On The Go) display errors and warnings as plain text. These logs often include file paths, line numbers, and error types, but they are not interactive.
Example:
/path/to/file/MediaRepository.java:67: error: incompatible types
The proposed feature is to automatically detect such patterns in build logs and make them clickable. When a user taps on a log line:
This behavior should work for both errors and warnings, and support common compiler outputs (javac, kotlinc, Gradle).
Use Case
When developing on mobile:
Example flow:
QueueAdapter.java:83: warning
This is especially useful on small screens where navigation is slower and less precise.
Suggested Implementation Ideas
Use regex like:
(.+.java):(\d+):\s+(error|warning):
Additional Enhancements (Optional)
(Reference or example images creating by ai)
Benefits
🙏 Summary
Making build log errors clickable with automatic navigation will significantly enhance the usability of AndroidIDE for on-device development.