When Rider Forgets How to Write Assembly Definitions: My Day-Long Fight With UnityAtoms
Yesterday, adding a dependency in Jetbrains Rider was a non-event: type the class name, hit Alt+Enter , keep coding. Today, the exact same shortcut quietly stopped writing anything to my .asmdef file and it took me a full day to even understand what was going on, let alone fix it. For context: right now, I'm working on a flexible selection system for my game The Weight of One: The Jovarko…
Yesterday, using JetBrains Rider to add a dependency was seamless. Typing the class name and hitting Alt+Enter would import the reference and code could continue. Today, the same shortcut stopped writing to my .asmdef file, and it took a full day to figure out why. My project contains several modules, each with its own Assembly Definition: Core.asmdef, Systems.asmdef, UI.asmdef, Data.asmdef.
I recently added UnityAtoms through the Package Manager and wanted to use types like AtomEvent and AtomValueList from the Data module. My attempt to resolve the unresolved type in Rider worked momentarily but failed again when I switched focus back to the Unity Editor. I tried every standard fix, including invalidating caches, regenerating project files, and cleaning out the Library folder, but nothing worked.
I eventually resolved the issue by manually editing the Assembly Definition file in Rider. This bug affects other users too, as evidenced by the YouTrack issue RIDER-94834. While JetBrains is aware of the problem, the UI does not indicate that the import was not successfully applied on disk. This lack of feedback is frustrating for developers.
I've opened a thread on the Rider support forum, and I encourage others experiencing this issue to upvote and comment to draw attention to the problem.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
