This question already has answers here:
'Could not instantiate class named UITableViewCellContentView' iPhone 3.1.2
(5 answers)
Weird UITableViewCell Loading Exception
(3 answers)
Closed 5 months ago.
I found this problem after I install the latest SDK and Xcode version 3.2 Beta from Apple. Before install, my iPhone project compile correctly and has no any exception. But after I finished setup the latest SDK, I open my iPhone project to do some update. I compiled the project like I did before, no error report.
But after I run it in iPhone simulator, open the view that contains TableView, it throw an exception:
2010-02-01 14:07:03.924 SimpleApp[5458:207] *** Terminating app due to uncaught exception
'NSInvalidUnarchiveOperationException', reason: '*** -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class (UITableViewCellContentView)'
I am wondering something has change to my project's setting while XCode was updating. Could you help me by give me your idea or suggest some guideline to solve this? I'm ready to answer you more if you want more information about this bugs.
-EDIT-
I found that compile's log report the strange warning. I don't sure this is relate to the exception.
ld: warning: directory '/Volumes/Skiiing2/CD/ViewBased/Unknown Path/System/Library/Frameworks' following -F not found
Click on your target, then click Info, then note your Configuration (you'll need to change it for all), then look under Search Paths->Framework Search Paths and delete the offending path.
in my case, it was the same warning message that leads to Linker error. I found that Xcode 'escapes' ( prepend a '\' ) to my quote " in Library Search Paths. The directory was not found, causing the library not found and unable to link.
Related
I am unable to add a new iOS app to fabric by following the instructions of the Fabric macOS plug in.
I have followed all of the instructions found at Crashlytics documentation
When running the app, I receive this error:
2018-03-12 14:22:24.090838-0400 [19139:8550117] [Crashlytics] Version 3.10.1 (129)
2018-03-12 14:22:24.636050-0400 [19139:8550293] [Fabric] unable to complete application configure: Error Domain=FABNetworkError Code=-5 "(null)" UserInfo={status_code=422, type=2, request_id=fbc432572e6f0e10f21d2ddc24c7f272, content_type=text/html; charset=utf-8}
I have tried searching StackOverflow and following answers, but no luck avoiding this error message.
Any ideas on this error message?
I had this problem and discovered that my 'visible' (in Xcode) info.plist was not a file in my root directory, and was an out of date version from earlier development activity. I am not sure why my correct/current info.plist did not display in Xcode. I found the current info.plist in Finder (it was in the root directory in Finder, just not appearing in Xcode). I dragged the file from Finder to Xcode and accepted all the defaults in the dialog that appeared. Then I simply built and ran the current scheme and all worked as it should.
Note: It appears that for some time I have been updating the 'invisible' info.plist directly from my apps Target / Info tab.
Make sure to include all dependency then throw a force crash or runtime error and do not forget to turn on your data or internet connection.
I recently updated to Xcode 7 and as usual something has to go wrong. Its really a shame because I was looking forward to the new features in Xcode 7.
I am faced with a an error which I cannot seem to fix. Every time I try and build the project I get the following error:
I thought there was something wrong with my project, so I made a new Single View application and I still get the same error.
I have tried the following things but none of them has worked for me:
Restart Xcode (Didn't work).
Clean and rebuild project (Didn't work).
Restart Mac (Didn't work).
Reinstall Xcode 7 from the Mac App Store (Didn't work).
Installed Xcode 7 on a different Mac (Still got the same issue, even with a new Xcode project).
I tried the solution in this Stack Overflow question: https://stackoverflow.com/a/31614717/1598906 - But alas it did not work.
Finally, I tried the following Terminal command with no avail: $ sudo killall -9 ibtoold
Is anyone else having this issue with Xcode 7.0? And if so, have you managed to come with any other solutions? I have tried everything I can think of and nothing works.
Lastly, below is a copy of the error Log:
2015-09-18 21:09:28.416 ibtoold[1598:39510] [MT] IBPlatformTool: ***
Failed to launch tool with description
System content
1x for IBCocoaTouchFramework-EightAndLater w/ default fidelity: Failed
to find or create execution context for description
System content
1x for IBCocoaTouchFramework-EightAndLater w/ default fidelity: Failed
to find a suitable device for the type SimDeviceType :
com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with runtime SimRuntime :
9.0 (13A340) - com.apple.CoreSimulator.SimRuntime.iOS-9-0 (Failure reason: Failed to create SimDeviceSet at path
/Users/daniel/Library/Developer/Xcode/UserData/IB Support/Simulator
Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator
to see why creating the SimDeviceSet failed.) 2015-09-18 21:09:38.290
ibtoold[1598:39510] [MT] IBPlatformTool: Wrote failed marshalling
request diagnostics to path:
/var/folders/lx/kkhv57fd2ll7rhdt0bwfpkb00000gn/T/IB-agent-diagnostics_2015-09-18_21-09-28_418000
/* com.apple.ibtool.errors */ /Users/daniel/Desktop/DS
APPS/BT/BloodyTest/BloodyTest/Base.lproj/LaunchScreen.storyboard:
error: Could not open document
Recovery Suggestion: Failed to connect with the iOS agent. Please file a bug report at bugreport.apple.com and attach a zip file of the
diagnostics located at
"/var/folders/lx/kkhv57fd2ll7rhdt0bwfpkb00000gn/T/IB-agent-diagnostics_2015-09-18_21-09-28_418000".
Underlying Errors:
Description: Failed to find or create execution context for description
System content 1x for IBCocoaTouchFramework-EightAndLater w/ default
fidelity
Underlying Errors:
Description: Failed to find a suitable device for the type SimDeviceType : com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with
runtime SimRuntime : 9.0 (13A340) -
com.apple.CoreSimulator.SimRuntime.iOS-9-0
Failure Reason: Failed to create SimDeviceSet at path /Users/daniel/Library/Developer/Xcode/UserData/IB Support/Simulator
Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator
to see why creating the SimDeviceSet failed.
Thanks for your time, Dan.
Well thanks to the community for all there help..... not.
In the end I got it working by simply upgrading to OS X El Capitan and Xcode 7.0.1.
One thing I would point out though, is that when I was looking through the Xcode app files, some of them were corrupted and when I updated to Xcode 7.0.1 this issue was not fixed. So before installing OS X El Capitan, I deleted the following:
Xcode 7.0.1 app
Library/Developer folder
Macintosh HD/Library/Developer folder
I then installed OS X El Capitan and then installed Xcode 7.0.1 and now everything works fine.
I hope this helps anyone else who is experiencing the same issue.
facing this error while building a project in xcode
warning: unable to merge a subprocess's serialized diagnostics
error: unable to open output file '/Users/s-09/Library/Developer/Xcode/DerivedData/ls-cujvtldtpxrezhdhbujnmfcrntjl/Build/Intermediates/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVPluginResult.o': 'Error opening output file '/Users/s-09/Library/Developer/Xcode/DerivedData/ls-cujvtldtpxrezhdhbujnmfcrntjl/Build/Intermediates/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVPluginResult.o': Input/output error'
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1
Cleaning the /DerivedData made it work
Can I safely delete contents of Xcode Derived data folder?
I have also faced that problem. I have closed, restarted Xcode; deleted the application from device and reinstalled it again, then the problem has gone.
Make sure the library and project files is truly included if it is not include it shows in red color in this type of case some time it is in original folder and not in project so delete it and add it again.
I recently turned on stricter warnings for a project, and Xcode started throwing warnings on some of Apple's classes. I'm not sure if this is an Apple bug, or if I'm doing something wrong. I'm using Xcode 6.1.1 on Yosemite.
TL;DR: adding some strict warning flags to your project starts throwing warnings in various XC*Test*.h headers. The issue is intermittent, but the steps below have reproduced the issue on multiple computers.
Steps to reproduce:
Create a new Xcode project via File → New → Project.
Choose iOS → Application → Single View Application.
For Product Name, type MyApp. Choose Objective-C and Universal. Save the project.
Build the project with CommandB. Run the tests with CommandU. Observe that they both finish with no errors or warnings.
Click on the Project to go to the Project Settings.
Click on the blue MyApp Project (as opposed to MyApp or MyAppTests targets).
Click on the Build Settings tab.
Search for Other Warning Flags.
Enter the following string for the Other Warning Flags for the app:
-Weverything -Wno-objc-missing-property-synthesis -Wno-objc-property-synthesis -Wno-direct-ivar-access -Wno-assign-enum -Wno-float-equal -Wno-sign-compare -Wno-switch-enum -Wno-gnu -Wnewline-eof
Build the app again. You should see three or four warnings about treating #import as #import, which is expected given the warnings you just enabled.
Clean the project with CommandShiftK
Build again. You may see extra warnings. If not, then you need to…
Delete the DerivedData folder, at least for this project. It is located at /Library/Developer/Xcode/DerivedData/MyApp-*, where * is some random identifier string. You may also need to delete /Library/Developer/Xcode/DerivedData/ModuleCache.
Clean and build again. And again. It may take a few times. Eventually...
You will see code and documentation warnings on XCAbstractTest.h, XCTestCase.h, and XCTestSuite.h. Screenshot:
As you can see, these warnings would be quite valid on my own code, but this is Apple’s framework code. Is there any way to stop these weirdly intermittent warnings from appearing? Or is it an Apple bug that the file gets warnings at all? I’m leaning Apple bug, because plenty of other Apple headers use #import instead of #import, and none of them is throwing warnings.
Update: I filed a radar: http://www.openradar.me/20038246
Update 2: I was able to glean some more information that may be helpful:
The issue appears to be at least partly related to where Derived Data is stored. See this screen recording, courtesy of Sam Marshall for details: http://cl.samdmarshall.com/a4Hy
Note that, when I reproduce the same steps as in Sam's video on my computer, I am not able to get rid of the extra warnings. They always come back. Possible differences between my and Sam's setups:
Sam is on Xcode 6.1, while I am on 6.1.1.
Sam is on Mavericks, while I am on Yosemite (10.10.2).
When I build in Xcode 6.3b2, I get an additional warning about "building module 'UIKit'". See screenshot: http://cl.ly/a3sK
Update 4: Radar was closed as a duplicate of an issue.
Update 5: I have a workaround, which is to disable the problem warnings on the Tests target only. Here’s a partial diff. Xcode won’t add the $(inherited) automatically, so you’ll have to add it yourself.
+ WARNING_CFLAGS = (
+ "$(inherited)",
+ "-Wno-documentation-unknown-command",
+ "-Wno-auto-import",
+ "-Wno-incomplete-module",
+ );
I have a problem in my app , in all simulator it works fine but in iPhone 6plus simulator
I got this message :
2014-11-10 11:18:11.651 myApp[14829:8759969] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Could not find a storyboard named 'Main' in bundle NSBundle </Users/roei/Library/Developer/CoreSimulator/Devices/01F5D8F1-B462-4DA7-90FD-D9F3E7E7EE2A/data/Containers/Bundle/Application/C8420B33-64D1-4D89-93A5-69324BE6DB88/Symbo.app> (loaded)'
*** First throw call stack:
I try to do this :
1)Make sure your -info.plist has Main story board file based name = MainStoryboard.
2)Right Click on your Story Board file in Xcode and select Delete then References Only
3)Right Click on your project and select Add Files to [Your Project]
4)Navigate to the story board file, found in the en.lproj folder in your projects directory and add it
5)Clean, Recompile and Run and you should find it works.
Got the idea from this SO post: XCode 4.2 MainStoryBoard Not Found
But it did not solve the problem.
I also tried to reset the simulator and clean the progect , but still did not solve the problem.
Please help me (-:
If anyone's still having this problem, what I did to fix it is just:
Go to the project file
Click on the target that you're having problem with
Select Build Phases
In Copy Bundle Resources, add your storyboard.