By error I disabled use auto layout in my storyboard and when I want to re enable it again the Xcode crashes. I need help please! It's very important....
The error is:
Process: Xcode [315]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 5.0.2 (3335.32)
Build Info: IDEApplication-3335032000000000~4
App Item ID: 497799835
App External ID: 106632651
Code Type: X86-64 (Native)
Parent Process: launchd [133]
User ID: 502
Date/Time: 2014-01-27 08:33:35.371 +0100
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report: 2942 sec
Crashes Since Last Report: 12
Per-App Interval Since Last Report: 2564 sec
Per-App Crashes Since Last Report: 12
Anonymous UUID: 24878C32-E46C-C700-0F6F-8B0D08B0549F
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
Sending userDidChangeValue: to <IDEInspectorBooleanProperty: 0x7fec6f13dcd0> from <NSButton: 0x7fec6f09da40>
ProductBuildVersion: 5A3005
ASSERTION FAILURE in /SourceCache/IDEInterfaceBuilderCocoaTouch/IDEInterfaceBuilderCocoaTouch-3747/IBPlugin/Utilities/IBObjectMarshalling.m:670
Details: Failed to run one shot request for IBUIDatePicker, IBUIImageView, IBUITabBar, IBUITabBarItem, IBUITableView, IBUIView, IBUIViewController, and IBUIViewControllerAutolayoutGuide.
Interface Builder encountered an error communicating with the iOS Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Exception name: NSInternalInconsistencyException
Exception reason: UITableView dataSource is not set
The error is larger, but I can't add much code.
EDIT:
An image to my Xcode:
EDIT:
I re-installed Xcode again, but the same problem.
SOLUTION:
Finally I solved it taking an old version of my storyboard and coping (cmd+c) the new viewcontrollers, and when I copy to the old storyboard this viewcontroller have "use auto layout" enabled. It's a bad solution (but faster). In my opinion this problem is an important Xcode bug.
Check your UITableView dataSource and delegate connection in Storybord
try link help you more
Xcode Interface Builder crashes when I edit storyboard
Start by trying to narrow down the problem. First, create a new iOS application project and see if selecting the xib file from the project navigator crashes Xcode. If Xcode doesn't crash, that is evidence there was something wrong with the xib file.
If Xcode crashes when selecting a xib file on a new iOS project, try adding an application xib file to the project by choosing File > New > New File. The application xib file is in the User Interface section of the new file assistant. Select the newly created xib file to see whether or not it crashes. If Xcode doesn't crash, that is evidence there is something wrong with the xib file that is part of Apple's Xcode project templates.
If Xcode crashes when adding a xib file to your project, create a Mac Cocoa application project. Select the xib file to see if it crashes Xcode. If Xcode doesn't crash, that is evidence that something is wrong with your iOS SDK installation.
If Xcode is still crashing, quit Xcode, trash Xcode's preferences file, and restart Xcode. The Xcode preferences file is located in the following directory:
/Users/YourUsername/Library/Preferences
If trashing the preferences file doesn't stop the crashing, reinstall Xcode.
Related
I have an app that is running with React-Native that doesn't crash on react-native run-ios, neither when I run it on Xcode, but when I upload it to iTunes Connect, the build is refused because of a crash.
The problem is that I cannot see the crash on Xcode > Window > Organizer > Crashes, because I cannot make it crash with a device or a simulator.
Does somebody know how to import a crash that comes from iTunes Connect to Xcode ?
Here is my crash log :
{"app_name":"mdef","timestamp":"2017-12-11 11:40:02.33 -0800","app_version":"1.2.0","slice_uuid":"3ff1d45d-3b65-325e-8df9-5b0ccf7550b7","adam_id":1246228626,"build_version":"66","bundleID":"com.mdef.mymatchup","share_with_app_devs":false,"is_first_party":false,"bug_type":"109","os_version":"iPhone OS 11.2 (15C114)","incident_id":"A6BCA3E0-DBB1-4E24-82F1-7B418F023CB0","name":"mdef"}
Incident Identifier: A6BCA3E0-DBB1-4E24-82F1-7B418F023CB0
CrashReporter Key: 972854c2d639e93f8277daa382921f72f9e8d379
Hardware Model: xxx1
Process: mdef [12142]
Path: /private/var/containers/Bundle/Application/07E05B5A-9B60-4A2E-BE1B-895E72344FC5/mdef.app/mdef
Identifier: com.mdef.mymatchup
Version: 66 (1.2.0)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: com.mdef.mymatchup [5622]
Date/Time: 2017-12-11 11:40:02.1820 -0800
Launch Time: 2017-12-11 11:40:01.1784 -0800
OS Version: iPhone OS 11.2 (15C114)
Baseband Version: n/a
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 1
Application Specific Information:
abort() called
Filtered syslog:
None found
Last Exception Backtrace:
(0x185cbe364 0x184f04528 0x185cbe2ac 0x104a8ff40 0x104a8dc04 0x185cc5cd0 0x185ba456c 0x185ba901c 0x104aa10b8 0x104ae0dd8 0x104ae0b38 0x18563aa54 0x18563aa14 0x18564496c 0x1856452fc 0x185645d20 0x18564e03c 0x1858e2f1c 0x1858e2b6c)
First of all in organiser crash logs will imported automatically if there will be any crash occurs on live app version.
Here you mentioned that your uploaded binary rejected due to crash issue. So they have provided you crash logs. Now that crash logs will not be imported into Xcode because App is not live yet.
So my suggestion is to resolve crash issue using this crash logs & lets get approval of application & make it live on app store. So after that if any user gets crash issue you will get list of it on Xcode -> Organiser.
Edit :
If you are not able to find out or detect the crash log than you should ask apple review team to provide more details regarding that crash issue
They can provide device & OS details to regenerate the crash also they can provide you steps to reproduce the crash.
If everything works than you should try & re upload new binary. You will surely get approval after this ways
For more better crash issues with detailed analysis you can use this crashlytics tool : https://fabric.io/kits/ios/crashlytics
Hope it will help you.
Thanks...
You can use analytic tools like fabric Crashlytics. whenever your app crashes on any device, Crashlytics will give you a detailed report about the crash on the dashboard with exact line number and details of the user's device.
Read this blog written by Bruno Barbieri about integrating Crashlytics in your react native app.
Or you can see crash manually from Xcode organizer.
read this to know more about checking crash reports from Xcode.
Solved ! I have fixed my problem by downgrading React-Native from 0.51.0 to 0.49.5, and I have no more crashes.
I'm running into a strange issue whereby an app I'm building crashes shortly after launching as an archived build from TestFlight, but runs without issue when running on the same device directly from Xcode. The application doesn't appear to be terminating fully - if I double-tap the home button, I see what looks like an image of the application in the background from midway through a run, even though the new session crashed long before it would have gotten to the displayed screen. If I then bring the application back to the foreground, it returns to its loading screen and then shuts down again, with a log that looks like this:
Incident Identifier: 983F8E4E-EFE0-4C93-8F46-D223FD86DF14
CrashReporter Key: 3515df1d8c55a27394a78b6efee5f83946ed9a99
Hardware Model: iPhone7,2
Process: FileProvider [218]
Path: /private/var/containers/Bundle/Application/89708FF4-E848-4F49-BC0D-B2DC9EF536C6/Drive.app/PlugIns/FileProvider.appex/FileProvider
Identifier: com.google.Drive.FileProviderExtension
Version: 4.2017.25202 (4.2017.25202)
Code Type: ARM-64 (Native)
Role: Unspecified
Parent Process: launchd [1]
Coalition: com.google.Drive.FileProviderExtension [368]
Date/Time: 2017-06-30 22:59:01.2937 -0700
Launch Time: 2017-06-30 22:59:00.7649 -0700
OS Version: iPhone OS 10.3.2 (14F89)
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace <0xF>, Code 0xdead10cc
Triggered by Thread: 0
...Any thoughts on what I should be investigating to understand what's going on here?
App is built in C++ using the Cocos2d-x framework.
Thanks!
_Kevin
Figured out what was going on, if not yet exactly why. Some of the details posted above turned out to be red herrings as I investigated further. What initially appeared to be a difference in behavior between an archived build and a build launched directly from Xcode was actually a difference in behavior between a debug build and a release build.
The solution was to create a new scheme in Xcode to run a release build (Product->Scheme->Manage Schemes in Xcode 8.3), duplicate my default mobile scheme, and then set the new scheme's Run->Info->Build Configuration to Release.
Once I ran a release build with Xcode attached, I found an error (probably an incorrectly-initialized variable but I'm still investigating) that occurred in release builds only.
The reason why crash logs weren't being generated appears to have been that the error was causing an assertion to trip (the CC_ASSERT macro in Cocos2d-x), so iOS considered the app shutdown to be a legitimate termination and didn't log it as a crash.
I have been working on an App today and have been able to debug it. All of the sudden I can't use breakpoints without Xcode 5.1 crashing. It will stop on the breakpoint, look like it's trying to display the local variables in the bottom left window, and then crash.
This is the crash report:
Process: Xcode [8084]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 5.1 (5084)
Build Info: IDEFrameworks-5084000000000000~21
App Item ID: 497799835
App External ID: 444172641
Code Type: X86-64 (Native)
Parent Process: launchd [189]
Responsible: Xcode [8084]
User ID: 294396280
Date/Time: 2014-04-03 14:57:52.981 -0600
OS Version: Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 5BFD5C24-5465-3BC8-137A-4BF1A8D48B38
Sleep/Wake UUID: F94AB6A7-9517-4F94-93DA-CC2C9154C8A7
Crashed Thread: 30 DBGLLDBSessionThread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 5B130a
Assertion failed: (!isNull() && "Cannot retrieve a NULL type pointer"), function getCommonPtr, file /SourceCache/lldb/lldb-310.2.36/llvm/tools/clang/include/clang/AST/Type.h, line 547.
(I can supply the rest of the report of what the threads are doing if it is helpful).
I have placed breakpoints in various files and locations in the code. I am able to use breakpoints in some places, but the majority of the breakpoints cause the crash.
I have looked through several SO pages with no luck. Among other things I have tried deleting all the breakpoints and just adding 1 back in. I have deleted and regenerated the schemes.
Any ideas?
I updated to 5.1.1. and the problem still exists:
Process: Xcode [19072]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 5.1.1 (5085)
Build Info: IDEFrameworks-5085000000000000~10
Code Type: X86-64 (Native)
Parent Process: launchd [197]
Responsible: Xcode [19072]
User ID: 294396280
I happened to have two iPhones connected via USB (a 4 with iOS 7.1 and a 5 with iOS 7.1.1), and Xcode 5.1.1 was "beach-balling" on me at the first break-point, wherever it might be, whichever breakpoint was hit first.
Just disconnected the iPhone 4 from USB.
I can use breakpoints again :)
YMMV of course ...
I encountered this problem as well recently with the same exact LLVM error:
Assertion failed: (!isNull() && "Cannot retrieve a NULL type
pointer"), function getCommonPtr
In my case it was a piece of code where I was storing an enum value (Permission) within another object as a reference, rather than a value:
Correct:
#property(nonatomic, readwrite) Permission permission;
Wrong:
#property(nonatomic) Permission *permission;
I was able to narrow down the problem by running Xcode's code analysis. After I made a correction to one or more of the warnings in each class I would rerun the analysis, then test and commit. Tedious but effective, and now I can debug again properly. Hope this helps steer someone in the right direction.
I clicked to turn off auto layout. And now I click the check box to turn it on, and xcode immediately crashes..Every time. I'm pretty sure that all tableviews have a datasource. I can't work on the project! Please help.
Process: Xcode [5748]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 5.0 (3332.25)
App Item ID: 497799835
App External ID: 38302662
Code Type: X86-64 (Native)
Parent Process: launchd [144]
User ID: 501
Date/Time: 2013-09-30 00:12:40.236 -0400
OS Version: Mac OS X 10.8.5 (12F37)
Report Version: 10
Interval Since Last Report: 62599 sec
Crashes Since Last Report: 13
Per-App Interval Since Last Report: 4441 sec
Per-App Crashes Since Last Report: 13
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 5A1413
ASSERTION FAILURE in /SourceCache/IDEInterfaceBuilderCocoaTouch/IDEInterfaceBuilderCocoaTouch- 3742/IBPlugin/Utilities/IBObjectMarshalling.m:670
Details: Failed to compute auto layout status IBUIDatePicker, IBUILabel, IBUITableViewCell, and IBUITableViewCellContentView.
Interface Builder encountered an error communicating with the iOS Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Exception name: NSInternalInconsistencyException
Exception reason: UITableView dataSource is not set
I just faced this problem and removing all of the File Owner's Outlets and Referencing Outlets did the trick.
Note: Firstly, as I couldn't turn off autoLayout graphically as Xcode crashed just by trying to view the .xib, I managed to do it following AbuYusuph's suggestion.
I was able to fix this issue by deleting the symlinks I had from the /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/ to the /Users/xxx/Library/Developer/Xcode/iOS DeviceSupport. I hope this will help.
I just remade an entire viewController and it works now. Not really answering the question. I am thinking it's just a glitch
Whenever I add a new language to Xcode (Project -> Localizations -> +), Xcode crashes immediately. Here is the error:
Process: Xcode [1362]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 4.4.1 (1488)
Build Info: IDEApplication-1488000000000000~2
App Item ID: 497799835
App External ID: 9950605
Code Type: X86-64 (Native)
Parent Process: launchd [132]
User ID: 501
Date/Time: 2012-09-10 11:53:15.906 -0700
OS Version: Mac OS X 10.8.1 (12B19)
Report Version: 10
Interval Since Last Report: 3309 sec
Crashes Since Last Report: 5
Per-App Interval Since Last Report: 3139 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: 6F2A1E95-B759-4403-BA5B-A1D00B69A631
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 4F1003
ASSERTION FAILURE in /SourceCache/IDEXcode3ProjectSupport/IDEXcode3ProjectSupport-1559/Xcode3Sources/XcodeIDE/Frameworks/DevToolsBase/pbxcore/Xcode3Model/Xcode3VariantGroup.m:709
Details: Assertion failed: [newFilePathString hasPrefix:self.resolvedFilePath.pathString]
Object: <Xcode3VariantGroup: 0x4017fbe00>
Method: -addNewReferenceForLocale:filePath:fileType:
Thread: <NSThread: 0x40030a220>{name = (null), num = 1}
Hints: None
Go to project and add new languages.(you might receive some path error)
Go localize.string file,uncheck your english in inspector pane.
Copy de.lproj(your language project) inside the en.lproj folder in finder and delete from outside.
Now add manually your de.lproj string file in your project.
Now enable english as well.
I've found an identical thread on the Apple Developer Forum:
https://devforums.apple.com/thread/166062?tstart=0
The solution there is to create a new project and drop all your source files in it? Sweet jesus.
EDIT: here's a terrible, hacky fix that worked for me: you can individually 'un-localize' all of your files (uncheck English in your files' Inspector pane), then go to Project -> Localizations -> +, and now adding langs seems to work for me. Seems to have something to do with Xcode not being able to add a lang & localize many objects at once?
I was running into this problem too (but in Xcode 7). I solved it like this:
Remove the plist from the project (but keep the file on disk).
In the finder, copy the plist file from your base localization (e.g. en.lproj) to the other lproj folders.
Add the plist file from each lproj, one by one, to your project.
The plist file will appear in Xcode as a tree of localized files, just as if you'd successfully used the Localize checkboxes.
Hope that helps!
Being a lazy bastard, I didn't want to recreate a new project with all the hassle of reconfiguring the whole show.
Here's what I did to fix the problem: I copied my storyboards somewhere else and removed them from the project. Then I moved them in my source folder (NOT in a xxx.lproj folder) and re-added them in my project.
Afterwards, I was able to add a new language in the project settings. Talam, case closed.