Search Issue Tracker

Active

Under Consideration for 1.11.X

Votes

5

Found in [Package]

1.11.2

Issue ID

ISXB-1203

Regression

No

"error CS1061: 'InputAnalytics.IInputAnalytic' does not contain a definition for 'TryGatherData'" is thrown when rebuilding Addressable Assets Cache

Package: Input System

-

How to reproduce:
1. Open the attached project "AddressableError.zip"
2. Open Window>Asset Management>Adressables>Groups
3. Click Build>New Build>Default Build Script in the Addressables Groups window

Expected results: Build is successful
Actual results: "error CS1061: 'InputAnalytics.IInputAnalytic' does not contain a definition for 'TryGatherData'" is thrown

Reproducible with: 1.9.0 (2021.3.46f1), 1.11.2 (2021.3.46f1, 2022.3.52f1, 6000.0.27f1, 6000.1.0a5)
Not reproducible with: 1.8.2 (2021.3.46f1)

Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested

Comments (7)

  1. acesgamedevelopment

    Nov 18, 2024 13:50

    Yeah, downgrading to 1.8.2 worked for me as well.
    To downgrade, you have to go via the changelog website and then add the older version to your project. It took me a while to find out how to do it at first.

  2. eiwzkart

    Nov 02, 2024 13:25

    It should be Input system package issue, the only way to fix is downgrading it to 1.8.1 or 1.8.2

  3. ScionOfDesign

    Oct 26, 2024 23:04

    Fix the issue by deleting and regenerating "UnityConnectSettings.asset"

  4. TheJavierD

    Sep 19, 2024 17:29

    I fixed my issue by removing the analytics library
    native input library was using it and that's where the error was

  5. TheJavierD

    Sep 19, 2024 17:23

    I have the same issue but how do you even downgrade packages?
    On Unity 6 and input system is 1.10.0

  6. XEDORA

    Sep 02, 2024 13:43

    I'm having the same issue with Input System 1.9.0 and newer. Downgrading to 1.8.2 solved it. (Using Unity 6000.0.17f1, macOS)

  7. SwingWren

    Aug 12, 2024 14:24

    I think the categorization of the issue is wrong? I found the issue to be located in the Input package version 1.9.0. After downgrading to 1.8.2 the problem disappears.
    (Using Unity 6000.0.14f1 DX11)

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.