Many years ago I worked as part of a team creating an operating system for a mobile device, it was a team of about 50 people and it took about 3 years to get the first version ready. You think you can create an entire operating system on your own and by assistance from a forum?

I've noticed the same thing happening. Not just databases but things like values in defaults remain. But only for a short while, if you delete an app then reinstall it within a few or several seconds of deleting it then this occurs, if the time gap is longer, say a few minutes, then it gets deleted.

7 years later since this thread was created, and this still occurs very frequently. Ridiculous.

Several days ago I uploaded a build to Testflight successfully, I just uploaded the identical version (just bumped the build number, that was the only change) and re-uploaded it, I just got the above error and the build isn't showing in Testflight (it appeared briefly for about 10 seconds saying processing then then vanished). So this is defiantly an Apple back end bug.

Every incoming notification to the phone, not just to your app? No. An invisible app, no a background app, no. No disrespect but you're obviously very new to iOS development. Such things like this are out of the question.

Not sure of the exact requirements here but what about if the url is stored within a .plist file which is read at run time. The value in the .plist can be the actual final url, or it is easy to inject a different url into there at build time. There is a tool to edit the contents of plists.

In my experience with App Store reviewers, they are not based in the US and English is not their first language nor a strong language in many cases. With you application and the use of the word happy that could perhaps lead to some mis-assumptions on their part. A happy number implies a fun or child like app, which is what the reviewers may think it is. Have you tried emphasizing the mathematical nature of your app to them, steering away from phrases like happy?

You could for example have a variable which gets written to by each view controller as it loads, thus keeping a record of the last loaded view controller. Or you could recursively scan the view controllers to determine what's at the top, I did that in one of my app's, the code is below. Its specific to the structure of my app but you get the general idea. extension UIApplication {     class func topViewController(_ base: UIViewController? = UIApplication.shared.keyWindow?.rootViewController) -> UIViewController?     {         if let nav = base as? UINavigationController         {             if nav.visibleViewController is UIAlertController             {                 let top = topViewController(nav.viewControllers.last)                 return top             }             else             {                 let top = topViewController(nav.visibleViewController)                 return top             }         }                  if let tab = base as? UITabBarController         {             if let selected = tab.selectedViewController             {                 let top = topViewController(selected)                 return top             }         }                  if let presented = base?.presentedViewController         {             if presented is UIAlertController             {                 return base             }             else             {                 let top = topViewController(presented)                 return top             }         }         return base     } }

For this entitlement you have to ask Apple if they will grant it to your app, if they do then they will add it to the provisioning/signing profiles etc.

It says "error: The specified item could not be found in the keychain." But you haven't said if the certs are in your keychain, if not why haven't you added them as that's what the error says is the problem, if you have then you haven't posted a screenshot of your keychain contents/showing if they are valid or not.

What on earth does that mean? You have an app and you want the app to make the iPhone reboot? That's totally impossible.

"Once I "published" that base app to TestFlight it loaded find on my iPhone." If the app loads fine on the iPhone, then what is actually the problem?

Errm, wouldn't it be better to instead eliminate the crash from your extension??? Common reasons for getting a crash with the call extension are: a) you're loading up too many/large data structures at once and are running out of memory, i.e. you load up an array of phone numbers which is hundreds of thousands entries b) you attempt to add a duplicate phone number c) the phone numbers are not sorted in order.

Asynchronous is asynchronous. You have to learn how to design and implement your code to take account of that.

It can't be achieved. You can't make notification trigger based on arbitrary events, nor can you make your app launch in order to post the notification.