So, i'm loading an old project to do some updates. The project has been upgraded a few times in the past without issue. However, upgrading to 11.5 is producing the dreaded error: A Fatal Error Has Occurred. Click OK to Quit.
The next screen produces MS C++ Runtime Error:
Runtime Error!
The app has ... terminated in unusual way... Please contact support team ...
Completely useless error so i'm wondering if anyone has discovered common causes. This project does have an old 3rd party Xtra called MasterApp. However, all the other casts and .dir files upgrade fine when using this Xtra. The only thing unique about the files that fail is they are both over 200mb.
since the error message of director does not help, I would suggest you to try these things to narrow the error:
-Open the files in Director 10 an copy all Cast Members etc into a new file. Try if that helped.
-Remove the xtra fro the files and see if that helps. If it helps, than try to replace - for example by the BudApi-Xtra.
-Does your casts have big media which are not images? Sounds oder Videos for example? I would suggest lokking at them first.
-Try to convert the files on a windows PC.
BTW: Do you have the latest version of D11.5? MayBe there is an update that you can install.
Regards
Arno
Related
When I tried to archiving the project directly using Xcode menu (Product - Archive), it works well. But when I tried to execute it from the Integration menu (bot), I got this error:
Build operation failed without specifying any errors. Individual build
tasks may have failed for unknown reasons. One possible cause is if
there are too many (possibly zombie) processes; in this case,
rebooting may fix the problem. Some individual build task failures (up
to 12) may be listed below.
What happen? I couldn't find any error messages and completely have no clue on what's going on. I have tried to reboot the macmini and also revert the changes but it still.
UPDATE (Edit 3)
The issue has been fixed on Xcode 11, from beta 3:
Xcode uses response files by default to pass input files to the Swift compiler. To turn this behavior off, set USE_SWIFT_RESPONSE_FILE to NO.
You can use an unlimited number of Swift files in a target. (35879960)
Old answer
I've only seen this error arising when the total of files (notice all their respective absolute paths count) exceed the command line length limit (looks like it's imposed by the OS, currently 262144 bytes on my rMBP). It's a known issue.
To fix this (AFAIK), you have 2 options:
Fast (short term): Put your project on a shorter path on the server (like moving the project from /Users/mrjimoy_05_server/myprojects/mycoolproject/ to /p/mycoolproject)
Better (long term): While the first solution might work, for now, you'll probably reach the same point where you're now in the near future. So a better solution is to modularize your app (separate it into frameworks/projects). Since every module will get built separately, it'll be much harder to reach the limit and get this error again.
I hope it helps.
PD: Looks like the error thrown by the New Build System is:
unable to spawn process (File exists)
Edit 1
The error thrown by the New Build System on Xcode 10 now is:
unable to spawn process (Argument list too long)
Edit 2
The Swift team have solved this issue, but it also needs some work from the Xcode team, which hasn't been done yet on the latest released Xcode version (10.2)
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.
i am beginner in using opencv.i have tried with simple a program of reading an image. the build was unsuccessful with following error:
1>LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt
i am using opencv 2.4.2 ,visual studio 2010.(windows 7 user). i checked my property sheet many times as per the instruction.please anyone help me in this. thanks in advance
I find out that I have the same problem. The problem is that my project setting is debug version, and the lib I include in the linker-->input is release version. After changing the project to release version, the problem disappear. After changing project to release version, you need to edit all the properties again.
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.
I haven't touched any of my Blackberry projects for about 2 weeks now. Today I had to make some modifications, but when I tried to compile and run my code I got an error message like the following (this has been simplified):
JavaBuilder handling CoreException
org.eclipse.core.runtime.CoreException: File not found: C:\Program Files\etc etc etc\ClassName.class
And this error pops up for every single one of the files in my project.
I'm not a Java professional by any means, but I'm pretty sure this has something to do with my build path. What do I have to do? I did a system restore a little while back don't know if that has anything to do with this.
Thanks a lot.
Problem solved. For some reason alot of the folders in my project's folder were duplicated (ie: mainpackage, mainpackage(2)), so each one of my class files had a twin. Eclipse didn't tell me this, instead it just decided to say "I can't find the files" even though they were there. Not a very useful error message.
So I deleted mainpackage(2) and now it runs fine.
Thanks again for the help.