A newly created services in an empty project is failing to build. V 4.0.3

[mhijaziB]

Describe the Bug

After creating a new service using the Beam Services window in Unity and opening the service, building it fail.
Building throws the following error:

PotatoService.csproj: Error NU1105 : Unable to find project information for 'C:\Unity\Repos\Beam-Sdk-4\Library\BeamableEditor\GeneratedProjects\Unity.Beamable.Customer.Common\Unity.Beamable.Customer.Common.csproj'. If you are using Visual Studio, this may be because the project is unloaded or not part of the current solution so run a restore from the command-line. Otherwise, the project file may be invalid or missing targets required for restore. 0>------- Finished building project: PotatoService. Succeeded: False. Errors: 1. Warnings: 0

I was able to fix this by using the following command inside the service's folder: dotnet restore PotatoService.csproj

To Reproduce

Steps to reproduce the behavior:

1. Go to Beam Service Window
2. Click on Create new service
3. Open the service and build
4. See error

Expected Behavior

Building a newly created service should work without restoring the service.

Note from Chris:

The project is complained about, Unity.Beamable.Customer.Common.csproj, is generated from within Unity to mirror the associated .asmdef file.
Perhaps what is happening is a race condition where that project gets generated AFTER the restore for the whole PotatoService finishes.

Metadata

• SDK version: 4.0.3
• Engine version: Unity 6.2
• Operating System: Windows 11

[cdhanna]

I'd start by taking a look at the beam project build / beam project run commands to see if they are implicitly restoring, or maybe even explicitly calling things with the --no-restore flag.

[DiasAtBeamable]

I'd start by taking a look at the beam project build / beam project run commands to see if they are implicitly restoring, or maybe even explicitly calling things with the --no-restore flag.

Neither one of those Commands implicity calls dotnet restore.

Should we implicitly do this or improve our error message?

@cdhanna

[DiasAtBeamable]

Moe also couldn't reproduce this issue again.

[DiasAtBeamable]

Closing it as a no-repro.