{
  "id": 1639907,
  "title": "When Rider Forgets How to Write Assembly Definitions: My Day-Long Fight With UnityAtoms",
  "url": "https://urgent.news/2026/08/18/when-rider-forgets-how-to-write-assembly-definitions-my-day-long",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-18T05:08:47.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/giovarco/the-rider-bug-thats-probably-already-in-your-project-you-just-havent-noticed-yet-2p0c"
  },
  "original_language": "en",
  "account": "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.",
  "summary": "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…",
  "key_points": [
    "Rider stopped writing to .asmdef file after adding UnityAtoms",
    "Tried various fixes like invalidating caches and cleaning Library folder",
    "Manual edit of Assembly Definition resolved the issue"
  ],
  "editors_take": "This issue highlights a frustrating gap in JetBrains Rider's integration with Unity, where a usually seamless dependency import process fails without clear feedback, leaving developers to troubleshoot manually.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}