If you run into the error "Could not create status list error" while syncing a branch using the Github Mac app here is a solution
Solution: There are nested folder paths in your file path (in my case it was under the cocoa pods folder). Deleting the top level folder fixed the issue.
The OP's solution does not work for me. I get the "Could not create status list." error on repositories that do and do not contain folders.
Related
After upgrading to the latest versions of Visual Studio for Mac, Xamarin, and Xcode, I am unable to create a signed IPA archive. Everything runs on the simulator, everything builds fine in my release configuration. I can even create the archive just fine. But after I click "Sign and Distribute", regardless of whether I try to publish to the App Store or simply save the IPA to disk, I get the extremely generic "Failed to create IPA archive" message with no other detail about what failed.
As always with these types of problems, this worked the last time I tried to publish (2 months ago). Even trying to use "Sign and Distribute" on an archive I previously published successfully to the App Store fails with the same message. Are there any logs for this where I can see exactly what is failing? The Archive output window at the bottom of the screen doesn't show activity for this stage of the process.
UPDATE:
After finding the logs, was able to see the following error that shows that for some reason after upgrading the apps, permissions were somehow lost for creating the zip archive:
zip -r -y "/Applications/Xcode.app/MyApp.ipa" Payload
zip I/O error: Permission denied
zip error: Could not create output file (/Applications/Xcode.app/MyApp.ipa)
zip exited with code 15
ERROR:Failed to create IPA archive.
Finshed
So now the question becomes why, and what steps need to be taken to fix this the proper way (i.e., not just brute-forcing broad permissions)?
Are there any logs for this where I can see exactly what is failing?
To find Mac logs through:
You can select the Go > Go to Folder menu item in Finder, and then copy and paste any of these paths into the dialog.
Visual Studio for Mac
~/Library/Logs/VisualStudio/7.0 (this number may change depending on
the version you are using)
This folder can also be opened via "Help -> Open Log Directory".
If you meet the Permission denied error in the log, this may be due to saving the IPA in the XCode.App folder. You can try a different location.
If you still meet problem, you can send a feed back inside visual studio for more help.
It's very likely due to permission issue while zipping the archive.
To check if it's your case:
Open the log folder at ~/Library/Logs/VisualStudio/7.0 or in Visual Studio for Mac Help > Open Log Directory
Find and open the last log file for publishing (like Publishing.yyyy-mm-dd__hh-mm-ss.log)
Scroll to the last rows of that file. If it contains something like this (see the block below) so it's your case
zip I/O error: Permission denied
zip error: Could not create output file (/Applications/Xcode.app/YourApp.ipa)
zip exited with code 15
ERROR:Failed to create IPA archive.
Finished
In this case, once you see Output IPA file popup, just choose other save location (Desktop for example)
I am trying to merge a development branch into master and I keep getting an error involving xcschememanagement.plist that reads: The data couldn’t be read because it isn’t in the correct format. I have already created a .gitignore file, as well as navigating to the file locations in terminal and running git rm --cached xcschememanagement.plist
Here are some screenshots of what I am seeing:
To solve the problem, you can locate xcschememanagement.plist, right click--->OpenAs---->SourceCode to find where the error happens and fix it. But you should always edit the info.plist with Open As > Property List to avoid messing up.
I am trying to commit to my local repository but it keeps saying "The working copy “Project” failed to commit files.
warning: unable to access '/Users/me/.config/git/attributes': Permission denied"
I tried this Unable to access 'git/attributes'
It worked for a while but after about an hour of working on my project the error comes back.
I don't know if this is related but some storyboard files are randomly marked for Deletion (with the D beside their file name) when trying to commit.
Sicne that .config folder is supposed to be owned by the user, check, whenever you see again this error:
the new owner of that .config folder (to see of it is root)
the process running at that time (like a local BitBucket server running as root),
or your command history (to see if it involved a command like sudo htop)
From the command line I am attempting to open the repobrowser by using the following command:
TortoiseGitProc.exe /command:repobrowser
Once the command is executed a dialog displaying "No working directory found." is displayed. I have even tried pointing to where I think the repo is by the following:
TortoiseGitProc.exe /command:repobrowser /path:"http://domain.here.com/" /notempfile
This produces the same error. I have done something similar using TortoiseSVN which brings up a URL dialog box.
I have looked in the settings to see if a path may be set for temporary files, but I didn't find any. Why is this error happening and how do I correct it?
Thanks.
With (Tortoise)Git it is not possible view a remote repository in the repository browser w/o cloning it first.
TortoiseGitProc.exe /command:repobrowser w/o the /path: parameter only works if the current directory is a working tree or (bare) local repository.
Firstly I read through many existing threads and followed the instructions there
Here
Here
Here
Here
Here
Here
Almost all the above threads asked me to delete the cache file. I went into the machine and deleted the cache file. I even edited the cache file (XML file named version config) but still it gets overwritten
But still even after that I am seeing the same issue.
The build agent has got dynamic $SourceDir as value
What else can I do to fix this? Please Help.
I tried doing tf workspaces but it simply keeps saying that "Unable to determine the source control server"
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (838): Unable to create the workspace 'NVM1756PDV_105_7' due to a mapping conflict. You may need to manually delete an old workspace. You can get a list of workspaces on a computer with the command 'tf workspaces /computer:%COMPUTERNAME%'.
Details: The path C:\Builds\7\Common_Security\cloud\src is already mapped in workspace NVM1756PDV_104_7.
Run the tf workspace /delete NVM1756PDV_104_7 command to correct this error.
Try using TFS Sidekicks to delete the workspace using the Workspace Sidekick.