Xcode memory warning - failed to load Objective-C class information

Question

I only get this error on older iPhone4s by registering a user using Facebook and Parse. When I run it on the simulator, this error will never happen.

When this happens, the application takes up only 21.2 MB of memory, which is only 4.2% of the amount of memory available in my 4s test.

I'm not sure where to start to fix this error. Completely lost, to be honest.

2015-11-12 08: 09: 27.647 APPNAME [3883: 426582] Warning about receiving memory. warning: failed to load Objective-C class information. This will significantly reduce the quality of the available type information. (lldb)

Some updates on the issue, if you still think this is a duplicate, I will delete it. Although the question you suggested as a replica doesn't really help me solve the problem.

I could partially remove the error by reducing the number of requests that occur simultaneously and using Parse. Application, to get the first launch and register a new user, I need:

• facebook magazine
• request data in facebook graph
• add facebook data for user Parse
• create a reputation table and link
• launch of the main screen
• request reputation
• terms and conditions of request
• study request status

Having deleted the last two, I can get a warning to leave in the first seconds of using the application. And then I get a warning / error 10 minutes after starting the application without interaction.

This makes me think, if you have a lot of queries happening in the background at the same time, can this cause a warning about this type of memory? Or is it just a bug on Xcode, as another question suggests?

Answer 1

I came across this warning while creating my Cocoa application (OS X). but most likely this will happen with the iOS app.

warning: could not load any Objective-C class information. This will significantly reduce the quality of type information available 

With this warning, Xcode 7.3.1 took me to a line of code inside a third-party library -SwifyJSON. But I knew that this was not at all related to a third-party library, because it worked very well until a warning file appeared.

I had a MainViewController with a TabViewController that had multiple user views (and controllers of course)

I came across a warning immediately after setting up my second custom classes to pass data between them.

In MainVC, my code was

 private var firstTabVC = FirstTabVC var jsonInfo:JsonInfoClass = JsonInfoClass private var secondTabVC = SecondTabVC // waring had occured after this was added 

Xcode only took me to a third-party library when the jsonInfo instance line was directly above the secondTabVC instance line. (JsonInfoClass is a custom class associated with third-party JSON data)

I moved the line of problematic code just below the line of 'firstTabVC'. and then Xcode stopped complaining about loading the Objective-C class. I got the error "EXC_BAD_ACCESS" in the string "firstTabVC". It was here that I began to disbelieve what Xcode said.

So, I went to the custom class SecondTabVC, and I saw that I declared an instance of MainVC.swft (I had no idea why I like it anyway):

 var mainVC:MainViewController = MainViewController() 

to set "self" (MainVC) in it so that I can transfer data from MainVC, for example:

 override func prepareForSegue(segue: NSStoryboardSegue, sender: AnyObject?) { . .. secondTabVC.mainVC = self .... } 

after I changed the declaration in SecondTabVC.swif to

  var mainVC: MainViewController! 

Theft disappeared and worked great. Hope this helps someone.

Answer 2

This error occurred to me this morning, after an error message that I met: "warning: failed to load Objective-C class information, which will significantly reduce the quality of the type information."

But my situation may be different from yours. I created a class called "ILViewController" that was inherited from "UIViewController" and did not have a direct "view" property. When I turned to "ILViewController.view" (actually, "ILViewController" didnot have the property "view", but "UIViewController" did), this error occurred. So I want to say that you should check to see if your custom classes have some properties, but you still accessed them! Good luck