Use TestFlight-no longer worry about environment errors, and no worries about testflight

Use TestFlight-no longer worry about environment errors, and no worries about testflight

I. Preface

During iOS development, various bugs are inevitable. Therefore, you will solve all the bugs and then submit them to the AppStore. However, some people may encounter this situation: download the latest package after the installation and release, and find the access environment error. Check that the environment in the uploaded package is wrong (the formal environment, daily environment, and pre-release environment are not the formal environment ). This problem is embarrassing because the package used by the test engineer during the test is indeed correct, so this is not a test pot, but a developer's pot. After my tests, the release package used for uploading to the AppStore cannot be installed on the test machine. Therefore, after you upload the package to the AppStore, you can review it until it is released.

How can this pot be dumped? TestFlight is used!

Ii. Start

When your program has not been released (release) to the AppStore, you can use TestFlight to invite users to test your app and collect useful feedback.

You can invite up to 2000 testers to test programs that you haven't released by email.

So practical, let's take a look at how to use it.

First, you need to install the app TestFlight on your mobile phone.

 

 

 

 

 

 

 

 

 

First install and open the App, you will find the interface is as follows:

The following Apple ID is the Apple ID that is currently logged on to the device where the App is currently installed. Next, we can perform the test. In this way, you have configured TestFlight for your mobile phone (in fact, a tool software is installed ).

Then, log on to itunesconnect and create or view the existing app page:

You will find a TestFlight option. Click to enter:

 

After closing the pop-up window, you will find the interface as follows:

The build version here is the package uploaded when you normally mount the AppStore. Click All testers to view the persons who can use TestFlight for testing. Add testers to users and functions:

Click the user and TestFlight Beta tester in the function:

Internal testers are added from the iTunes Connect user, that is, internal developers. External testers may not be added to iTunes Connect users. Click an external Tester:

You can follow the above content and then add a tester. You can also create a group in testFlight and add an external tester.

Then add the build version at TestFlight:

After the build, the tester you invited will receive an email:

After you click View in TestFlight, you will find a string of uppercase letters in it. Open TestFilght on your mobile phone, click Redeem, and enter the string of uppercase letters you see, enter return to install the beta app.

Now you can perform the test.

Pay attention to the following points:

1. if you encounter a problem about lack of exit compliance certification, you can add ITSAppUsesNonExemptEncryption in Info. plist before packaging and set it to NO:

In this way, package again and then test.

There is also a way for you to avoid the problem of export compliance certification, that is, you still submit the app according to the normal logic, and then directly submit for review, this problem does not occur when you add a test user. I personally recommend the latter because if you think your app has no bugs, you can package it and submit it for review. However, you need to set up manual release at this time. In this way, after you submit the application for review (the app status changes to the pending review status), The tester can directly install the test version through TestFlight. If the test passes, we do not have to submit the application for review again. If the test fails, you can cancel the version review, modify the bugs found in the test, and submit the changes again.

 

Iii. Summary

Here is just a brief introduction to the use of TestFlight, the specific content should be tried by yourself, for example, you can set the test information, tell the tester to test something:

The entire process is very convenient.

If you have any questions, leave a message at any time.