[BadRequest] Bad request: Invalid normcore version
I updated to the latest version, migration succeeded, but I still seem to be stuck on the old rooms, even with new names. How can I make sure my normcore version is up to date?
KHi @Alix Ollivier. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. 
K----------------------
The knowledge sources don’t explicitly describe the error, so I can’t give a definitive, documented fix. However, there are a few things we can verify from the docs and typical Normcore setup.
The knowledge sources don’t explicitly describe the error, so I can’t give a definitive, documented fix. However, there are a few things we can verify from the docs and typical Normcore setup.
- **Confirm you’re actually running Normcore 2 (not 1)** After upgrading, your project should only contain the Normcore 2 package (via the Normal scoped registry) and *no* old Normcore 1 files. The official upgrade guide explicitly requires deleting the old `Normal/Realtime` folder after importing Normcore 2, then restarting Unity and running the migration. [[Upgrading guide](<https://docs.normcore.io/guides/upgrading-from-normcore-1-to-normcore-2>)]
- In your project, check that:
- The Normal/Realtime folder from Normcore 1 is gone.
- Normcore appears in Package Manager → My Registries, coming from the Normal scoped registry. [Normal registry]
- In your project, check that:
- **Make sure you’re using a Normcore 2 app key** The docs don’t explicitly say this, but app keys are created and managed in the Normcore dashboard, and the Getting Started flow assumes you’re using a current app key from `dashboard.normcore.io`. [[Getting started](<https://docs.normcore.io/essentials/getting-started>)]
- Log into the dashboard, create a new app if needed, and copy its App Key.
- In Unity, on your Realtime component, paste that key into the App Key field.
- Ensure you don’t have any old prefabs/scenes referencing an outdated Realtime component with an old key.
K- **Check that you’re connecting correctly (Realtime vs Room)** The docs emphasize using `Realtime.Connect()` rather than calling `room.Connect()` directly. [[Room intro](<https://docs.normcore.io/room/room>)]
- In your code, you should be doing something like:
- Avoid manually constructing and calling unless you know you need the low-level API.
- In your code, you should be doing something like:
- **Use DisconnectEvent info to confirm the error type** Normcore 2 exposes detailed disconnect events. `BadRequest` is one of the documented `DisconnectEvent` subclasses. [[Disconnect subclasses](<https://docs.normcore.io/room/disconnect-events#disconnectevent-subclasses>)]
- Subscribe to and log the full event:
- This may give more detail than just “Invalid normcore version” and help confirm that the server is rejecting the client as an incompatible/old version.
- Subscribe to and log the full event:
- **Ensure there’s only one Normcore version in the project** The upgrade guide notes that having two copies of Normcore (old + new) in the project causes GUID conflicts and duplicate symbols until the old one is removed. [[Upgrading guide](<https://docs.normcore.io/guides/upgrading-from-normcore-1-to-normcore-2>)]
- Double‑check there are no leftover s or folders from an older Normcore version outside the package (e.g., in or a custom folder).
- Deleted the old folder,
- Confirmed Normcore is only coming from the Normal scoped registry,
- Updated your app key from the dashboard,
- And you still get ,
Kthen the docs don’t provide further steps. In that case, I’d recommend:
- Grabbing the full output, and
- Contacting Normal via support or Discord with that log, since this looks like a backend/client-version mismatch that isn’t fully documented in the public docs.
----------------------
Note: you can ask me a follow up question by @ mentioning me again
----------------------
K@185325614775926784 Kapa.ai is still learning and improving, please let me know how I did by reacting below.
MI was just investigating this on the backend. You're trying to connect to a quickmatch room?
MI think there's a bug here that we need to investigate.
M@Alix Ollivier there's a serious bug here, but I'm really at a loss for how it can happen. Our servers are seeing requests come from you where it's sending your appKey in the normcoreVersion field. The thing that's particularly strange is that normcoreVersion is hard coded at build time within our native plugin to be the native plugin version.
MAre you able to send us a copy of this project to look at?
Athis was like a first pass at a vibe-coded remake of my room manager, this is the only script i was affecting so I probably just wrote it wrong. When I try "Join room on start" in the realtime and select "Quickmatch" it works
NormcoreRoomManager.cs26.19KB
Mthe thing is that the bug you’re hitting should be /impossible/ no matter what you do in C#
Mafter you updated, did Normcore ask you to restart Unity?
AAHere's my cursor chat, it did end up renaming a package then reimporting then we reverted, but all this was after the initial bug that I mentioned in the first chat
Mok we figured it out! it was a backend bug that could only be triggered by using a non-default room server size
Myou should be good to go now. we've deployed the fix
AOh amazing haha! I was about to put in a lot of work to try to reinstall Normcore