I know there are lots of posts on this error and it seems like it is a catchall for Xcode. I have tried all the suggestions in these posts:
Installation Failed "Invalid argument" when trying to run Today application extension
Installation Failed: Invalid Argument -iOS Extension
https://forums.developer.apple.com/thread/7338
And none of them have worked (I tried every answer's suggestion). I have reverted to older commits that I know never saw this error, done clean clone installs, I uninstalled and reinstalled Xcode, restarted my computer, deleted all derived data, and everything else I could possibly think of. Please let me know if you think you have an answer.
Note: I still think there may be an issue with the info.plist, but like I said, even reverting back to an older version doesn't work. Is there potentially a place xcode keeps info.plist files on the local hard drive and references these?
Thanks!
Somehow while installing Amazon AWS using pods in my project, the link to the Info.plist in the build settings of the project was deleted. I am still not sure how this problem occurred across all versions of the application, even older ones where this would not have been included. By filling this entry in the Build Settings to App_name/Info.plist the project finally compiled again.
Related
When I try to archive my xamarin forms app for publishing it gives the following error: Debugging symbol file for Plugin.Audiorecorder.dll is not valid and was ignored.
When I try to run the app in a simulator everything works fine.
How can I fix this?
I have tried to clean the solution and rebuild it.
I have deleted the bin and the obj folder.
I have changed the debugging options to portable.
But nothing worked
You may have installed other Nuget packages in your app. When archiving it, it'll cause conflicts between assemblies. You should try to resolve it by eliminating those conflicts.
If it still doesn't work, I suggest you directly report it to VS Product Team, from VS > Help > Send Feedback > Report a Problem.
I've got a very curious error to share regarding Xcode localization process. I will try to share as much detail as legally possible.
From Xcode, I am trying to export an XLIFF file to send to our translators, via "Editor > Export for Localizations". However, this immediately throws error with the message:
The operation couldn't be completed. Argument list too long
This is indeed confusing, as I cannot find a more verbose log anywhere (I have already tried checking my Console.app). So, I spent quite a few time googling – to no avail. I couldn't find similar case like this. The error itself happens only when I am trying to export for localization. I can build and run the app just fine.
Facts
~ $ xcodebuild -version
Xcode 8.2
Build version 8C38
~ $ xcode-select -version
xcode-select version 2347.
~ $ echo $PATH
/Users/david.christiandy/.rbenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/david.christiandy/arctools/arcanist/bin:/usr/local/go/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands
I am using Xcode 8.2 on macOS Sierra 10.12.5.
The error happens only when I try exporting from localization. This is also true when I run the localization process via xcodebuild -exportLocalizations.
I can build and run the app just fine. (I believe) there's no problem with my header search paths.
Attempts
Thought there was something wrong in the code, so I tried to run the export process (via xcodebuild command) in a CI. Somehow, it's working. For the record, I am using Bitrise CI with the same stack as my system (Xcode 8.2.x, macOS 10.12)
Asked colleagues to run export process on their machines, and they have the same error.
This leads me to think that there must be something wrong with the configuration. So I made a standalone project to confirm that the export process fails consistently. Turns out, it works just fine!
So, the hypothesis I got currently is:
There's probably something wrong in the code, and
There might be tools/software (that most of our iOS engineers installed) that might contribute to the error (since the CI completes just fine).
I don't know why the CI can run the export process just fine, and I don't know when it might suddenly stop functioning (just like our local machines).
Appreciate any help on this matter. Thank you!
I also asked this question on Apple developer forums, here is the link: https://forums.developer.apple.com/thread/86762
“Argument list too long” sounds like E2BIG, which you get when you try to run a child process with a huge argument list (I believe the current limit is 256 KiB). I suspect that Export for Localizations is running some sort of command line tool to do that work (probably the extractLocStrings tool, which you’ll find lurking within Xcode’s app bundle) and passing it full paths to each of the files in your project. Depending on how many files you have and how long those paths are, it’s easy to run into problems like this.
One of the ‘fun’ things about bugs like this is that they are dependent on where you place your project. Things might work if the project is at the top of your home directory but fail if it’s nested deep inside a subdirectory.
That also suggests a potential workaround, namely, to move your project further up in the directory hierarchy.
Finally, you should definitely file a bug about this. I believe we’ve seen this before (r. 30703294) but your report will help reinforce that this is causing problems for developers in the field. Please post your bug number, just for the record.
Several days ago before I read this answer, I managed to get the export working by deleting some folders via Xcode (remove references only). Initially I suspected that there's an invalid format within the folders that I deleted, but when I tried deleting other folders, the export process works just fine.
I also tried exporting strings using Xcode 9, and I didn't encounter the problem. So hopefully this bug is only for Xcode 8.3.3 and below.
I am trying to build my app but I received an error that "TapkuLibrary/TapkuLibrary.h" file not found but the file is added to my references.
I am not the one who did this project, this was just past to me without proper turn over.
I actually replaced my laptop and just open my source code from a new one with XCode 7.3.1
I also tried several solutions that I found here but still not working.
I'm also loosing some Link Binaries,
Hey I keep getting this error. I think its because earlier i deleted everything in derived data folder and now i get this error when i try to run my project this is a new little test project I'm doing for the apple watch does anybody know how to fix it? Thanks
I recognize this issue and I tried to restart Xcode, my computer, clear cache, clean etc when I also had this problem, without any luck. The only thing that got it working for me was to completely uninstall Xcode and remove all files. Check this post of how to do that.
UPDATE: QUESTION CLOSED: Fixed myself with a little backtracking. I'm using a framework that requires a source tree variable. (Sparrow). I updated the source tree on my main Mac Mini but not in my MacBook Pro. So, Xcode was searching an old directory due to that mistake.
This may be one of those weird Xcode bugs, so I'm looking for a little advice. I have Xcode 4.3.2 (latest as of this writing Apr 7 2012) installed on two Macs. I have a project saved in Dropbox so I can quickly get at it and work on it from either place. I've done this with several other projects and never experienced this issue.
One one computer, a Mac Mini, the project builds fine. On the other, a 2009 MacBook Pro, I get build errors. For one, even though I'm using -fno-objc-arc on a few of the source files, I am still getting ARC related errors. That is very puzzling to me. No issue when building on the Mac Mini. I'm also getting "file not found" errors pertaining to the .pch file. The error log is pointing me to a strange path like
/var/folders/9l/s_phv6yj0hv6q82_lrdcckb00000gn/C/com.apple.Xcode.501/SharedPrecompiledHeaders/...Prefix.pch' file not found
Here's what I've tried so far
Deleted Xcode and reinstalled from the MAS
Deleted the /var/folders directory called out in the logs
Removed the project build directory
Performed a Product -> Clean in Xcode
Restarted Xcode numerous times
Still no dice. Looks like unless I can nail down this issue, I'll be stuck working from one workstation for this project only. All other projects work fine when doing this.
Thank you for any help you can offer.
I was using a Source Tree variable in XCode, and one of the variables was out of date and pointing to the wrong path. One of the source files that was subsequently updated was working on one Mac but throwing errors on the other, which caused the build to fail and the linker to display strange errors.