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 6995113
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T19:58:46+00:00 2026-05-27T19:58:46+00:00

I just noticed a rather severe bug in my iPhone/iPad app: I have a

  • 0

I just noticed a rather severe bug in my iPhone/iPad app: I have a class called AppDelegate that implements the UIApplicationDelegate protocol – like every iPhone app has. I’m using Core Data, and the AppDelegate sets up my managed object context (I mostly just left the default methods of the Xcode template in place).

Now I need the managed object context in a few places in my app and I would also like to call the -saveContext method from a few places. So I used the singleton pattern and added a class method + (AppDelegate *)sharedAppDelegate that is implemented like this:

+ (AppDelegate *)sharedAppDelegate
{
    static dispatch_once_t pred = 0;
    __strong static id _sharedObject = nil;
    dispatch_once(&pred,^{
        _sharedObject = [[self alloc] init];
    });
    return _sharedObject;
}

Everything worked fine so far. Now however, I tried to access the sharedAppDelegate‘s UIWindow property and noticed it was nil. At first I was quite confused, but then I realized that first my main method creates an instance of AppDelegate, which creates the UIWindow and view controllers in -application:didFinishLaunchingWithOptions: and then, -sharedAppDelegate creates another one! I find it very strange that my app seemed to work quite well so far, because for instance only the first instance calls -saveContext when the app exists.

Anyway, I would like to change it so that the main method also uses the sharedAppDelegate. Does that mean that I need to override the -init method? How can I prevent an infinite loop (-sharedAppDelegate also calles init after all)? Should I make the _sharedObject variable of global scope?

  • 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-27T19:58:47+00:00Added an answer on May 27, 2026 at 7:58 pm

    You don’t create your own instance of the app delegate. The UIKit Framework creates one for you when the application starts up. You get the current app delegate from the delegate method on UIApplication. So when you want to get your shared managed object context:

    // Get the instance of your delegate created by the framework when the app starts
    AppDelegate* appDelegate = (AppDelegate*)[[UIApplication sharedApplication] delegate];
    
    // Assuming you're using the default methods from the template...
    NSManagedObjectContext* context = [appDelegate managedObjectContext];
    

    You can always get the current singleton UIApplication objected with the sharedApplication method and you can always get the proper instance of your app delegate using the delegate method on the application instance.

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

Sidebar

Related Questions

I've just recently begun to use markdown and have noticed that any markdown within
I just noticed that by instance famous application like chrome didn't have any 64
I just noticed that java.util.Observable is a concrete class. Since the purpose of Observable
I was working on an app tonight and I noticed that I have two
Just noticed that the style of the navigation menu on windows.com is just what
I just noticed that the return list for results is limited to 1000. I
I just noticed that Chromium was installed in AppData in both Vista and XP.
I just noticed that you can do this in C#: Unit myUnit = 5;
I just noticed that you can not use standard math operators on an enum
I just noticed while creating a RESTful WCF service that the Method parameter on

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.