Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
478 views
in Technique[技术] by (71.8m points)

ios7 - iOS MKMapShapshotter completion block is not always being called

I am trying to use the new iOS7 MKMapSnapshotter to generate a static map image. Whenever my app needs a map, I call the following:

MKMapSnapshotter *snapshotter = [[[MKMapSnapshotter alloc] initWithOptions:theOptions] autorelease];
dispatch_queue_t aQueue = dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_BACKGROUND, 0);
DebugLog(@"Snapshotter allocated %@ and run on queue %@", snapshotter, aQueue);

[snapshotter startWithQueue:aQueue completionHandler:^(MKMapSnapshot *snapshot, NSError *error) {
    DebugLog(@"Snapshotter completion block %@", snapshotter);
    // perform selector on main thread to set self.imageView.image = shanpshot.image;
}

In most cases this is working great. However sometimes, it seems like the device gets overloaded with requests for maps and then it stops rendering. In my log file I will see the first log statement about the "Snapshotter allocated" but never see the "Snapshotter completion block" message.

Is it possible that my requests are never executed off of the dispatch queue? Has anyone ever had this problem?

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)

This is (or appears to be) a bug in MKMapSnapshotter.

If network data and WiFi are turned off, the completion handler will not be called (unless there are cached data in the OS - see https://stackoverflow.com/a/5769108/481207 for clearing the cache).

In fact, the snapshotter appears to block waiting on data. It does not time out or detect that there is no data. After many minutes, e.g. 15 minutes, snapshotter.isLoading = YES. Calling cancel does not cause the completion handler to be called.

If WiFi or network data are turned back on, subsequent calls to start a (new) snapshotter will call the completion handler.

This s*cks badly if a variable is set when the snapshotter is started and cleared in the handler, because the variable is never cleared.

if (!isRendering) {
    isRendering = YES;

    [snapshotter startWithCompletionHandler:
     ^(MKMapSnapshot* snapshot, NSError* error) {
         // This may not be called so this code will
         // never run again.
         isRendering = NO;
     }];
}

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...