I am getting random crash in my in-market app that I believe caused by ODR. And It looks like I am not the only who encountered it, I found this radar and this thread but neither of them seem to have a fix for the issue. I am hoping somebody here have encountered this issue and found a fix for it, or a repro steps would be helpful too because I cannot reproduce it
Related
I am getting a crash log that I can't repro with the message:
"Selector name found in current argument registers: release"
I cannot figure out what this means and googling, has not given me any good answers.
It is labeled as
Exception Type: SIGTRAP
And the line of code that it is crashing at is:
let accentColor = data.AccentColor == nil ? UIColor.blackColor() : data.AccentColor!
The same line of code worked in the init() function, but it seems to be crashing at this later point after the user taps a button
This crash is happening a fair amount when I send it out to users, but I can't repro it or figure out what may be causing it.
What does this error message mean and what can I do to fix the issue?
This does not look like an issue with the HockeySDK but much rather with Swift itself.
I've seen several people having issues with Swift compiler optimizations lately. The issue probably only occurs on Ad-Hoc builds because Xcode uses the Release configuration for this which uses a different set of compiler settings.
If you try switching your local build from Debug to Release too, you should be able to reproduce this issue.
As a workaround, you can disable these optimizations for your Ad-Hoc builds but if this persists, you should probably file a bug with Apple.
I know this issue appears quite a lot but it seems like it is every time for a different reason. So when I try to build I get this error :
Command /Applications/Xcode-beta.app/Contents/Developer/usr/bin/ibtool
failed with exit code 255
And when I try to open main.storyboard, Xcode quits and I have this in the log :
Details: Failed to compute auto layout status IBLayoutConstraint and
IBUILabel. Encountered an error communicating with Interface Builder
Cocoa Touch Tool. If you choose to file a crash report or Radar for
this issue, please zip and attach the diagnostics at
"/var/folders/wv/vs8lxfzd7t3fl5jlckbcjlvh0000gr/T/IB-agent-diagnostics_2015-11-17_17-20-58_309000"
to your crash report. Exception name: NSGenericException Exception
reason: Unable to install constraint on view. Does the constraint
reference something from outside the subtree of the view? That's
illegal. constraint: view:>
I tried several things, cleaning the project, restarting Xcode and rebooting the computer, to no avail. I looked at the flags for IB like said at this question : Command /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool failed with exit code 255, but I don't have any. I opened IB in code, try to give it a look but it's quite massive, however all the
setTranslatesAutoresizingMaskIntoConstraints are set to NO inside. (This is also a solution I have seen mentioned in several places.
I should mention that I tried opening an other project and it worked perfectly well, so I guess it comes from this project, which is strange because it comes somebody else and it worked well on his computer, so some strange combination of project-xcode guilt.
Thanks for your help,
PS : And last, I am using Xcode-beta, version 7
EDIT
I also tried removing everything at this path /Library/Developer/CoreSimulator/Profiles/Runtimes.,(an other often seen solution for this error) though it didn't seem very related to my situation.
Already this question is in stack overflow.
Try this
My code is unable to build on xcode 7. What is Segmentation fault?
A segmentation fault happens when your code tries to access memory that it isn't allowed to access. This is often a sign of an uninitialized reference.
It's not clear to me from your screenshot exactly what is going on, though. Perhaps you could provide more details?
From the screenshot it looks like it is happening when you build your project. If this is correct, you need to create a minimal example that displays the problem i.e a code fragment that crashes the compiler in the same way and then you need to raise a bug report about it with Apple (supplying your minimal example so they can reproduce it).
This has happened to me a couple of times in the past and the way I have identified the bit that crashes the compiler is to comment out everything in the source file and then add it back in function by function.That will narrow the problem down to the function. After that you repeat with the lines of code in the offending function, until you get the line that crashes the compiler.
Along the way you may find a work around to stop the compiler crashing. If you do, do not be tempted to skip reporting the bug to Apple. They need to know.
WE had our existing project code base restructured, wherein a Static Library was separated out to be its own repository and it was added to the project as a submodule.
However, one of the issue we're facing is, duplicate print entries of log messages (all NSLog messages).
Before we restructured our project, logging to console had been fine and usual.
I've tried to look into sysLog and ASL documentation but I couldn't figure out what could be the issue.
Has anyone faced such an issue before?
I suppose this information should suffice, but if you need any more information let me know. I'm counting on that someone might have faced similar issue and has some solution or weird fix to it.
Thanks in advance.
This happened to me (in 2020). Fixed by re-launching the Console app. Console got itself confused somehow.
Could anyone suggest what this error might be caused by and suggest any possible solution? This is a compile time error and doesn't seem to have anything to do with code as the file in question is a xib.
The series of events which seems to lead to this error was:
Write project
Save project to USB drive
Open project at different location
This suggests to me that the problem is internal to XCode or there was corruption when copying to the USB but I haven't been able to verify either of those options. If anyone could shed some light on this, I'd be very grateful.
The solution was to re-create the nib as no attempt to rescue the current one or replace it with an old copy was successful.
If anyone has has the same problem and did find a way to solve it without re-creating the nib, I'd still like to know please!