IssueTracker

Thanks for the report! I believe this has already been fixed in 3.6, but without concrete repro steps I can't confirm. Can you add any additional details? Or, would you mind downloading the latest canary and seeing if the problem still exists there?

Just tried it 3.6 and I'm seeing the same behavior. I've attached a sample project.

In the project:
- There are 3 modules :app, :blue and :red
- :app implements :blue and :red
- :blue and :red are independent modules, they have no dependencies on other modules
- Each module has a single activity and layout
- The activity in :blue (BlueActivity) is marked as `internal`

My observations:
(1) A class is visible in auto-complete despite lack of dependencies on the module containing that class.
------ ex. class RedActivity is visible in :blue layout
(2) A class is visible in auto-complete despite being internal
------ ex. internal class BlueActivity is visible in :app and :red layouts

---

Android Studio 3.6 Canary 12
Build #AI-192.6262.58.36.5871855, built on September 12, 2019

Thank you for the additional details and sample project! I've accepted this to make sure I won't lose track of it, but it will be at least a few days before I can get to it.

Thanks for your patience. Taking a look now.

Thank you OP for attaching your project. It really helped with chasing down this issue.

A fix for this should land in 4.0 Canary 5.

Nice, thanks for taking care of that one. I've since switched back to just a single module project.. but I'm sure this will be helpful for devs with larger projects.