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 create an IOS archive... The specified path, file name, or both are too long. #105

Open
DavidLBrandt opened this issue Apr 15, 2022 · 0 comments

Comments

@DavidLBrandt
Copy link

I am working on an update to a Xamarin.Forms app In Visual Studio Community 2022 on a Windows 11 Pro machine.

I receive the following error when I try to archive the iOS project for distribution:

Cannot create an IOS archive 'XXXXXXXX.iOS'. Process cannot be executed on XMA server.
There was an error unzipping the file C:\VSArchives\2022-04-13\31a2aedc.zip: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

I have been working on this for almost a week and need a new vector of attack. Please share if you have any suggestions.

Things I have tried already (separately and combined):

  • Enable Win32 Long Paths through Local Group Policy Editor
  • Changing iOS Archives location to drive root folder
  • Setting UseShortFileNames to True in my projects PropertyGroup (XXXXXXXX.iOS.csproJ)
  • Moving my solution folder to drive root
  • Cleaning Solution, Deleting all Bin/Obj folders, rebuilding solution
  • Set LongPathsEnabled at HKLM\SYSTEM\CurrentControlSet\Control\FileSystem to 1 in Registry Editor

The archiving error began when I implemented Facebook Login using the Plugin.FacebookClient, which btw worked great except for this. When I remove this NuGet package and rem out the dependent code my solution archives again.

A zip file is being created in my archives folder on my local machine (which I can unzip without issue), and the error message say the problem is unzipping on the XMA server. Does this suggest another way to address the issue?

Thank you!

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

1 participant