Chapter 230 Higher Developer Permissions

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

Lin Hui once again received a call from Elizabeth Nice.

Lin Hui couldn't help but sigh silently, she is really an energetic woman.

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 treat me like a mule. Do you still have human rights?

Although he protested deep down, Lin Hui still answered the call.

Elizabeth Nice: "Lin, I'm sorry to bother you so late.

I hope I didn't affect your rest.

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

I'm busy arranging a construction machine for you.

However, arrangements for application distribution were not considered.

Regarding application distribution..."

Lin Hui was a little impatient that his private time was interrupted.

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

Lin Hui wanted to hear Elizabeth Nice's opinion.

In fact, Android application distribution is quite simple.

For test distribution of Android software, just package an apk package and send it to the test device.

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

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

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

But how to say it?

Trouble is all relative. Although it is troublesome for Apple to distribute applications individually.

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

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

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

Android devices involve a lot of trouble.

However, the situation now is slightly better than in the past few years.

After all, there are not so many manufacturers who like to modify mobile phone systems.

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, which makes Pingchen very complicated.

It is relatively simple to perform similar operations on Android.

Specifically, it comes to the distribution of test applications on Apple mobile phones.

In previous lives, Lin Hui usually used TestFlight directly for application distribution.

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

Software developers can use the TestFlight application to distribute applications to be tested to up to 10,000 testers.

Developers only need to upload the beta version of the software and use iTunes to add the tester's name and email address to easily complete the distribution task.

In its previous life, TestFlight was able to take into account many different Apple platforms when distributing.

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

But I don’t know that something strange has happened in this time and space.

This space-time TestFlight does not distribute Apple internal beta applications at all.

Although Lin Hui was already used to the trivial differences between the two time and space.

But it’s hard to make a meal without rice. If you don’t use TestFlight to distribute test applications, Lin Hui has no good solution.

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

Although it is feasible in theory, it is very troublesome.

Testers often need to add the device UDID (Unique Device Identifier) ​​to the whitelist of the developer account to install and test.

In this process, the corresponding UDID must be collected from device to device, and then these UDIDs must be manually added to the personal developer account.

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

Moreover, using personal developer accounts for application distribution has great limitations.

A personal developer account can be used for testing on up to 100 devices within a year.

If you are just an ordinary software developer, this application distribution method is actually enough.

But Lin Hui is a maverick software developer.

With Lin Hui's high-yield situation like a sow's, there's no telling how many software projects a year he would have to build.

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

Not to mention that Lin Hui has to waste corresponding testing qualifications for a piece of software that has been transferred.

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

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

I hope Elizabeth Nice can provide Lin Hui with a more efficient way to test software.

Although in this time and space TestFlight is "not doing its job", it is distributing software.

If you do not use a personal developer account to distribute software, it seems that you can only distribute it through corporate signatures.

But that’s not necessarily the case. Maybe Apple has other methods when testing software.

It’s not like the official website hasn’t done something cool yet.

Just listen to Elizabeth Nice saying: "Regarding application distribution, considering that there are many inconveniences when distributing applications with personal developer accounts.

We have decided to introduce a higher authority signature mechanism to 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 software distributed using this signature.

However, due to the current confidentiality of the shortcut command software, if Mr. Lin wants to invite testers for this software, he can only do so among Apple internal staff."

In fact, there is absolutely no need for Elizabeth Nice to add the last sentence.

The principle of confidentiality of software transfer has been confirmed in the form of a contract when signing the transfer contract.

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

In the spirit of the contract, Lin Hui would not be able to invite irrelevant people at will.

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

Before listening to Elizabeth Neesi's words, Lin Hui originally thought that Apple was doing something crazy in app distribution.

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

Distribute applications directly using the signature mechanism.

Isn't this exactly 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's impression was that it would be very troublesome to apply for an enterprise development account on the Apple App Store.

A lot of restrictions.

For example, the applicant for an enterprise development account must be an enterprise, and it must be an enterprise with more than 500 employees.

Although there are clear conditions, you still face many difficulties when actually applying.

As a result, it is extremely difficult for later generations of companies to apply for account development accounts.

It’s not bad to have this permission now.
Chapter completed!