Time Travel: 2014

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 bound the UDID 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 he would have to build in a year.

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

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

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

In short, Lin Hui, who was used to using corporate test accounts, always felt awkward with 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 for software distribution, it seems that it can only be distributed through corporate signatures.

But that's not necessarily the case. Perhaps Apple has other methods when testing software.

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

Just listen to Elizabeth Nishi saying: "Regarding application distribution, considering the inconvenience of individual developer accounts when distributing applications.

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 Nish to add the last sentence.

The principle of confidentiality of software transfer has been confirmed in the form of 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 couldn't just invite irrelevant people.

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

Before listening to Elizabeth Nishi'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 whole bunch 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 have to 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 authority now.

At least the privileges of enterprise-level accounts can often be used to do some naughty things.

I don’t know if Apple will stop using this permission after this test is over.

Lin Hui did not mince words as he came into contact with more Westerners.

Instead, he asked bluntly: "As for the permission to use signatures to distribute software, can I still use it after completing the test of the shortcut software?"

Elizabeth Nice: "This is natural, Mr. Lin, why do you ask that? We are not so stingy in our affairs.

In fact, among Apple's millions of personal developer accounts, only a few have this higher-level signature mechanism.

Since your personal developer account is allowed to have such permissions, we will naturally consider it after certification.

No matter from the perspective of design elements or market value, you are the best software designer.

You deserve this. "

Although Elizabeth Nishi's words were not sure whether Lin Hui was a compliment or a fact.

But having a personal developer account with enterprise-level account benefits is still of great benefit to Lin Hui.

A major privilege of an enterprise-level account is that you can install signed applications on any iOS device, and there is no limit on the number of installations.

Let’s talk about the process of Lin Hui’s previous online application.

After Lin Hui uploads the applications, it does not mean that these applications can directly face ordinary users.

After that, it still needs to go through official review.

Despite Lin Hui's current situation, the review/verification time for each online application is very short.

But it still needs to be reviewed/verified. Only after review/verification can it be downloaded by other users.

However, having an enterprise-level account does not have this restriction.

This mechanism can be used to circumvent the review/review mechanism of Apple’s application launch for software distribution.

Technology knows no borders Enterprises have national borders.

From ancient times to the present, cooperation in all interests between China and foreign countries has almost never been able to escape the vicious circle of "working together with the same mind → sharing the same bed but having different dreams → fighting in the same room → dying together".

Although Lin Hui and Ping Chen have always cooperated closely since his rebirth, who can guarantee that this close relationship will continue?

Even though Lin Hui and Pingchen could be considered a community of interests at this time.

But it is just a community of "interests".

The close cooperation between Lin Hui and Pingchun is entirely based on interests.

This relationship is completely different from a community of shared destiny.

Communities of interests can have a solid relationship when they share the same interests and demands.

But when one party in the community of interests faces greater interests, there is no guarantee that it will not turn its back on the other party.

What's more, Lin Hui is Chinese, while Pingchun Company is an American company.

Technology may have no borders, but technology companies do.

This means that even if there is cooperation between Lin Hui and Pingchun, it is destined to be difficult to touch the core technology.

In case of such disagreement.

In addition, there is the potential background of great power.

Even though Lin Hui and Pingzhen were in the honeymoon stage at this time.

But Lin Hui has no doubt that there are many hidden dangers that may break out under the surface of the "honeymoon period" between him and Pingchun.