Library\PackageCache\[email protected]\Runtime\UGUI\UI\Core\Dropdown.cs(734,24): error CS0103: The name ‘ListPool’ does not exist in the current context

[thekrocker]

Checklist

• I've updated to the latest released version of the SDK
• I've searched for existing GitHub issues
• I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group
• I've read the Code of Conduct
• This issue is not security related and can safely be disclosed publicly on GitHub

Environment

Describe your dev environment here, giving as many details as possible. If you have them, make sure to include:

• Unity Editor Version: 6000.0.29
• Unity SDK Version: 17.0.1
• Installation Platform & Version: Android

Goals

What do you want to achieve?
I want to install Facebook Unity SDK Succesfully.

Expected Results

What do you expect to happen?

• Having no compile errors

Actual Results

After installing Facebook SDK, it conflicts with ugui of Unity because of Dropdown class.

Library\PackageCache\com.unity.ugui@2.0.0\Runtime\UGUI\UI\Core\Dropdown.cs(734,24): error CS0103: The name ‘ListPool’ does not exist in the current context

What actually happened? Can you provide a stack trace?
It conflicted with Unity's UGUI package.

Steps to Reproduce

What are the steps necessary to reproduce this issue?

• Download Facebook, Import to Unit.

Solution & Details

• Solution 1: to remove Library folder in Unity project folder, and re-open Unity project.
• Solution 2: Removing Unity UI in Unity Registry in the Package manager, and reinstall via clicking + icon and "com.unity.ugui".

This problem has been alive for months. I think it should be updated in in Dropdown or ListPool class in source code.

[doronn]

I just encountered this as well.
I am confused as to why the sdk even edits this unity package?

[diemonic1]

Any solutions?

[thekrocker]

Any solutions?

I have already provided solution on the text.

[EgeAtPachamama]

I have this happen whenever I import FacebooK SDK into one of our projects for the last year. Usually just closing and reopening solves the issue. @thekrocker 's solution always works if open/close doesn't solve it.