[Bug]: Could not find a part of the path

[grabnerM]

What happened?

I tried to add OneSignalSDK.DotNet to my MAUI (.NET8) project. This was only possible via CLI because in VS i always got the error

"Could not find a part of the path 'C:\Users\maximilian.nuget\packages\onesignalsdk.dotnet\5.1.3\res\ios\OneSignalFramework.xcframework\ios-arm64_x86_64-maccatalyst\OneSignalFramework.framework\Versions\Current\Modules\OneSignalFramework.swiftmodule\x86_64-apple-ios-macabi.private.swiftinterface'."

This problem got already reported but every issue is marked as closed. Honestly, i don´t know why these issues got closed, but IMO is this a crucial bug.

Steps to reproduce?

1. Create a .Net 8 MAUI project
2. Try to add OneSignalSDK.DotNet

What did you expect to happen?

Correct installation of the nuget package

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[grabnerM]

Okay. Now i got the project to run at least. After installing the package via CLI you HAVE to run "dotnet restore" because damn VS is not able to do this on itself.
Still, this can´t be the way to go to use this package..

[ColdstarJoey]

Same issue for me even if i use package console, do we know how to resolve this in VS yet as i had to open the folder in Terminal and run the cli command

[mads195]

We've also seen this behavior on all workstations with the OneSignal SDK and limited to just the OneSignal SDK. Occurs during install or after git pull onto a new workstation.

Get round:
To install, use dotnet add package OneSignalSDK.DotNet
Post git pull, use dotnet restore

The error:
Error that appears if using the nuget package manager:
Error occurred while restoring NuGet packages: Could not find a part of the path 'C:\Users\MYUSER\.nuget\packages\onesignalsdk.dotnet\5.2.1\res\ios\OneSignalLiveActivities.xcframework\ios-arm64_x86_64-maccatalyst\OneSignalLiveActivities.framework\Versions\A\Modules\OneSignalLiveActivities.swiftmodule\x86_64-apple-ios-macabi.private.swiftinterface'.

[Hunv]

I also have it. I guess the path is just too long, as the path has 265 characters (for me, depends on username) and 260 is the maximum at windows.

Solution: Run this PowerShell command and reboot:
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1

Solution 2:
I sometimes have the problem even if the registry key above is set. In that case this helps:

1. Get nuget.exe from https://dist.nuget.org/win-x86-commandline/latest/nuget.exe as referenced by Microsoft here: https://learn.microsoft.com/en-us/nuget/reference/nuget-exe-cli-reference?tabs=windows
2. Change the Solution File (.sln) that the referenced nuget package has the updated version and save it.
3. Open a PowerShell Window
4. Change to your solution folder (cd C:\your\solution\path\)
5. Run c:\path\to\nuget.exe restore
6. Done

[jkasten2]

This issue happens when doing iOS builds on Windows, due to iOS frameworks using very long paths. The work around above is correct for Windows.