Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot download/update to ios version 12.2.0 due to missing file #238

Open
Mataboge opened this issue May 1, 2022 · 6 comments
Open

Cannot download/update to ios version 12.2.0 due to missing file #238

Mataboge opened this issue May 1, 2022 · 6 comments

Comments

@Mataboge
Copy link

Mataboge commented May 1, 2022

Tried updating to the latest version 12.2.0, visual studio complains about not finding the file below. Tried to manually edit the .csproj and do a restore (cleared cache, restore on command line), it give the error below when i build. I went to the specified path i realised that the file 'arm64-apple-ios-simulator.swiftdoc' is not there. how do i proceed?

The Error message
Error occurred while restoring NuGet packages: Could not find a part of the path 'C:\Users\UserName\.nuget\packages\xamarin.facebook.sharekit.ios\12.2.0\lib\xamarinios10\Facebook.ShareKit.resources\FBSDKShareKit.xcframework\ios-arm64_i386_x86_64-simulator\FBSDKShareKit.framework\Modules\FBSDKShareKit.swiftmodule\arm64-apple-ios-simulator.swiftdoc'.

@Mataboge
Copy link
Author

@SotoiGhost

@facilityweb
Copy link

I have the same issue,

@facilityweb
Copy link

I fixed this issue, updating the nugget package in visual studio for mac. The reference is found there

@olivertech
Copy link

Hi there,
I am facing with this problem yet... neither from VS or command line. The error is below, when I try to install Xamarin.Facebook.iOS 12.2.0.1:

Severity Code Description Project File Line Suppression State
Error Could not find a part of the path 'C:\Users\marcelo_oliveira.nuget\packages\xamarin.facebook.sharekit.ios\12.2.0.1\lib\xamarinios10\Facebook.ShareKit.resources\FBSDKShareKit.xcframework\ios-arm64_i386_x86_64-simulator\FBSDKShareKit.framework\Modules\FBSDKShareKit.swiftmodule\arm64.swiftinterface'.

Is I install all the libraries asked to install (4), I cant update as well... So, How to update it ??? I thing we have here a real problem... I need to update to be able to use our app in iOS 14.

Any perspective to solve that ?

Thanks.

@kevin-hine-innis
Copy link

kevin-hine-innis commented Oct 11, 2022

I can't say this is your problem, but something that could be a problem on windows: https://superuser.com/questions/1119883/windows-10-enable-ntfs-long-paths-policy-option-missing
Windows by default doesn't allow file names and paths greater than 256 characters, which your paths are.

The easiest way to test this is to move your nuget directory to the root of your C:\ drive and see if that fixes the issue.
https://stackoverflow.com/questions/4092759/is-it-possible-to-change-the-location-of-packages-for-nuget

I hope this helps.

p.s.
For some packages (not this one), I have only been able to install them from VS for Mac. No idea why.

@johbake
Copy link

johbake commented Jan 9, 2023

directory length definitely seems to be a problem. I got around many failures by shortening my path to "C:.npak" but now it's failing on:

System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:.npak\xamarin.facebook.gamingserviceskit.ios\12.2.0.1\lib\net6.0-ios15.4\Xamarin.Facebook.GamingServicesKit.resources\FBSDKGamingServicesKit.xcframework\ios-arm64_armv7\FBSDKGamingServicesKit.framework\Modules\FBSDKGamingServicesKit.swiftmodule\armv7-apple-ios.swiftdoc'.

That path is 272 characters so there's no way this'll install on Windows since I can't make my path much shorter.

Is the nuget package Xamarin.Facebook.iOS restricted to only being installed on Macs? If so, that needs to be documented. If not, this will need to be addressed and, hopefully, include more Windows testing because this clearly hasn't ever been tried. I'd also hope that, if you're fixing this, you fix all the other long path issues, if possible, because having all users modify their default nuget path is rough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants