Question

I have a problem with a function running before the previous one has had time to finish. According to the logs they both run but it is almost as if the function called from the AppDelegate is put onto a separate thread.

-(IBAction) checkLocation {
[AppDelegate locateMe];
[self checkForChangeAndReloadTable];    
}

The locateMe function can be called from several views which would do different things with the information. It finds the user’s location and saves it to user defaults. checkForChangeAndReloadTable checks the defaults and, if the location has changed, reloads the table with new, more relevant information. It seems the change happens after it checks so this does work if the checkLocation function is called twice by the user.

Is this expected? Any ideas how to get around it?

Answer 1

Without seeing any source code to the locateMe or checkForChangeAndReloadTable methods, it’s impossible to say, but several CoreLocation methods run asynchronously, which is probably your problem.