Search Issue Tracker

Won't Fix



Found in [Package]

preview - 1.0.0

Issue ID




Console errors appear after upgrading New Input System Package to preview 1.0.0 when using Input Action Asset

Package: Input System


How reproduce:
1. Create a new Unity project
2. Install Input System preview - 0.9.6 through Package Manager
3. Create new Input Actions Asset ( Assets -> Create )
4. Double-click newly created asset, create a new Action Map, click "Save Asset"
5. With "New Controls.inputactions" (in Project window) selected check "Generate C# Class" in the Inspector and click "Apply"
6. Update Input System to preview - 1.0.0 through Package Manager
7. Observe the console

Expected result: no errors appear in the console
Actual result: "does not contain a definition and no accessible extension method accepting a first argument could be found" errors appear in the console

Reproduced with: 2019.2.10f1, 2019.3.0b7, 2020.1.0a9
Could not reproduce with: 2017.4.33f1 (no Package Manager), 2018.4.11f1, 2019.2.0a1 ("ugui" could not be found error), 2019.3.0a1 ("InputDeviceCharacteristics" could not be found error)

- also reproduced with Input System versions lower than preview - 0.9.6, what matters is that preview - 1.0.0 update is available
- a workaround would be to delete old version C# Class and generate a new one, after the package update

  1. Resolution Note:

    I believe it's too late for it to be worth to handle this one properly (given how long the change has been out there by now) but in the future we need to handle this better. The API breakage here shouldn't have happened or should have been handled with proper script API upgrades.

    One thing that's apparent is that at least as of 2019.4, the compile error will prevent a reload of the updated input system DLL -- which it should not; there's no compile error in the package's DLL and it should get reloaded just fine. This fact prevents the newer importer from getting loading -- which would automatically fix the problem.

    However, as of 1.0 of the package we have started explicitly prevent API breakage. In future major versions, we will provide proper script API upgrades. So, I believe we're on a better path with this going forward.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.