Internal build system error.

Unity Engine
1

Hello, I’m having a issue on my project, that i can’t press Play, or build, and the console only appears the following errors:

Internal build system error. Backend exited with code 2.
tundra: error: Unexpected stdin

Backend produced unparsable log entry
{“msg”:“enqueueNode”,“enqueuedNodeAnnotation”:“MovedFromExtractor Library/Bee/artifacts/mvdfrm/UnityEditor.UnityConnectModule.dll_FFB3750DB57770ED.mvfrm”,“enqueuedNodeIndex”:20,“enqueueingNodeAnnotation”:“ScriptAssemblies”,“enqueueingNodeIndex”:5}{

Sometimes this error changes, and as long as they appear, i will update here.

Info:

  • I’m using Unity 2021.3.1f1
  • I have Firebase integrations on my project
  • The error started for a co-worker as soon as we updated to unity 2021.3.1f1, and he managed to resolve updating the Firebase to version 9.0.0, and that was the moment that i started getting the error (Not sure if the firebase have something to do with it)
  • My folders names are according to ASCII and there is no special characters or spaces
  • The error appears always after the project is recompiled (Script edition or builds)

What I tried to do:

  • Delete library
  • Delete Bee folder in library
  • Re-clone the project
  • Use another unity version (2021.3.3f1), (2022.3.1f1)
2

I am on firebase 9 and I have the same issue. One thing of note is I am on MacOS Mojave 10.14.6. I ran a similar version of my project on Monterey and did not have this issue during the build process. However, running the built game on Mojave had an issue.

3

I installed the python 3 on my MacOS and forced it to be the main python, that solved the problem for like 2 hours or so, and after a restart that i needed to do, it broke again…

4

Could you file a bug report on this? We’ve been trying to hunt down these for a while - it seems there are some corner cases that make that happen.

5

Done,
CASE IN-5193

1 Like
6

stupid question, but how can i find the bug based on that case #, so i can upvote and track it?

7

Hi,
I had the same issue using Firebase 8.7.0, I just upgraded to the latest Firebase 9.3.0 and the bug is gone.

Unity 2021.3.3f1 / macOS 12.4 / M1 chip

8

will this be resolved with the old firebase version?

9

I also met this problem today. At first, I did the same thing as the host, but it didn’t have any effect. Later, I just had to restart my computer because of the incompatible hardware of my computer.

10

For anyone who finds this thread I recommend going to this one instead:

It’s a more complete thread with more people, and possible solutions.