CN115065670B - IOS APP automatic release method, macOS server and system - Google Patents

IOS APP automatic release method, macOS server and system Download PDF

Info

Publication number
CN115065670B
CN115065670B CN202210986063.3A CN202210986063A CN115065670B CN 115065670 B CN115065670 B CN 115065670B CN 202210986063 A CN202210986063 A CN 202210986063A CN 115065670 B CN115065670 B CN 115065670B
Authority
CN
China
Prior art keywords
server
macos
release
instruction
ios app
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210986063.3A
Other languages
Chinese (zh)
Other versions
CN115065670A (en
Inventor
辛鹏辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Bank Co Ltd
Original Assignee
Ping An Bank Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Bank Co Ltd filed Critical Ping An Bank Co Ltd
Priority to CN202210986063.3A priority Critical patent/CN115065670B/en
Publication of CN115065670A publication Critical patent/CN115065670A/en
Application granted granted Critical
Publication of CN115065670B publication Critical patent/CN115065670B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application provides an IOS APP automatic release method, which comprises the following steps: the macOS server responds to a publishing instruction input by a user to read a local configuration file, wherein the configuration file comprises publishing data required by publishing the application program file; the macOS server writes the release data and the code path into parameters of corresponding fields in a preset script template to form a release script; the macOS server calls the release script to generate a check instruction and an upload instruction; the macOS server executes the check instruction and sends the check instruction to an IOS APP release management server to verify the application program file; the macOS server receives a verification result fed back by the IOS APP release management server; and when the verification result is that the verification is passed, the macOS server executes the uploading instruction and sends the uploading instruction to the IOS APP release management server so as to upload the application program file to the IOS APP release management server. The technical scheme can more quickly and safely issue the IOS APP.

Description

IOS APP automatic release method, macOS server and system
Technical Field
The application relates to the field of mobile internet, in particular to an IOS APP automatic issuing method, an IOS APP automatic issuing device, a macOS server and an IOS APP automatic issuing system.
Background
The App end occupies most of market shares in android and IOS two major arrays at present, and application store release of IOS at present completely depends on manual operation, and the mode is inefficient and easy to make mistakes, and has high professional requirements and high threshold in practical application. If the operator is unfamiliar, the malfunction can cause a significant accident to the entire release. Even if the user uses the automatic release mode, the user also uploads the early APP special password and account number mode, and the key information of the account number is stored in the mode plaintext, so that certain potential safety hazards exist.
The existing potential safety hazards are likely to cause the issued account to be stolen after the account is leaked or intercepted in the plaintext transmission process, further causing commercial loss, and the application preconditions of the technology in the industry are not clearly described, so that comprehensive information can be obtained by searching in multiple directions, and resource waste is caused.
Disclosure of Invention
In view of this, it is actually necessary to provide a faster and safer IOS APP automatic issuing method, IOS APP automatic issuing apparatus, macOS server, and IOS APP automatic issuing system.
In a first aspect, an embodiment of the present application provides an IOS APP automated publishing method, where the IOS APP automated publishing method includes the following steps:
the macOS server responds to an issuing instruction input by a user to read a local configuration file, wherein the configuration file comprises issuing data required by issuing an application program file, and the issuing data comprises a secret key ID and an issuer unique identifier; the issuing instruction comprises an access path and a code path of the configuration file, wherein the macOS server reads the local configuration file according to the access path;
the macOS server writes the release data and the code path into parameters of corresponding fields in a preset script template to form a release script;
the macOS server calls the release script to generate a check instruction and an upload instruction;
the macOS server executes the check instruction and sends the check instruction to an IOS APP release management server to verify the application program file;
the macOS server receives a verification result fed back by the IOS APP release management server, wherein the verification result comprises verification passing or verification failure; and
and when the verification result is that the verification is passed, the macOS server executes the uploading instruction and sends the uploading instruction to the IOS APP release management server so as to upload the application program file to the IOS APP release management server.
In a second aspect, an embodiment of the present application provides an automatic issue device of IOS APP, where the automatic issue device of IOS APP includes:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for responding to a publishing instruction input by a user to read a local configuration file, the configuration file comprises publishing data required by publishing an application program file, and the publishing data comprises a secret key ID and a unique identifier of an issuer; the issuing instruction comprises an access path and a code path of the configuration file, wherein the acquisition unit reads the local configuration file according to the access path;
the creating unit is used for writing the release data and the code path into parameters of corresponding fields in a preset script template to form a release script;
the calling unit is used for calling the issuing script to generate a checking instruction and an uploading instruction;
the execution unit is used for executing the check instruction and sending the check instruction to the IOS APP release management server so as to verify the application program file;
the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a verification result fed back by an IOS APP release management server, and the verification result comprises verification passing or verification failure; and
and the uploading unit is used for sending the uploading instruction to the IOS APP release management server by the execution unit when the receiving unit receives that the verification result is that the verification is passed, so as to upload the application program file to the IOS APP release management server.
In a third aspect, an embodiment of the present application provides a macOS server, where the macOS server includes: the computer readable storage medium is used for storing program instructions, and the processor and the bus execute the program instructions to realize the IOS APP automatic issuing method.
In a fourth aspect, an embodiment of the present application provides an IOS APP automated release system, where the IOS APP automated release system includes:
the macOS server is the macOS server;
and the IOS APP release management server is in communication connection with the macOS server and is used for verifying the application program file, returning a verification result and receiving the application program file uploaded by the macOS server when the verification is passed.
According to the IOS APP automatic issuing method, the IOS APP automatic issuing device, the macOS server and the IOS APP automatic issuing system, issuing is performed through the electric shock issuing button on the issuing interface, so that a publisher does not need to pay more attention to specific internal implementation when issuing application files, and only simple button clicking operation is performed according to a system established according to a scheme, and issuing of production application files can be easily achieved. And an APP special user name and a special password are not needed, so that the publishing of the application program file is safer.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the structures shown in the drawings without creative efforts.
Fig. 1 is a flowchart of an IOS APP automatic publishing method provided in an embodiment of the present application.
Fig. 2 is a first sub-flowchart of an IOS APP automatic publishing method provided in the embodiment of the present application.
Fig. 3 is a second sub-flowchart of an IOS APP automatic publishing method according to an embodiment of the present application.
Fig. 4 is a third sub-flowchart of an IOS APP automatic publishing method provided in the embodiment of the present application.
Fig. 5 is a schematic diagram of an IOS APP automatic publishing apparatus of the IOS APP automatic publishing method according to the embodiment of the present application.
Fig. 6 is a schematic diagram of an obtaining unit provided in an embodiment of the present application.
Fig. 7 is a schematic diagram of an IOS APP automatic publishing system provided in the embodiment of the present application.
Fig. 8 is a schematic internal structure diagram of a macOS server according to an embodiment of the present application.
The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the above-described drawings (if any) are used for distinguishing between similar items and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances, in other words that the embodiments described are to be practiced in sequences other than those illustrated or described herein. Moreover, the terms "comprises," "comprising," and any other variation thereof, may also include other things, such as processes, methods, systems, articles, or apparatus that comprise a list of steps or elements is not necessarily limited to only those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such processes, methods, articles, or apparatus.
It should be noted that the descriptions in this application referring to "first", "second", etc. are for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In addition, technical solutions between the embodiments may be combined with each other, but must be based on the realization of the technical solutions by a person skilled in the art, and when the technical solutions are contradictory to each other or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope claimed in the present application.
Please refer to fig. 1 and fig. 7 in combination, fig. 1 is a flowchart of an IOS APP automatic publishing method according to an embodiment of the present application. Fig. 7 is a schematic diagram of an IOS APP automatic publishing system provided in the embodiment of the present application. The IOS APP automatic release system 1 specifically comprises: macOS server 10 and IOS APP release management server 20. The IOS APP release management server 20 is in communication connection with the macOS server 10 to verify the application file and return a verification result, and when the verification is passed, receives the application file uploaded by the macOS server 10. The IOS APP automatic release method specifically comprises the following steps S102-S114.
Step S102, the macOS server 10 responds to a release instruction input by a user to read a local configuration file, wherein the configuration file comprises release data required by releasing an application program file, and the release data comprises a secret key ID and a unique identifier of an issuer; the issue instruction includes an access path and a code path of the configuration file, wherein the macOS server 10 reads the local configuration file according to the access path. It can be understood that, after the user selects the relevant information of the application file to be published on the publishing interface of the macOS server 10, the user clicks the submit button, the macOS server 10 receives the response and then accesses the code path corresponding to the application file selected according to the publishing interface and the access path of the configuration file, the macOS server 10 can access the code corresponding to the application file according to the code path, thereby obtaining the code path information of the application file and accessing the configuration file according to the access path of the configuration file, and reads the content in the configuration file, and determines the content in the configuration file, and reads the content in the configuration file when determining that the content in the configuration file is correct. The content in the configuration file is data required for publishing the application program file, that is, the content in the configuration file is a key ID and an issuer unique identifier corresponding to the publishing application program file.
Step S104, the macOS server 10 writes the release data and the code path into the parameters of the corresponding fields in the preset script template to form a release script. It is to be understood that the preset script template is a shell script preset by a developer, and the shell script is a computer program and is executed by a command line interpreter. And a developer sets a check block template and an uploading block template in the shell script. The check block template comprises an operation code, an APP of an instruction to be verified, a path and file name of the APP being verified, a secret key ID and a unique identifier of an issuer, wherein the specific code is xcrun alcohol-valid-APP-f [ ipa path ] -t ios-apiKey [ apiKey ] - -apiIssuser [ api _ issuer ] - -boot. The uploading block template comprises an operation code, an APP needing to upload a witness instruction, a path and a file name of the APP being uploaded, a secret key ID and a unique identifier of an issuer, and the specific code is xcrun along-upload-APP-f [ ipa path ] -t ios-api key [ api key ] - -api server [ api _ issuer ] - -boot. And the macOS server 10 performs parameter replacement according to the acquired parameter information of the release data and the code path and the corresponding field in the shell script to obtain the release script. That is, the macOS server 10 transmits the acquired code path, key ID and unique identifier of the issuer to the shell script to replace the parameters of the path and filename field of the APP being verified, the parameters of the key ID field and the parameters of the unique identifier field of the issuer in the shell script, so as to obtain the verification instruction of the application file. The macOS server 10 transmits the obtained code path, key ID and unique identifier of the issuer to the shell script to replace the parameters of the path and filename field of the APP being uploaded in the shell script, the parameters of the key ID field and the parameters of the unique identifier field of the issuer in the shell script, so as to obtain an uploading instruction of the application program file. The macOS server 10 integrates the obtained check instruction and the upload instruction to form an issue script.
In step S106, the macOS server 10 calls the issue script to generate a check instruction and an upload instruction. It is understood that, after the release script corresponding to the application program file is formed, the macOS server 10 calls the release script and executes the instructions in the release script to generate the verification instruction and the upload instruction.
In step S108, the macOS server 10 executes the check instruction and sends the check instruction to the IOS APP issue management server 20 to verify the application program file. It can be understood that, the macOS server 10 first executes the check instruction in the issue script, and sends the information in the instruction to the IOS APP issue management server 20, and the IOS APP issue management server 20 receives the data packet sent by the macOS server 10, and analyzes the data packet to obtain the instruction that needs to check the application program file, and obtains the code path, the key ID, and the parameter information in the unique identifier field of the issuer corresponding to the application program file according to the instruction. The IOS APP release management server 20 checks the application program file according to the obtained parameter information.
In step S110, the macOS server 10 receives the verification result fed back by the IOS APP release management server 20, where the verification result includes that the verification passes or fails. It can be understood that the IOS APP issue management server 20 checks the information in the check instruction sent by the macOS server 10 according to step S108, and feeds back the check result to the macOS server 10 after the check is completed, so that the macOS server 10 knows whether the application file has passed the verification.
In step S112, when the verification result is that the verification is passed, the macOS server 10 executes the upload instruction and sends the upload instruction to the IOS APP release management server 20, so as to upload the application file to the IOS APP release management server 20. It can be understood that, after the macOS server 10 receives the result fed back by the IOS APP issue management server 20, the macOS server 10 makes a determination according to the returned result, and when the verification result is that the verification is passed, the macOS server 10 calls the issue script again and executes the upload instruction in the issue script, and the macOS server 10 sends the information party in the upload instruction to the IOS APP issue management server 20. When the verification result is that the verification fails, the macOS server 10 displays the verification failure, thereby prompting the user that the current verification fails, so that the user checks the related information and reissues the related information.
In the embodiment, the issuing button is issued through electric shock on the issuing interface, so that a publisher does not need to pay more attention to the specific implementation of the inside of the issuing application program file, and can easily realize the issuing and the on-line production of the application program file only by performing simple button clicking operation according to a system established according to a scheme. And an APP special user name and a special password are not needed, so that the publishing of the application program file is safer.
Please refer to fig. 2, which is a first sub-flowchart of an IOS APP automatic publishing method according to an embodiment of the present application. Before step S102, the following steps S202-S204 are specifically included.
In step S202, the key ID and the unique identifier of the issuer are obtained. The user can understand that the user creates a version of the application program file to be issued on the developer account platform, creates a P8 key file under the version of the corresponding application program file for downloading and saving, and obtains a key ID and an issuer unique identifier corresponding to the application program file.
Step S204, storing the obtained secret key ID and the unique identifier of the issuer. It can be understood that a developer writes a key ID and an issuer unique identifier corresponding to an application file acquired from a developer account platform into a document, and can call the document to acquire the key ID and the issuer unique identifier corresponding to the application file at any time when the key ID and the issuer unique identifier are required. The developer can also write the acquired application program file into the script, so that the application program file can be directly acquired if the application program file needs to be acquired. And when the developer issues the application program file, manually filling in the key ID and the unique identifier of the issuer corresponding to the obtained application program file in the issue interface, that is, the last method is to store the key ID and the unique identifier of the issuer corresponding to the obtained application program file by itself, and when the application program file needs to be issued, the developer manually adds the key ID and the unique identifier of the issuer.
In the embodiment, the key ID and the unique identifier of the issuer corresponding to the application file are acquired at the developer account platform and stored locally, and the acquired key ID and the unique identifier of the issuer are acquired when the application file is issued, so that the issuing of the application file is more efficient and safer.
Please refer to fig. 3, which is a second sub-flowchart of the IOS APP automatic publishing method according to an embodiment of the present application. Before step S104, the following steps S302-S308 are specifically included.
Step S302, whether a command line development tool exists is checked. It will be appreciated that before the replacement of parameters in the instruction is performed, the user is required to enter a check on the macOS server 10 to verify that a command line development tool is present so that subsequent macOS servers 10 can execute the instruction normally.
Step S304. And checking whether an application program file uploading tool exists. It can be understood that, after the user verifies that the command line tool exists on the macOS server 10 of the user, the user needs to input again to verify whether the application file uploading tool exists, so that the subsequent macOS server 10 can upload the application file to the IOS APP release management server 20 normally when receiving the message that the IOS APP release management server 20 passes the verification. In some embodiments, the application file uploading tool may be checked before the command line development tool.
Step S306, if there is no command line development tool or application file uploading tool, it is prompted that the tool is not installed. It is to be understood that when a user inputs a verification instruction of a command line development tool or an upload application file tool on the macOS server 10, if the user's macOS server 10 is not installed, the non-installation is directly prompted.
Step S308, if a command line development tool and an application program file uploading tool exist, the fact that the command line development tool and the application program file uploading tool are installed is prompted. It will be appreciated that when a user enters validation instructions for a command line development tool and/or an upload application file tool on the macOS server 10, the user is prompted directly for installation if the macOS server 10 of the user has installed the relevant tool.
In the above embodiment, whether necessary tools are installed is checked in advance, so that the application program file release failure is avoided.
Please refer to fig. 4, which is a third sub-flowchart of an IOS APP automatic publishing method according to an embodiment of the present application. Step S102 specifically includes the following steps S402 to S406.
Step S402, determining whether the content in the local configuration file is correct. It can be understood that, when the macOS server 10 calls the local configuration file, the content in the local configuration file is checked first, and it is determined first whether the content in the local configuration file is empty, whether the format of the content information is normal, and whether the content information is in a scrambled state.
Step S404, when the content in the local configuration file is correct, the content in the local configuration file is read. It can be understood that, after the macOS server 10 checks the content in the local configuration file, when it is determined that the content in the current local configuration file is correct, the content in the local configuration file is read.
In step S406, when the content in the local configuration file is incorrect, a reading failure is prompted. It can be understood that, after the macOS server 10 checks the content in the local configuration file, and when it is determined that the content in the current local configuration file is incorrect, the macOS server 10 directly prompts the user on the interface that the reading is failed and what reason is, if the content in the configuration file is empty, the macOS server 10 directly displays on the interface, and if the content is empty, the reading is failed, and if the reading is failed due to a network problem, the macOS server 10 directly displays on the interface, and the network is abnormal, and the reading is failed. Thereby facilitating the user to know what reason failed to read the local configuration file.
In the embodiment, the problem can be directly found by judging whether the reading of the local configuration file is successful, the problem is prevented from being prompted until the issuing stage, the resource waste is reduced, the problem can be more clearly solved by increasing the judgment, the problem can be conveniently modified by developers, and the time for the developers to troubleshoot the problem is reduced.
Please refer to fig. 5, which is a schematic diagram of an IOS APP automatic issuing apparatus of an IOS APP automatic issuing method according to an embodiment of the present application. The IOS APP automatic issuing device 1000 comprises an obtaining unit 100, a creating unit 200, a calling unit 300, an executing unit 400, a receiving unit 500 and an uploading unit 600.
The acquiring unit 100 is configured to read a local configuration file in response to a publishing instruction input by a user, where the configuration file includes publishing data required for publishing an application program file, and the publishing data includes a key ID and a unique identifier of an issuer; the issue instruction includes an access path and a code path of the configuration file, where the obtaining unit 100 reads the local configuration file according to the access path.
And the creating unit 200 is configured to write the release data and the code path into parameters of corresponding fields in a preset script template to form a release script.
The invoking unit 300 is configured to invoke the issue script to generate a check instruction and an upload instruction.
And an execution unit 400, configured to execute the check instruction and send the check instruction to the IOS APP issue management server 20 to verify the application program file.
A receiving unit 500, configured to receive a verification result fed back by the IOS APP release management server 20, where the verification result includes a pass verification or a failure verification.
And an uploading unit 600, configured to, when the receiving unit receives that the verification result is that the verification is passed, the executing unit sends the uploading instruction to the IOS APP release management server 20, so as to upload the application program file to the IOS APP release management server 20.
Please refer to fig. 6, which is a schematic diagram of an obtaining unit according to an embodiment of the present disclosure. The acquisition unit 100 includes a judgment unit 101, a reading unit 102, and a presentation unit 103.
A judging unit 101, configured to judge whether content in the local configuration file is correct.
The reading unit 102 is configured to read the content in the local configuration file when the determining unit determines that the content in the local configuration file is correct.
A prompting unit 103, configured to prompt that reading fails when the determining unit determines that the content in the local configuration file is incorrect.
Please refer to fig. 8 in combination, which is a schematic diagram of an internal structure of a macOS server according to an embodiment of the present application. macOS server 10 includes a computer-readable storage medium 11, a processor 12, and a bus 13. The computer-readable storage medium 11 includes at least one type of readable storage medium, which includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, and the like. The computer readable storage medium 11 may in some embodiments be an internal storage unit of the macOS server 10, such as a hard disk of the macOS server 10. The computer readable storage medium 11 may also be an external macOS server 10 storage device in other embodiments, such as a plug-in hard drive, smart Media Card (SMC), secure Digital (SD) Card, flash memory Card (Flash Card), etc. provided on the macOS server 10. Further, the computer-readable storage medium 11 may also include both an internal storage unit of the macOS server 10 and an external storage device. The computer-readable storage medium 11 can be used not only for storing application software and various types of data installed in the macOS server 10, but also for temporarily storing data that has been output or is to be output.
The bus 13 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.
Further, the macOS server 10 may also include a display component 14. The display component 14 may be a Light Emitting Diode (LED) display, a liquid crystal display, a touch-sensitive liquid crystal display, an Organic Light-Emitting Diode (OLED) touch panel, or the like. The display component 14, which may also be referred to as a display device or display unit as appropriate, displays information processed in the macOS server 10 and a user interface for displaying visualizations, among other things.
Further, the macOS server 10 may also include a communication component 15. The communication component 15 may optionally include a wired communication component and/or a wireless communication component, such as a WI-FI communication component, a bluetooth communication component, etc., typically used to establish communication connections between the macOS server 10 and other intelligent control devices.
The processor 12 may be, in some embodiments, a Central Processing Unit (CPU), controller, microcontroller, microprocessor or other data Processing chip for executing program codes stored in the computer-readable storage medium 11 or Processing data. Specifically, processor 12 executes a handler to control macOS server 10 to implement the IOS APP automated publishing method.
It is to be understood that fig. 8 only shows the macOS server 10 with components 11-15 and the IOS APP automated publishing method, and those skilled in the art will appreciate that the architecture shown in fig. 8 does not constitute a limitation of the macOS server 10, and may include fewer or more components than shown, or some components in combination, or a different arrangement of components.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, to the extent that such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, it is intended that the present application also encompass such modifications and variations.
The above-mentioned embodiments are only examples of the present invention, and the scope of the claims of the present invention should not be limited by these examples, so that the claims of the present invention should be construed as equivalent and still fall within the scope of the present invention.

Claims (10)

1. An IOS APP automatic release method is characterized in that the IOS APP automatic release method comprises the following steps:
the macOS server responds to an issuing instruction input by a user to read a local configuration file, wherein the configuration file comprises issuing data required by issuing an application program file, and the issuing data comprises a secret key ID and an issuer unique identifier; the issuing instruction comprises an access path and a code path of the configuration file, wherein the macOS server reads the local configuration file according to the access path;
the macOS server writes the release data and the code path into parameters of corresponding fields in a preset script template to form a release script;
the macOS server calls the release script to generate a check instruction and an upload instruction;
the macOS server executes the check instruction and sends the check instruction to an IOS APP release management server to verify the application program file;
the macOS server receives a verification result fed back by the IOS APP release management server, wherein the verification result comprises that the verification is passed or fails; and
and when the verification result is that the verification is passed, the macOS server executes the uploading instruction and sends the uploading instruction to the IOS APP release management server so as to upload the application program file to the IOS APP release management server.
2. The IOS APP automatic release method of claim 1, wherein when a macOS server receives a release instruction input by a user and obtains a first execution instruction, the macOS server specifically includes before reading a local configuration file:
acquiring a secret key ID and an unique identifier of an issuer; and
and storing the acquired secret key ID and the unique identifier of the issuer.
3. The IOS APP automated release method of claim 1, wherein before the macOS server writes the received release data in the parameters of the corresponding fields in the preset script template to form the release script, it comprises:
checking whether a command line development tool exists;
checking whether an application program file uploading tool exists;
if no command line development tool or application program file uploading tool exists, prompting that the command line development tool is not installed; and
and if a command line development tool and an application program file uploading tool exist, prompting that the command line development tool and the application program file uploading tool are installed.
4. The IOS APP automated release method of claim 3, wherein when a command line development tool is present, performing a check whether an upload application file tool is present.
5. The IOS APP automated release method of claim 1, wherein the pre-defined script templates include a check block template and an upload block template, the check block template including an opcode, an APP of the instruction to be verified, a path and file name of the APP being verified, a key ID, and an issuer unique identifier; the uploading block module comprises an operation code, an APP to be uploaded with a witness instruction, a path and a file name of the APP being uploaded, a secret key ID and an unique identifier of an issuer.
6. The IOS APP automatic release method of claim 1, wherein the macOS server reading the local configuration file in response to the release instruction input by the user specifically comprises:
judging whether the content in the local configuration file is correct or not;
when the content in the local configuration file is correct, reading the content in the local configuration file; and
when the content in the local configuration file is incorrect, reading failure is prompted.
7. The utility model provides an automatic release device of IOS APP which characterized in that, the automatic release device of IOS APP includes:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for responding to a publishing instruction input by a user to read a local configuration file, the configuration file comprises publishing data required by publishing an application program file, and the publishing data comprises a secret key ID and an unique identifier of an issuer; the issuing instruction comprises an access path and a code path of the configuration file, wherein the macOS server reads the local configuration file according to the access path:
the creating unit is used for writing the release data and the code path into parameters of corresponding fields in a preset script template to form a release script;
the calling unit is used for calling the issuing script to generate a checking instruction and an uploading instruction;
the execution unit is used for executing the check instruction and sending the check instruction to the IOS APP release management server so as to verify the application program file;
the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a verification result fed back by an IOS APP release management server, and the verification result comprises verification passing or verification failure; and
and the uploading unit is used for sending the uploading instruction to the IOS APP release management server by the execution unit when the receiving unit receives that the verification result is that the verification is passed, so as to upload the application program file to the IOS APP release management server.
8. The IOS APP automated release apparatus of claim 7, wherein the fetch unit comprises:
the judging unit is used for judging whether the content in the local configuration file is correct or not;
the reading unit is used for reading the content in the local configuration file when the judging unit judges that the content in the local configuration file is correct; and
and the prompting unit is used for prompting that reading fails when the judging unit judges that the content in the local configuration file is incorrect.
9. A macOS server, the macOS server comprising:
a computer readable storage medium for storing program instructions; and
the processor executes the program instructions to implement the IOS APP automated issue method of any of claims 1 to 6.
10. An IOS APP automatic release system specifically comprises:
a macOS server, the macOS server being the macOS server of claim 9;
the IOS APP release management server is in communication connection with the macOS server and used for verifying the application program file, returning a verification result and receiving the application program file uploaded by the macOS server when the verification is passed.
CN202210986063.3A 2022-08-17 2022-08-17 IOS APP automatic release method, macOS server and system Active CN115065670B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210986063.3A CN115065670B (en) 2022-08-17 2022-08-17 IOS APP automatic release method, macOS server and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210986063.3A CN115065670B (en) 2022-08-17 2022-08-17 IOS APP automatic release method, macOS server and system

Publications (2)

Publication Number Publication Date
CN115065670A CN115065670A (en) 2022-09-16
CN115065670B true CN115065670B (en) 2022-12-23

Family

ID=83208300

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210986063.3A Active CN115065670B (en) 2022-08-17 2022-08-17 IOS APP automatic release method, macOS server and system

Country Status (1)

Country Link
CN (1) CN115065670B (en)

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6836794B1 (en) * 1998-09-21 2004-12-28 Microsoft Corporation Method and system for assigning and publishing applications
US7886267B2 (en) * 2006-09-27 2011-02-08 Symantec Corporation Multiple-developer architecture for facilitating the localization of software applications
US11593075B2 (en) * 2015-11-03 2023-02-28 Open Text Sa Ulc Streamlined fast and efficient application building and customization systems and methods
CN108469957A (en) * 2018-03-08 2018-08-31 平安科技（深圳）有限公司 Using packing method for uploading, device, computer equipment and storage medium
CN110543335A (en) * 2019-08-15 2019-12-06 上海易点时空网络有限公司 Application program configuration management method and system
CN110851135A (en) * 2019-09-12 2020-02-28 中国平安财产保险股份有限公司 Automatic application program building and uploading method and device, computer equipment and storage medium
CN112564989A (en) * 2021-02-23 2021-03-26 鲁班(北京)电子商务科技有限公司 Application deployment method and device
CN114429408B (en) * 2021-12-31 2023-10-20 中国南方电网有限责任公司 Method, device, equipment and system for checking configuration file of intelligent substation
CN114827133A (en) * 2022-06-27 2022-07-29 浪潮云信息技术股份公司 Application software management method and device and computer

Also Published As

Publication number Publication date
CN115065670A (en) 2022-09-16

Similar Documents

Publication Publication Date Title
CN112118286B (en) Multi-thread link tracking method and device based on MDC and computer readable storage medium
CN110647471B (en) Interface test case generation method, electronic device and storage medium
CN109582907B (en) Method, device and equipment for verifying integrity of webpage resources and readable storage medium
CN105302722B (en) CTS automatic testing method and device
CN109658542B (en) Diagnostic parameter data verification method, diagnostic parameter data verification device, vehicle diagnostic equipment and storage medium
CN110659198A (en) Application program test case execution method and device and software test system
CN108804315B (en) Test method and device applied to dynamic development, electronic equipment and storage medium
CN108427639B (en) Automated testing method, application server and computer readable storage medium
CN112039900A (en) Network security risk detection method, system, computer device and storage medium
CN115357434A (en) Complete machine testing method, device to be tested, computer device and storage medium
CN111400167A (en) Redfish service compliance verification method, device, equipment and medium
CN114218072A (en) Test script generation method and device, storage medium and computer equipment
CN112818270B (en) Data cross-domain transfer method and device and computer equipment
CN109388420A (en) Application upgrade test method, device, computer equipment and storage medium
CN115065670B (en) IOS APP automatic release method, macOS server and system
CN112947964A (en) Chip firmware updating method, device, equipment and storage medium
CN112181836A (en) Test case generation method, system, device and storage medium
US20240031166A1 (en) Web-side data signature method and apparatus and computer device
US11146571B2 (en) Data transmission method, apparatus, terminal device, and medium
CN110837500A (en) Data screening method and device based on local embedded window and computer equipment
CN114253642B (en) System information processing method, device, electronic equipment and medium
CN113655737B (en) Vehicle-mounted electronic controller rapid upgrading system and method transmitted through CAN
CN111737129A (en) Service control method, service control device, computer readable medium and electronic equipment
CN112261072A (en) Service calling method, device, equipment and storage medium
EP2768206A1 (en) Download management method and device based on android browser

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant