Ios5 What Does "Discarding Message for Event 0 Because of Too Many Unprocessed Messages" Mean

iOS5 What does Discarding message for event 0 because of too many unprocessed messages mean?

This what Apple Technical Support says about this (after paying $49 for a Developer Tech Support Incident):

These messages are coming from Core Location framework. The most likely cause of these messages is that there isn't a run loop running on the thread on which the CLLocationManager was created. (This implies that the CLLocationManager wasn't created on the main thread.) The messages that are being discarded are location messages: event 0 is a location and event 24 is an authorization status update, for example. Because the messages being discarded, you won't see the appropriate delegate callbacks being invoked. Did you set up a geofence or some other callback and isn't servicing it quickly enough? The queue limit appears to be 10 before it starts dumping events and logging this message.
This information isn't publicly documented yet. I'm working with the Core Location team to improve the reported messages and see if this can be better documented.

Xcode leak tool stuck on MapkKit/CllocationManager Ios8

In the end I found the problem. Well the problem was pretty stupid I believe not many people will ever have this kind of issue but i will post my silly mistake.
While I developed the app I included a lot of logs there (some response from the server) as the time passed I forgot to remove them (of course before the release I would ).
That what actually stuck the app when it was running using tools.
That the response I received from apple support:

As NSLog also writes on the main thread, it was blocking both the map display and the location manager.
One thing to keep in mind is, although NSLog is generally used for printing our debug information, that is not it’s real job.
If you look at the Foundation Framework Reference docs, NSLog is described as: Logs an error message to the Apple System Log facility.
Therefore it is a very heavyweight call, and effects the performance of apps a lot.

and indeed when I run "Time profiler" I noticed that percentage time of running Nslog in some method are quite heigh.......

startMonitoringForRegion not always working

after searching and different trials i figured out how to solve it.

simply that view has to be visible and running all the time in order for the didEnterRegion and didExitRegion to work.

i moved everything to the appDelegate and now it's working.

---

Related Topics