IOS study 19th: several minor issues in real-machine debugging

In the last half-month, we began to deploy and debug the product.

Then we will find many problems.

First, it may be the memory of the Virtual Machine and the real machine itself, and many other factors may cause real-level flash push exceptions.

The basic solution is to use the memory detection tool for debugging. Generally, it is a memory problem. It seems that the debugging capacity on the simulator is much higher than that on the real machine.

Second, it seems to be about resources or code case sensitivity. Do you forget the details of this Agency (it takes a long time ).

It seems a bit case-insensitive on the virtual machine. It does not prompt an error, but an inexplicable exception occurs on the real machine, and the final result is a size problem.

Of course, whether this is the case or not is actually not easy to say, but I have encountered it. Here I am going to give a possibility error warning.

The debugging steps for a real machine are basically divided:

Developer account application --- certificate generation and download installation ---- application appid application --- device registration ---- description file generation and then download add to developer tool device --- modify part of project configuration properties in xcode

----- Run-to-udevice;

--------------
Download the real machine test and application upload tutorial documents and click -----------------

I. Account Application

There are a lot of online tutorials. I will upload a PDF document later.

Because the account is owned by the company, it is applied by the Project Manager. The specific practice is unknown ~

Ii. certificate generation, download, and installation

For more information, see PDF.

No difficulty.

Iii. Application of appid

This is also very simple, that is, to specify the bundle name ID for your application. Pay attention to two points here.

1. after applying for appid, it seems that you have no permission to delete it. Because I tested it twice before, I applied for two XX applications. XX. test. It will be fruitless to delete the app that you want to delete later.

A little more, slight interface scammers always want to delete invalid ones ~)

2. you can use the matching symbol * to name xx. xxx. * (for example, if you have multiple test applications, you can use the same description file containing the appid. You only need to use XX For the configuration files of different applications. xxx. app1,

That is, replace * to indirectly reduce the generation of the description file and multiple appids ).

3. If you use the name * above, there will also be disadvantages. For example, appid can be configured for the game center and internal purchase attribute configuration.

Disadvantages of one-to-multiple configurations ~ I have never seen it, because I only use this appid for testing.

Iv. device registration

For more information, see the PDF document.

No difficulty.

5. The description file is generated and downloaded and added to the developer tool device.

See PDF.

No settings. Check the Certificate Name. Select appid. Select the debugging device.

Then it is down. Click it to automatically deploy and associate it with xcode.

Vi. modifying some configuration properties of a project in xcode

1. Modify the bundle name

2. Select the corresponding certificate code signature

TIPS: there may be two minor issues.

1. After SVN or synchronization, the system prompts a signature error and other problems during run. It may be because a colleague submitted the file and modified the signature option. You just need to export the certificate from the certificate.

2. There is no connected device information in the run option after all settings are completed.

Check whether the SDK version selected by deployment target in your configuration information is higher than the SDK version of your device ~~

7. run the test.