StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15171048
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-03-02T05:20:20.327
FavoriteCount
0
LastActivityDate
2013-03-02T05:20:20.327
LastEditDate
LastEditorUserId
0
OwnerUserId
3847
ParentId
10977679
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
Using your classes, this is what I would do. In your AppDelegate.m, when your app is in the foreground or background, I'd move the CLLocationManager to run in the foreground / background to match. The reason I'm doing this is because if the CLLocationManager is not moved to the background when the app is in the background, no location updates are sent to the CLLocationManager's callback <pre><code>- (void)applicationDidEnterBackground:(UIApplication *) application { [[LocationController sharedInstance] stop]; [[LocationController sharedInstance] startMonitoringSignificantLocationChanges]; NSLog(@"entered background Mode"); } - (void)applicationDidBecomeActive:(UIApplication *) application { [[LocationController sharedInstance] stopMonitoringSignificantLocationChanges]; [[LocationController sharedInstance] start]; NSLog(@"application Did Become Active"); } </code></pre> So lets say your app then moves to the background, and after awhile, iOS decides it's using too much memory and kills your app. A few minutes later, iOS then receives a location update, and respawns your app, letting it know it respawned due to a location service. You then need to re-start the background location service, as it will be the only chance your app has to do so. <pre><code>- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { if ([launchOptions objectForKey:UIApplicationLaunchOptionsLocationKey]) { [[LocationController sharedInstance] startMonitoringSignificantLocationChanges]; } return YES; } </code></pre> Oh, and one last change, I'm not sure why in your <code>locationManager:didUpdateToLocation:fromLocation:</code> method you're stopping the location service, as when you do that no more updates come through. Just leave it running, then every time a location change comes through you can send that to the server. <pre><code>- (void)locationManager:(CLLocationManager *)manager didUpdateToLocation:(CLLocation *)newLocation fromLocation:(CLLocation *)oldLocation { if ( abs([newLocation.timestamp timeIntervalSinceDate: [NSDate date]]) < 30) { self.lastLocation = newLocation; [self updateLocation]; //sending location to server } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POrecieving location updates after app is terminated
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USjklp
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.