Search Issue Tracker

Fixed in 2022.2.X

Fixed in 2021.2.X, 2022.1.X

Votes

32

Found in

2021.1.11f1

2021.1.12f1

2021.2.0a4

Issue ID

1345099

Regression

No

Only some assemblies fail to be loaded when assembly name does not match the file name

Scripting

-

How to reproduce:
1. Open the attached project's "case_1345099-Project.zip" Scene labeled "SampleScene"
2. In the Project Window, re-import the included DLL files
3. Wait for the re-import process to finish
4. Observe the Console Window
5. Rename Assemblies that didn't throw an error
6. Re-import the Assemblies again
7. Observe the Console Window

Expected result: Errors are thrown for all Assemblies that have mismatching names
Actual result: 'Assembly name does not match file name' error is thrown only for a single Assembly

Reproducible with: 2021.1.11f1, 2021.1.14f1, 2021.2.0a4, 2021.2.0b1
Not reproducible with: 2019.4.28f1, 2020.3.14f1, 2021.1.10f1, 2021.2.0a3 (No errors are thrown)

  1. Response avatar

    Resolution Note (fix version 2022.2):

    Fixed in: 2022.2.0a4

  2. Response avatar

    Resolution Note (fix version 2022.1):

    Fixed in: 2022.1.0b11

  3. Response avatar

    Resolution Note (fix version 2021.2):

    Fixed in 2021.2.16f1

Comments (6)

  1. 8139987a7b6bafbe9305d2e594dadf9f?d=mm

    mikaelK

    Mar 02, 2022 16:54

    Updated unity from .9f to .13f and now my scripts can't find assemblies and types.
    Previously did work.

  2. 2a0495093dfbc6e666824cd2371ae14c?d=mm

    MidnightCoffeeInc

    Nov 15, 2021 18:25

    Just want to comment that this issue is singlehandedly preventing me from using 2021.2, which has some features my project needs :(
    It's breaking because I'm using Firebase.
    https://github.com/googlesamples/unity-jar-resolver/issues/441

  3. E23a2039e35c7da7ede02b8f4c68189a?d=mm

    Volcore

    Sep 20, 2021 14:02

    Any updates on this? It's been a major blocker to adopting any new version since 2021.1.10f1.

  4. F4e7df924954601a9fdad50317faa5a5?d=mm

    ThainaYu

    Aug 20, 2021 05:10

    This is seriously waste my time. My editor code on cloud build was fail to run for week and I just found this was the root cause

  5. Af6d1054c297e79d586c2926b365ba82?d=mm

    chkuang

    Jul 07, 2021 18:06

    Instead of throwing error for all assemblies that have mismatching names, perhaps loosen the rules like it used to be? Or perhaps just makes it as a warming?

    What is the reason behind enforcing the naming rule?

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.