Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 725681
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T06:21:52+00:00 2026-05-14T06:21:52+00:00

NSOperationQueue has waitUntilAllOperationsAreFinished , but I don’t want to wait synchronously for it. I

  • 0

NSOperationQueue has waitUntilAllOperationsAreFinished, but I don’t want to wait synchronously for it. I just want to hide progress indicator in UI when queue finishes.

What’s the best way to accomplish this?

I can’t send notifications from my NSOperations, because I don’t know which one is going to be last, and [queue operations] might not be empty yet (or worse – repopulated) when notification is received.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T06:21:52+00:00Added an answer on May 14, 2026 at 6:21 am

    Use KVO to observe the operations property of your queue, then you can tell if your queue has completed by checking for [queue.operations count] == 0.

    Somewhere in the file you’re doing the KVO in, declare a context for KVO like this (more info):

    static NSString *kQueueOperationsChanged = @"kQueueOperationsChanged";
    

    When you setup your queue, do this:

    [self.queue addObserver:self forKeyPath:@"operations" options:0 context:&kQueueOperationsChanged];
    

    Then do this in your observeValueForKeyPath:

    - (void) observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object 
                             change:(NSDictionary *)change context:(void *)context
    {
        if (object == self.queue && [keyPath isEqualToString:@"operations"] && context == &kQueueOperationsChanged) {
            if ([self.queue.operations count] == 0) {
                // Do something here when your queue has completed
                NSLog(@"queue has completed");
            }
        }
        else {
            [super observeValueForKeyPath:keyPath ofObject:object 
                                   change:change context:context];
        }
    }
    

    (This is assuming that your NSOperationQueue is in a property named queue)

    At some point before your object fully deallocs (or when it stops caring about the queue state), you’ll need to unregister from KVO like this:

    [self.queue removeObserver:self forKeyPath:@"operations" context:&kQueueOperationsChanged];
    

    Addendum: iOS 4.0 has an NSOperationQueue.operationCount property, which according to the docs is KVO compliant. This answer will still work in iOS 4.0 however, so it’s still useful for backwards compatibility.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I want to setup a serialized task queue using NSOperationQueue but I'm a little
The Problem I have an NSOperationQueue called logEntryGeneratorQueue I want to wait until all
I'm using NSOperationQueue in my app and i want to set multiples arguments to
When debugging in a thread created with an NSOperationQueue I can set breakpoints just
This is written in my viewDidLoad method NSOperationQueue *queue = [NSOperationQueue new]; NSInvocationOperation *op
What I Want I've got an NSOperationQueue in my application and it's critical that
i start the product request already in a operation block NSOperationQueue * queue =
I am using an NSOperationQueue to get some data for my app: NSOperationQueue *queue
I want to use Core Data in background threads and NSOperationQueue. Now I thought
I have a NSOperationQueue with a number of NSOperations in it. I want to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.