question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Updating to 1.4.0 from 1.3.0 fails with with Unity 2020.1.17

See original GitHub issue

Describe the bug Updated my project from 1.3.0 to 1.4.0 with Unity 2020.1.17 and not all of my sources are compiled

To Reproduce Can’t really

Expected behavior All sources compile

Screenshots image

Environment (please complete the following information):

  • Version 1.4.0
  • Platform: Editor/Windows
  • Unity version: 2020.1.17
  • Build options: .Net 4.x

Additional context The problem might come from the fact that we are using external .cs files added as unity packages. We have several projects included like:

[package.json]
"bimvisualizer.shared": "file:../../BimVisualizer.Shared",

These point to folders with .net standard 2.0 projects (which are using C#9.0) (also the bin and obj folders are renamed to .bin and .obj so unity will not try to use the dlls inside them). The errors seem to only come from one project where c# 9 and 8 are used, and not from the unity project.

Should I include another folder for assemblies in the settings?

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
mob-sakaicommented, Jan 6, 2021

👍

Also could you provide some documentation on this in the readme?

Sure.

1reaction
mob-sakaicommented, Jan 6, 2021

@KuraiAndras

Check name field in bimvisualizer.shared/package.json and bimvisualizer.application/package.json.

For example:

[bimvisualizer.shared/package.json]
{
  "name": "com.bim.visualizer.shared",
  "version": "1.0.0",
  ...
}

and

[bimvisualizer.application/package.json]
{
  "name": "com.bim.visualizer.application",
  "version": "1.0.0",
  ...
}
  • Remove !Packages/
  • Add Packages/com.bim.visualizer.shared
  • Add Packages/com.bim.visualizer.application

Also why is the Packages folder excluded by default?

This is to prevent unintended compiler changes and to minimize the impact of compiler changes. Packages and store assets should (essentially) be compiled with the default compiler.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Resolved - Unable to start Oculus XR Plugin
I tried using oculus version 1.4.0, same error. I have the Oculus assets from the asset store in the project, and I updated...
Read more >
Unity 2020.1.0
IAP: Unity purchasing gives error on project upgrade due to failing to find UnityEngine.UI assembly (1193773).
Read more >
Unity 2021.3.7
Send on Windows. Package Manager: Fixed an issue where some PackageInfo properties would not be populated correctly if the package came from a ......
Read more >
Unity 2023.1.1
Editor Window Management: 2D projects created with versions from 2023.1.0a25 to 2023.1.0b4 fail to upgrade to 2023.1.0b9 and later ...
Read more >
Unity 2023.1.0
Editor: Fixed an issue where a UnityException ("Could not find the requested Platform ... Multiplayer: Added Netcode for GameObjects 1.4.0.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found