Unable to update from 2.0.4 to 3.0.0

[RsZoli]

When i'm trying to update the NuGet from 2.0.4 to 3.0.0 i got the following error:

System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\.nuget\adame.firebase.ios.core\10.24.0\lib\net6.0-ios16.1\Firebase.Core.resources\FirebaseCoreInternal.xcframework\ios-arm64_x86_64-simulator\FirebaseCoreInternal.framework\Modules\FirebaseCoreInternal.swiftmodule\arm64-apple-ios-simulator.private.swiftinterface'.

There is only one file at that path:

The downloads are finishing okay as far as i can tell:

GET https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/index.json
OK https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/index.json 296ms
CACHE https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/index.json
GET https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/10.24.0.1/adame.firebase.ios.core.10.24.0.1.nupkg
OK https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/10.24.0.1/adame.firebase.ios.core.10.24.0.1.nupkg 99ms
CACHE https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/10.24.0.1/adame.firebase.ios.core.10.24.0.1.nupkg
GET https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/10.24.0/adame.firebase.ios.core.10.24.0.nupkg
OK https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/10.24.0/adame.firebase.ios.core.10.24.0.nupkg 59ms
CACHE https://api.nuget.org/v3-flatcontainer/adame.firebase.ios.core/10.24.0/adame.firebase.ios.core.10.24.0.nupkg

[AdamEssenmacher]

Probably this: https://github.com/TobiasBuchholz/Plugin.Firebase?tab=readme-ov-file#troubleshooting

[RsZoli]

@AdamEssenmacher sadly, no! this is my full path: "c:.nuget\adame.firebase.ios.core\10.24.0\lib\net6.0-ios16.1\Firebase.Core.resources\FirebaseCoreInternal.xcframework\ios-arm64_x86_64-simulator\FirebaseCoreInternal.framework\Modules\FirebaseCoreInternal.swiftmodule"

It is only 216 characters!

[AdamEssenmacher]

Is the file actually there?

[RsZoli]

@AdamEssenmacher No, its not! Thats why i included a screenshot of the folder!

[AdamEssenmacher]

OK.

C:\.nuget\adame.firebase.ios.core\10.24.0\lib\net6.0-ios16.1\Firebase.Core.resources\FirebaseCoreInternal.xcframework\ios-arm64_x86_64-simulator\FirebaseCoreInternal.framework\Modules\FirebaseCoreInternal.swiftmodule\arm64-apple-ios-simulator.private.swiftinterface

is 265 characters. This is almost definitely the long file path issue I liked above.

https://github.com/TobiasBuchholz/Plugin.Firebase?tab=readme-ov-file#troubleshooting
dotnet/maui#17828
https://developercommunity.visualstudio.com/t/Allow-building-running-and-debugging-a/351628

[RsZoli]

@AdamEssenmacher You are right, i'm sorry! I was lazy and asked the ChatGPT regarding how many characters it has!

However i have long path enabled, i encountered this anomlaly before! So if you can tell me how i can i download the files needed manually, i'll just do that!

Thank you!

[AdamEssenmacher]

Getting past the long path issue involves several steps, including clearing your local nuget caches and ensuring that your initial package restores are done via command line. These are well documented in the MAUI issue linked above.

[RsZoli]

@AdamEssenmacher I don't need help with the long path issue, i just said in my last post that i already have long path enabled! :(

I need that missing file so i can update this NuGet package! Anyway, i'll figure it out somehow!

[AdamEssenmacher]

The file didn't get extracted because of the long file path issue.

[RsZoli]

Well i managed to update the NuGet, shortened the path even more, now the missing file is indeed there, however the project won't build:

C:\.n\xamarin.build.download\0.11.4\buildTransitive\Xamarin.Build.Download.targets(52,3): error : Could not find 7zip.exe in Xamarin installation

[Skarzag]

We have the same problem on our project, It work with Android but not with iOS.
I tried a lot of workaround suggested here and there.

• With dotnet restore command in command terminal i got the same message as @RsZoli about 7zip.exe
• With Visual Studio debug, the build process seems to be stucked here
  

Hope we'll find reliable and definitive solution soon because this package is an not far from an essential