Question or issue on macOS:
In Xcode 3.1 up to Xcode 4.6.3, it included the LLVM-GCC compiler, with front ends from the GNU Compiler Collection and a code generator based on LLVM. In Xcode 3.2 and later, it included the Clang C/C/Objective-C compiler, with newly-written front ends and a code generator based on LLVM, and the Clang static analyzer. Oct 05, 2009 Hello, I just upgraded to 4.6.3 (from 4.6.2) and when I build my project in Xcode I'm greeted with about 20 of the same error: 'error: cast from pointer to smaller type 'il2cpparraysizet' (aka 'int') loses information' What gives? I had zero issues in 4.6.2. User2562 posted. Same problem here:(Details: xCode Version 4.6.1 (4H512) Xamarin Studio Version 4.0.3 (build 13) Installation UUID: 4e4bf6ac-b298-403d-93f0-e82b63317abd Runtime: Mono 2.10.12 (mono-2-10/c9b270d) GTK 2.24.16 GTK# (2.12.0.0) Package version: 210120000.
I have an OS X app that’s distributed through the Mac App Store, and recently updated to Xcode 4.6.3.
When I run my regular build now, I receive:
I can’t seem to discern any other changes in my project, so I can’t tell if it’s an issue related to the 4.6.3 update, or something else.
I have tried restarting Xcode, running a clean build, and cleaning the build folder.
How to solve this problem?
Solution no. 1:
I think I may have figured this one out. I’ve been running Xcode 4.6.3 on OS X Mavericks, under the impression that any build-specific tools were bundled in the Xcode application.
But, it seems codesign is in /usr/bin. Whether it’s put there by one of the Xcode installers or comes with a vanilla system install, I’m not sure. But reading through the man page for codesign, I found this nifty option:
And then I found this post (https://alpha.app.net/isaiah/post/6774960) from two weeks ago (~June 2013), which mentions (albeit second-handedly):
@isaiah I asked a guy in the labs about it. He said codesign now
requires embedded frameworks to be signed separately before code
signing the app bundle as a whole.
Manually re-running the codesign command that Xcode normally runs, while adding the --deep flag to the end, signs the application properly.
I’m not yet sure exactly what ramifications this manual signing has, or whether I can tweak the Xcode build to add the --deep flag automatically, but this seems to be the underlying issue. (codesign no longer automatically deeply signs your app bundle.)
Solution no. 2:
As highlighted in other answers, there is a change to the way code signing works. If you’ve installed any of the Xcode 5 DP’s then the new tools will be being used even if you are using Xcode 4.6.X.
All you need to do at this stage (in Xcode 4.6.X) is take the –deep flag suggested above and add it into your code signing flags (Target, Build Settings) see image below.
Solution no. 3:
For me, this problem was caused after dragging a folder named “resources” in my project. After changing its name into anything else(like “resourcessss” for example), the error disappeared.
Solution no. 4:
I had the same problem, but the answer was simple: the code signing identity on my app was set to “-“, so simply setting that to “Don’t Code Sign” fixed me up.
“-” seems to be the default setting when you carry out some set of actions, although I can’t tell you what those are.
Solution no. 5:
This might help somone:
Xcode 4.6 3 Dmg Download
I finally figured out the solution by trial and error. In my case I had a folder name that matched the “Product Name” variable under build settings. This also matched the entire project name! So I simply changed one field. I changed the “Build Settings” -> “Product Name” . The value of MySpecialApp was changed to My-SpecialApp. That was simply it! I then logged back into the Apple developer portal and created a new App ID and mobile provisioning profiles for development and distribution and the rest is history. My releases now work when deployed via the Ad Hoc distribution.
A final note on this. This is definitely a bug that Apple should either alert the user that they have done something wrong and enable some sort of automated corrective action.
– See more at: http://www.chrisdanielson.com/2012/08/29/codesign-ipa-and-the-code-object-is-not-signed-at-all-problem/#sthash.F0nF3BbC.dpuf
Solution no. 6:
For me it was a corrupted Framework PaddleMAs which:
1. I removed from my Cocoapods File
2. Ran pod install
3. Restarted my Xcode
Xcode 4.6.3 Dmg Torrent
and it solved the problem. For some reason a corrupted framework will prevent it being signed unfortunately XCode doesn’t show this error really clearly and give you a good fix suggestion. Have raised a bug with Apple to fix.
Xcode 4.6.3
