Crossover: 2014

Chapter 230 Higher Developer Authority

Just when Lin Hui was about to continue playing with these engineering machines.

Lin Hui received another call from Elizabeth Nishi.

Lin Hui couldn't help sighing silently, she really is a woman full of energy.

It's almost ten o'clock in the evening, why are you calling again?
Lin Hui: ⊙﹏⊙∥

Although the transfer contract was signed.

But you can't use me as a mule. Does anyone have the right?
Although he protested deeply in his heart, Lin Hui still answered the call.

Elizabeth Nishi: "Lin, I'm sorry to disturb you so late.

I hope I haven't disturbed your rest.

The reason why I called you is because of some previous oversights on my part.

I patronized to arrange engineering machines for you.

But it does not take into account the arrangements for application distribution.

Regarding app distribution..."

Originally, Lin Hui was a little impatient when his private time was interrupted.

But it is indeed a slightly troublesome thing about testing application distribution.

Lin Hui wanted to hear Elizabeth Nishi's opinion.

In fact, Android application distribution is quite simple.

The test distribution of Android software can be directly packaged into an apk package and sent to the test device.

Barring some special circumstances like version compatibility, the test app can be installed on almost any Android device to start testing.

But it is not possible under the Apple mobile phone system.

There are a lot of troubles involved in installing test software in the Apple mobile phone system.

But how?

Trouble is relative. It is troublesome for Apple to distribute applications.

But compatibility testing is much simpler than that of Android devices.

Because Apple's mobile phone system is not open source, the device types are far less diversified than the Android system.

Therefore, testers only need to consider the version of the Apple mobile phone system and the corresponding size and resolution of the screen when performing compatibility tests on the software.

And Android devices involve a lot of trouble.

But things are a little bit better now than in years past.

After all, there are not so many manufacturers who like to change the mobile phone system.

The application distribution mentioned by Elizabeth is actually to install the installation package on the test mobile phone.

In fact, there is not much complicated thing, but Apple made it very complicated.

It is relatively simple to perform similar operations on Android.

Specific to the distribution of test applications on Apple mobile phones.

In the previous life, Lin Hui usually used TestFlight to distribute applications directly.

In the previous life, TestFlight was a very powerful testing software distribution tool.

Software developers can distribute applications to be tested to up to 10000 testers through the TestFlight application.

Developers only need to upload the Beta version software and use iTunes to add the tester's name and email address, and then they can easily complete the distribution task.

In the previous life, TestFlight could also take into account many different Apple/Apple platforms when distributing.

Testers can download and use the TestFlight app for iOS, watchOS and tvOS and provide feedback to developers.

But I didn't know that something happened in this time and space.

This space-time TestFlight does not engage in the distribution of Apple's internal test applications at all.

Although the trivial differences between the two time and space are no longer strange to Lin Hui.

However, it is difficult for a clever woman to cook without rice, and Lin Hui has no good solution if TestFlight is not used to distribute test applications.

You can't directly use your personal developer account for distribution testing.

Although it works in theory, it is very troublesome.

Testers often need to install and test by adding the device UDID (Unique Device Identifier) ​​to the white list of the developer account.

In this process, the corresponding UDID is collected one by one, and then these UDIDs are manually added to the personal developer account.

After the test, you can use the device that has bound the UDID to the developer account to install the corresponding iOS internal test version for internal testing.

Moreover, the use of individual developer accounts for application distribution has great limitations.

Individual developer accounts can be tested on up to 100 devices within one year.

If it is just an ordinary software developer, this method of application distribution is actually sufficient.

But Lin Hui is a maverick software developer.

With Lin Hui's high yield like a sow, it is uncertain how many softwares will be produced in a year.

In this case, one hundred application distribution quotas among individual developers are not enough.

Not to mention the fact that Lin Hui had to spend corresponding testing qualifications for a piece of software that had already been transferred.

In addition to quota restrictions, individual developer accounts have many limitations.

In short, Lin Hui, who is used to enterprise test accounts, always feels awkward about this test mode.

I hope Elizabeth Nishi can provide Lin Hui with a more efficient software testing method.

Although in this space-time TestFlight "not doing business" for software distribution

If you do not use a personal developer account for software distribution, it seems that it can only be distributed through enterprise signatures.

But not necessarily, maybe Apple has other means when testing software.

It's not that the official hasn't done any show operation yet.

Just listen to Elizabeth Nishi said: "About application distribution, considering that there are many inconveniences when distributing applications with individual developer accounts.

We have decided to introduce a signature mechanism with higher authority into your personal developer account, Mr. Lin...

When testing, you can use this signature to directly distribute a certain number of applications.

In addition, Mr. Lin can invite testers to jointly debug the software distributed with this signature.

However, due to the current confidentiality of the shortcut software, if Mr. Lin wants to invite testers for this software, he can only invite testers within Apple. "

The last sentence was actually unnecessary for Elizabeth Nishi to add.

The principle of confidentiality of software transfer has been confirmed in the form of contract when the transfer contract is signed.

In this case, even if Lin Hui is allowed, he can invite testers at will.

In the spirit of the contract, it is impossible for Lin Hui to invite some irrelevant people at will.

As for the solution given by Elizabeth Nishi about distributing applications.

Before listening to Elizabeth Nishi's words, Lin Hui originally thought that Apple's application distribution was a magical operation.

After listening to it, it seems that it is nothing more than that.

Directly use the signature mechanism for application distribution.

Isn't this the same as the enterprise signature used by enterprise-level development accounts for application distribution?

The reason why I didn't directly create an enterprise-level development account for Lin Hui was just to not violate the so-called principles.

After all, Lin Hui had the impression that it would be very troublesome to apply for an enterprise development account in the Apple App Store.

A whole bunch of constraints.

For example, the applicant for an enterprise development account must be an enterprise with more than [-] employees.

Although there are clear conditions, but the actual application also faces many difficulties.

As a result, it is super strenuous for future generations to apply for account development accounts.

It's not bad to have this permission now.

(End of this chapter)