Hey everyone, I’m having a weird problem with the Google Relay plugin in Android Studio. I successfully imported my Figma design file using Relay version 0.3.10-hotfix, and everything seems to work during the import process. No error messages or anything like that.
The strange thing is that while the import appears successful, I can’t see the generated UI components in my project’s Android view. When I navigate to the actual file path though, the UI package files are definitely there.
I tried a few things to fix this:
Deleted the UI package files and reimported
Used “Reload from Disk” on the project root folder
Switched between different project views
What’s really puzzling me is that when I test with the sample Figma files and projects from the official Android documentation, everything works perfectly. The UI components show up right where they should be. But with my own custom Figma file and Android project, this visibility issue happens every time.
Has anyone else run into this problem? Is there some project configuration or Figma file setup that I might be missing?
Been dealing with this exact headache for months at work. The real problem isn’t just Android Studio being finicky - it’s that you’re stuck in this manual workflow that breaks every time something goes wrong.
You need to automate this entire Figma to Android pipeline. I set up a workflow using Latenode that monitors my Figma files for changes and automatically handles the import process without all these visibility issues.
The workflow pulls design updates from Figma API, processes the components through proper validation checks, and pushes them directly to the right directories in your Android project. No more wondering if files are there but not showing up.
Plus you get error handling that actually tells you what went wrong instead of guessing. When component names are invalid or paths are messed up, you get clear notifications instead of silent failures.
I’ve saved probably 10 hours a week just by not babysitting this import process anymore. The automation handles all the gradle syncing and file organization automatically.
check your figma file structur. you’ve probably got components nested too deep or auto-layout properties that relay cant parse. the files generate fine but android studio marks them as invalid resources, so they wont show up in project view. try flattening your component hierarchy in figma first.
Had this exact problem with Relay 0.3.10 two weeks ago. It’s a source sets issue in your module’s build.gradle file. When Relay generates UI components, they need to be in your source directories or Android Studio won’t see them during indexing. Check if the generated package path matches what’s in your sourceSets block. For me, Relay was generating files in a subdirectory that Android Studio’s indexer wasn’t scanning. I manually added the generated UI package path to java.srcDirs in my build.gradle. After that and a clean rebuild, the components showed up correctly in project view. Since sample projects work, your Relay setup’s fine - there’s just a mismatch between where the plugin generates files and where your project looks for source code.
This happens because Android Studio can’t recognize the generated code properly. I hit the same problem on a big multi-module project - the files were in the right folder but Studio didn’t see them as part of the module’s source tree. Check your Project Structure dialog to see where Relay’s actually putting the components. Sometimes it generates them in a “technically correct” spot that’s outside your current module. Also, make sure you don’t have custom source directory configs messing things up. For me, the fix was getting the UI package generated directly under the main source set instead of some random subdirectory. Clean and rebuild after you’ve confirmed the source paths - that usually fixes the indexing issue.
yep, sounds like a gradle sync issue. try going to the file menu and hit “invalidate caches & restart”. that usually solves those visibility problems in android studio where the files are there but not showing up.
This happens when Android Studio’s indexing system doesn’t recognize the generated files. I ran into the same thing with Relay last month. Turns out my custom Figma components had names that broke Android’s resource naming rules. Check if your Figma layers have special characters, spaces, or start with numbers - that’ll mess up the indexing even though the files exist. Also make sure your app module’s build.gradle has the Relay plugin set up right and the generated UI package is in the correct source directory. Try a manual gradle sync after you’ve checked the file structure - that usually fixes the indexing issue.