On the simulator 17.2 I was getting no call backs from accountStatusWithCompletionHandler: and the Settings app was crashing when I tried to open iCloud. After a few resets of Settings the simulator Settings started working and I could open iCloud. At that point I was getting call backs to accountStatusWithCompletionHandler: and everything was working.

see https://stackoverflow.com/questions/47542005/ckmodifybadgeoperation-is-deprecated-in-ios-11-anyone-know-an-alternative-appro

see https://stackoverflow.com/questions/47542005/ckmodifybadgeoperation-is-deprecated-in-ios-11-anyone-know-an-alternative-appro for a work-around. Apple's methods do not reset the badge count on CloudKit.

This is still an issue. If CloudKit increments badge count then even using the 'new' [[UNUserNotificationCenter currentNotificationCenter] setBadgeCount:0 withCompletionHandler:nil]; doesn't work. And now CKModifyBadgeOperation no longer works.

The following solution (from another forum thread) worked for me: "you can work around this problem by checking 'Supports Running without iOS App Installation' in the General tab of the WatchKit Extension target."

In Objective C I was able to replace: NSArray  *windows = [[UIApplication sharedApplication] windows]; with NSArray *scenes=[[[UIApplication sharedApplication] connectedScenes] allObjects]; NSArray *windows=[[scenes objectAtIndex:0] windows]; I follow that with: for (UIWindow  *window in windows) {         if (window.isKeyWindow) {             foundWindow = window;             break;         }    }   UIViewController* parentController = foundWindow.rootViewController;    while( parentController.presentedViewController &&           parentController != parentController.presentedViewController ){         parentController = parentController.presentedViewController;    }

I was using CloudKit. The app appeared in the Settings app only after the app accessed CloudKit through:       [[CKContainer defaultContainer] accountStatusWithCompletionHandler:^(CKAccountStatus accountStatus, NSError *error) { That makes sense. Try to use the function that requires some sort of permission suitable for inclusion in the Settings app

My new MacBook Air M2 was struggling with downloading and installing Xcode. The problem, I think, was that the laptop sleeps after a short period of time and that stops the download/install process. Download/install restarts at 80% or 0% when the laptop is reawakened - repeat. A simple way to avoid the laptop from sleeping is to open the Terminal application (Application/Utilities/Terminal) and type "caffeinate". That prevents the laptop from sleeping and lets the download/install process complete itself. When done type control-c into the Terminal and it will quit caffeinate.

I am using TestFlight to test on devices until I pony up for a new Mac. It is far from ideal but it works. No debugging - but you can confirm that things work or not.

It's unclear if this is related but I had similar errors. They were caused by my failure to call invalidateAndCancel on an NSURLSession when the app went into background.

This error does not crash my app - for me it is just a warning. (edit - It only occurs on the simulator, not a real device.) It is coming the first time I access a particular website The website is in the domain: h ttps://sites.google.com/site... It does not come the second time I access that website. It does not come when I access different websites. Access is through: 				NSURLSession *theConnection=[NSURLSession sessionWithConfiguration: [NSURLSessionConfiguration defaultSessionConfiguration] delegate:self delegateQueue:nil];         NSMutableURLRequest *theRequest= 									[[NSMutableURLRequest alloc] 									 initWithURL:[NSURL URLWithString:	 --- website here ----		]]; 			 NSURLSessionDataTask *task= [theConnection dataTaskWithRequest:theRequest]; 			 [task resume];			 The error comes 0.1 seconds after [task resume] and 0.1 seconds before a resultant call to URLSession:dataTask:didReceiveData: )

I discovered I could eliminate this error if, after dismissing the MFMailComposeViewController, I added dispatch_async before presenting a mail results UIAlertController: 			[self dismissViewControllerAnimated:YES completion:^{  //this is the MFMailComposeViewController 									dispatch_async(dispatch_get_main_queue(), ^{ 															[self presentViewController:eMailResults animated:YES completion:nil];        						});    		 }];

It sounds like 'complainant' is going after you hard. You may need an IP attorney to guide you. You wrote "I see that the problem is with the name of my app". If that were true,  change the name, tell Apple that you are not in violation of any trademarks and ask to be re-approved. Better would be to have that IP attorney write you a letter that you could send to Apple.

Use the user's iCloud key-value file for the free trial durable record and to record the user's article history.

the user needs to pay, either monthly or single time. once the duration is over, if the user needs to improve again then the program can be purchased again else stopped. If it is a monthly payment then it is either an autorenewable subscription or a non-renewing subscription. If it is a single time then it is a non-consumable. But if it is a 'single time' but 'can be purchased again' then it is a consumable.