All geek questions in one place

IPhone app crashes right after update

Today, my application update was released in the store when it was updated or downloaded the first time the application was launched right after launch.

I tested the application on the simulator and on the device (the same where I installed the update from the store) and I never experienced this problem.

My update was sent by the Organizer after archiving in the "Distribution" section.

Apple doesn't perform these types of controls until the release of the app?

Has anyone had a similar problem? I have no idea what could be causing. Thanks Stefano.

+6
source share
6 answers

Here is the best way to test the assembly without deploying to the repository:

  • Set the assembly diagram to "iOS device"
  • Create an archive
  • Select your archive and click "Distribute"
  • Select "Save for Enterprise or Ad-Hoc Deployment"
  • Choose a certificate to sign the code
  • After saving the ipa file, use the Apple iPhone Configuration Utility (*) to install it on your device.

You should always perform two tests:

  • installation on a blank device after uninstalling the application * and any profiles in the settings → General → Profiles
  • installing the top of the previous version of your application to make sure that any files / preferences / etc are correctly converted to the new format.

(*) The iPhone configuration utility is mainly used to deploy enterprise applications, but it is also useful for developers and is available as a free download for mac and windows at support.apple.com. You can use iTunes instead, but it's confusing.

How does your application crash? I don’t know ... it could be anything. Standard debugging advice applies.

+6
source

The problem is related to the Framework. I had this exact error. This was not a case of logic, as it collapsed before the AppDelegate was even called, and my use of NSMetadataQuery was much later in the life cycle than that.

It turned out that a weak binding of the Foundation structure was required.

The problem was resolved by changing (in the "Project Information in Xcode" section) the dependence of the Foundation.framework parameter from mandatory to optional. Check for such a framework.

+2
source

Try to remove all old versions of the application that are on your device and reinstall. Also try using a different device, possibly with a different Apple ID in the developer account.

0
source

This happened with our application, and, apparently, with other applications. Apple is aware of this problem and is currently working on a solution.

see this article: http://techcrunch.com/2012/07/05/apple-responds-to-app-crashing-issues-has-a-dedicated-team-working-on-a-fix/

0
source

If you use basic data, and you have an updated database in your latest version without updating the kernel data, in this case the application starts after starting after the update.

0
source

Maybe the problem with the ios version or some methods or classes are not supported by your code.

-1
source

Source: https://habr.com/ru/post/919639/

More articles:


All Articles