You have several issues here. It’s important to read the documentation related to the app lifecycle which states what is called under iOS 13 and what is called under iOS 12. You may also want to see my Single View App template that supports iOS 12 and 13. Looking at your code, here is a … Read more
Use shared instance for AppState class AppState: ObservableObject { static let shared = AppState() // << here !! // Singe source of truth… @Published var user = User() } so you can use it everywhere struct MyApp: App { @UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate @StateObject var appState = AppState.shared // … other code } and func application(_ … Read more
It is called dependency injection. Basically the caller/constructor should be setting the NSManagedObjectContext onto the called/constructed. In your AppDelegate you should set the NSManagedObjectContext into the rootViewController that is associated with the UIWindow. Your rootViewController should then set the NSManagedObjectContext into the next view controller and so on. How? It is just a simple proper … Read more
You can use this code as well if you want to launch it from didFinishLaunchingWithOptions.Hope this helps. dispatch_async(dispatch_get_main_queue(), { let importantAlert: UIAlertController = UIAlertController(title: “Action Sheet”, message: “Hello I was presented from appdelegate ;)”, preferredStyle: .ActionSheet) self.window?.rootViewController?.presentViewController(importantAlert, animated: true, completion: nil) }) And up-to-date: DispatchQueue.main.async { let alert = UIAlertController(title: “Hello!”, message: “Greetings from AppDelegate.”, … Read more
You do need to duplicate the code but you need to make sure it runs only on the correct system. In iOS 13 you don’t want that application delegate didFinishLaunching body code to run, so use an availability check to prevent it. In the same way, use availability to hide the window scene stuff from … Read more
In Cocoa, a delegate is an object that another object defers to on questions of behavior and informs about changes in its state. For instance, a UITableViewDelegate is responsible for answering questions about how the UITableView should behave when selections are made or rows are reordered. It is the object that the UITableView asks when … Read more
The other solution is correct in that it will get you a reference to the application’s delegate, but this will not allow you to access any methods or variables added by your subclass of UIApplication, like your managed object context. To resolve this, simply downcast to “AppDelegate” or what ever your UIApplication subclass happens to … Read more
Well, I would not recommend you using anything, related to network operations on watch itself. First of all because Apple does not recommend to do it for obvious reasons. The only network thing that is performed on the watch directly is loading images. I have been struggling with network operations and watch for like a … Read more
You may be having issues with the if (applicationIsActive) condition. Put a breakpoint on -didReceiveRemoteNotification and see whether it executes in different scenarios and see if it goes within the if-condition. (unrelated to a certain extent but worth checking) this question: didReceiveRemoteNotification when in background Note: -didReceiveRemoteNotification will not execute if your app was (initially) … Read more
I had the same issue. Based on the answer to this question, I added [self.window makeKeyAndVisible] just before presentViewController:animated:completion:, and that fixed it for me. In your case, showLoginView becomes – (void)showLoginView { UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@”MainStoryboard” bundle:nil]; LoginViewController *loginViewController = [storyboard instantiateViewControllerWithIdentifier:@”LoginViewController”]; [self.window makeKeyAndVisible]; [self.window.rootViewController presentViewController:loginViewController animated:YES completion:NULL]; }