Application program auditing state query method and device, computer equipment and storage medium

Abstract

The invention provides an application program auditing state query method. The method comprises the steps of determining a query target and login information in response to user input, logging in a platform according to the login information for a target application program which is not completed in an auditing state and meets a timing trigger condition in a target platform, obtaining the auditing state according to a preset data obtaining mode and updating a record, and then sending a notification to a user according to the auditing state, and then judging whether the target application program in auditing exists or not according to the auditing state record, if so, repeating the previous operation, and if not, stopping the query on the platform. According to the method, the query efficiency and the automation degree can be improved, and excessive manual operation of a user is not needed. Excessive query is avoided through timed triggering conditions, and resource waste is prevented. Notifications can be sent to the user in time, the user can take corresponding measures according to the accurate auditing progress situation, and the overall efficiency of application program development and release can be improved.

Description

Technical Field

[0001] The present application relates to the field of software development technology, and in particular to an application audit status query method, device, computer equipment and storage medium. Background Art

[0002] After an application is developed and tested by a developer, it will be submitted to an application publishing platform for publishing applications. The reviewer of the application publishing platform will review it. Only after the review is passed will the application be published on the application publishing platform for ordinary users to download and use. As the platform review becomes increasingly strict, the problem of review rejection often occurs. In traditional solutions, it is often necessary to rely on manual review to check the review status, but there are many platforms where applications need to be published, and there may be more than one application that needs to be checked, so there is a problem of low efficiency and affecting the normal launch of applications. Summary of the invention

[0003] The purpose of this application is to solve at least one of the above-mentioned technical deficiencies, and in particular to provide a set of efficient application review status query solutions.

[0004] In a first aspect, the present application provides a method for querying the application review status, comprising:

[0005] In response to user input, determining one or more target applications and one or more target platforms, and obtaining login information of the target platforms;

[0006] For any target platform, when the audit status record of any target application on the target platform is not completed, if the timing trigger condition corresponding to the target application is met, the target platform is logged in according to the login information;

[0007] According to a preset data acquisition method corresponding to the target platform, the audit status of the target application is obtained from the target platform, and the audit status record is updated;

[0008] Send notifications to users based on the review status;

[0009] Determine whether there are any target applications that have not been reviewed yet based on the review status record;

[0010] If so, then for any target platform, if the audit status record of any target application on the target platform is not completed, if the timing trigger condition corresponding to the target application is met, then the step of logging into the target platform continues to be executed according to the login information;

[0011] If not, stop querying on the target platform.

[0012] In one embodiment, the timing trigger condition includes a trigger interval, and after obtaining the review status of the target application from the target platform, further includes:

[0013] If the audit status of the target application is still not completed, and the audit timing value corresponding to the target application is less than the average audit duration corresponding to the target application, then the trigger interval corresponding to the target application is shortened.

[0014] In one embodiment, shortening the trigger interval corresponding to the target application includes:

[0015] According to the gap between the audit timing value and the average audit duration, shorten the trigger interval corresponding to the target application.

[0016] In one embodiment, shortening the trigger interval corresponding to the target application according to the difference between the audit timing value and the average audit duration includes:

[0017] The gap is multiplied by a preset adjustment coefficient, and the multiplication result is subtracted from the current trigger interval to obtain a new trigger interval.

[0018] In one embodiment, after obtaining the review status of the target application from the target platform, the method further includes:

[0019] If the audit status of the target application is still not completed, and the audit timing value corresponding to the target application is greater than or equal to the average audit duration corresponding to the target application, the trigger interval corresponding to the target application is maintained and a timeout prompt is issued to the user.

[0020] In one embodiment, the process of obtaining the average review time includes:

[0021] Determine the type of the target application;

[0022] Get the historical review time of other applications of the same type on the target platform, and calculate the average review time based on the historical review time.

[0023] In one embodiment, the average audit time is calculated based on historical audit records, including:

[0024] The average review time is calculated based on the historical review time and its corresponding weight. The farther the review date of other applications is from today's date, the smaller the corresponding weight of the historical review time of other applications is.

[0025] In a second aspect, the present application provides an application review status query device, comprising:

[0026] A response module, for determining one or more target applications and one or more target platforms in response to a user input, and obtaining login information of the target platforms;

[0027] A simulation login module is used for logging into any target platform according to the login information if the audit status record of any target application on the target platform is not completed and the timing trigger condition corresponding to the target application is met;

[0028] A status acquisition module, used to obtain the audit status of the target application from the target platform according to a preset data acquisition method corresponding to the target platform, and update the audit status record;

[0029] Notification module, used to send notifications to users based on the review status;

[0030] A judgment module, used to judge whether there are any target applications that have not been reviewed yet according to the review status records;

[0031] A first execution module is used for returning to any target platform, if the audit status record reflects that there are still target applications that have not been audited on the target platform, and if the audit status record of any target application on the target platform is not completed, if the timing trigger condition corresponding to the target application is met, then the step of logging into the target platform continues to be executed according to the login information;

[0032] The second execution module is used to stop querying the target platform when the audit status record shows that there is no target application program on the target platform that has not been audited.

[0033] In a third aspect, the present application provides a computer device comprising one or more processors and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the steps of the application audit status query method in any of the above-mentioned embodiments are executed.

[0034] In a fourth aspect, a storage medium stores computer-readable instructions, which, when executed by one or more processors, cause the one or more processors to execute the steps of the application audit status query method in any of the above-mentioned embodiments.

[0035] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0036] Based on the application review status query method in this application, the target application and target platform are determined in response to user input and the platform login information is obtained. For the target application whose review status is not completed and the timing trigger condition is met in the target platform, the platform is logged in according to the login information, the review status is obtained and the record is updated according to the preset data acquisition method, and then a notification is sent to the user according to the review status. Then, according to the review status record, it is determined whether there are still target applications under review. If there are, the operation of logging in to the platform to query when the previous review is not completed and the timing trigger condition is met is repeated. If not, the query on the platform is stopped. This method can improve the query efficiency and automation level. The system automatically obtains the login information to log in to the platform to query the review status without the user having to do too much manual operation. In addition, excessive queries are avoided through timing trigger conditions, and queries are stopped after all reviews are completed to prevent waste of resources. It can also provide accurate information, update the review status record in a timely manner, and send notifications to users. Users can take corresponding measures based on the accurate review progress, which helps to improve the overall efficiency of application development and release. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0038] Figure 1 A flowchart of a method for querying the application review status provided by one embodiment of the present application;

[0039] Figure 2 An internal structure diagram of a computer device provided for one embodiment of the present application. DETAILED DESCRIPTION

[0040] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, and do not belong to all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0041] This application provides a method for querying the application review status. Figure 1 , including steps S102 to S112.

[0042] S102, in response to the user's input, determining one or more target applications and one or more target platforms, and obtaining login information of the target platforms.

[0043] It can be understood that the user here refers to the software developer, and the target application can be understood as the specific software that the user is concerned about, such as a newly developed mobile game application, an office software, etc. The target platform is the platform where these applications need to be reviewed and released, such as major mobile application stores (such as Apple's App Store, Android application store, etc.), software distribution platforms, etc. Login information includes user name, password and other necessary information for logging into the target platform, so as to perform subsequent operations and inquiries on the platform.

[0044] The user input may be provided through a graphical user interface, command line, or other input methods. The user may specify more than one target application and target platform because a developer may develop multiple applications at the same time and want to publish these applications on different platforms. When the user input is received, the target platform and target application can be parsed from it. After determining the target application and target platform, the system needs to obtain the login information of the target platform in order to be able to log in to the target platform in subsequent steps to query the audit status. By obtaining the login information, the system can automatically log in to the target platform without relying on manual operation by the user, thereby improving query efficiency and automation.

[0045] S104, for any target platform, when the audit status record of any target application on the target platform is not completed, if the timing trigger condition corresponding to the target application is met, log in to the target platform according to the login information.

[0046] It can be understood that when there are two or more target platforms, each target platform will be queried in the manner of steps S104 to S112. Each target platform has a corresponding audit status record, which is used to record the audit status of the target application on this target platform, for example, "under review", "passed", "failed", etc. When the audit status recorded in the audit status record of any target application is empty or under review, it can be determined that the target application is not completed and the audit status query needs to be continued.

[0047] This embodiment adopts a timed query method. When querying the target application, it is necessary to determine whether the trigger interval corresponding to the target application is met, that is, whether the trigger interval has been reached since the last query. The audit time spent by each application on the same platform may be different, and each target application can use the corresponding timed trigger condition. The timed trigger condition is set to avoid querying the audit status too frequently and save system resources. If the timed trigger condition is met, the system will use the previously obtained login information to log in to the target platform. The login process involves simulating the user's login behavior.

[0048] In the simulated login process, if the target platform only needs an account and password, you can simulate the filling operation on the front-end interface to fill in the account and password and complete the login. You can also simulate HTTP requests to send the login information to the login interface of the audit platform and process the response after login (such as determining whether the login is successful, handling login failures, etc.). If a mobile phone number is required for verification, the login information entered by the user should also include the mobile phone number, and the mobile phone number should be registered with the SMS gateway service before using this method. When the target platform sends an SMS verification code, the SMS gateway can receive the verification code, and then receive the verification code through the SMS gateway API, and then automatically fill it into the verification code input box of the target platform. If there is a graphic verification code, it can be automatically recognized using a neural network model. For example, collect a large number of graphic verification code samples of the target platform. Label these verification code images and mark the characters or patterns in them. Next, train the labeled verification code samples. The trained model can be used to recognize new graphic verification codes. Other mature technologies can also be used in the simulated login process, which will not be repeated here.

[0049] If the target platform is successfully logged in, the subsequent steps can be continued. If the login fails, an error message can be issued to inform the user of the reason for the login failure, so that the user can make timely repairs, such as re-entering login information, developing a new simulated login method, etc.

[0050] S106, obtaining the audit status of the target application from the target platform according to a preset data acquisition method corresponding to the target platform, and updating the audit status record.

[0051] It is understandable that since different platforms may have different interfaces, data formats, and query methods, it is necessary to set specific data acquisition methods for each platform. Different target platforms may have different ways to provide application review status information. Some platforms may provide public APIs that allow developers to directly obtain review status data of specific data structures by sending requests. Data can be obtained through the python crawler interface. In addition, for this case, since the review status data may contain data that some users do not care about, the fields corresponding to the content of interest can be determined according to the API manual provided by the target platform. After obtaining the review status data, you can filter according to these fields, such as AppName (application name), AppState (application status), AppStateDesc (application status description), and Time (status time).

[0052] However, for target platforms that do not provide an API, the review status will only be displayed on the front-end page. In this case, you can use a script written in Java or Python to automatically find the HTML element containing the review status information from the web page elements on the front-end page. For example, the review status may be displayed on a specific tag, or a Tags, these specific tags can be used as flags to search and target the desired page elements.

[0053] After obtaining the audit status, the audit status record needs to be updated according to the latest audit status. If the audit status of the newly obtained target application is consistent with the record, no update is required. Otherwise, the audit status of the target application in the record should be updated to the newly obtained audit status. Updating the audit status record can ensure that the latest audit status of the target application on each target platform is always mastered, providing users with accurate notifications and decision-making basis. The audit status records of different target platforms can be stored in the same database. After obtaining the audit status data, the audit status records can be updated using the update instructions of the database (such as sql instructions). The audit status record can also be displayed on the front-end interface corresponding to this method for user viewing. In addition, in order to facilitate data processing, if the acquired data is not in the required data format (such as json), the acquired data will generally be converted to this format. If the conversion fails, a prompt can be issued to the user.

[0054] In addition, some audit platforms encrypt the data, such as symmetric encryption (AES, DES), asymmetric encryption (RSA, ECC) or SHA-256, etc. At this time, it is necessary to obtain the corresponding decryption method from the platform so that valid data can be parsed out.

[0055] S108, sending a notification to the user based on the review status.

[0056] It is understood that after obtaining the review status of the target application, a notification will be sent to the user based on this status. The purpose of the notification is to let the user know the review progress of the application on each target platform in a timely manner so that the user can take appropriate measures. For example, if the review status is "review passed", the user can prepare to publish and promote the application; if the review status is "review failed", the user can view the reason for the review failure and make corresponding modifications and resubmit. The notification method can be set according to the user's needs and preferences. Common methods include email notification, SMS notification and instant messaging software notification. Email notifications can be sent by calling the API of a third-party mail service provider, or SMS notifications can be sent using an SMS gateway. By sending notifications to users in a timely manner, users can manage and track the review process of the application more efficiently and improve the efficiency of development and release.

[0057] In addition, in order to prevent too many notification messages, you can choose a combination of multiple notification methods. For example, since users check instant messaging software more frequently, the reminder effect is stronger. After each query is completed, the newly queried audit status will be sent to the user via email to facilitate the user to leave a trace of the audit record. Only when the audit status changes, it will be notified through the instant messaging software, so that users can advance their work in a timely manner according to the latest audit status.

[0058] S110, judging whether there are any target applications that have not been reviewed yet according to the review status record.

[0059] When the audit status record shows that there are still target applications that have not been audited (passed or failed) among all the target applications that need to be queried for this target platform, it is necessary to return to step S104 to continue to query the status of the target applications that have not been audited. If all target applications of this target platform have been audited, it is possible to go to step S112 to complete the query of a target platform.

[0060] S112, stop querying the target platform.

[0061] Based on the application review status query method in this application, the target application and target platform are determined in response to user input and the platform login information is obtained. For the target application whose review status is not completed and the timing trigger condition is met in the target platform, the platform is logged in according to the login information, the review status is obtained and the record is updated according to the preset data acquisition method, and then a notification is sent to the user according to the review status. Then, according to the review status record, it is determined whether there are still target applications under review. If there are, the operation of logging in to the platform to query when the previous review is not completed and the timing trigger condition is met is repeated. If not, the query on the platform is stopped. This method can improve the query efficiency and automation level. The system automatically obtains the login information to log in to the platform to query the review status without the user having to do too much manual operation. In addition, excessive queries are avoided through timing trigger conditions, and queries are stopped after all reviews are completed to prevent waste of resources. It can also provide accurate information, update the review status record in a timely manner, and send notifications to users. Users can take corresponding measures based on the accurate review progress, which helps to improve the overall efficiency of application development and release.

[0062] In one embodiment, the timing trigger condition includes a trigger interval, and after obtaining the review status of the target application from the target platform, it also includes: if the review status of the target application is still not completed, and the review timing value corresponding to the target application is less than the average review time corresponding to the target application, then shortening the trigger interval corresponding to the target application.

[0063] It can be understood that the trigger interval is a key element in the timing trigger condition, which refers to the time interval for the system to query the next audit status. For example, if the trigger interval is set to 1 hour, the system will query the audit status of the target application every 1 hour. The audit timing value is a value used to record the length of time the target application has experienced from the start of the audit to the current moment. For example, 30 minutes have passed since an application was submitted for review, so this 30 minutes is the audit timing value of the application at this time. The average audit time is a statistical value for a specific type of target application on the target platform. It is calculated by analyzing the historical audit time of other applications of the same type on the platform, reflecting the audit time that such applications usually take on the platform.

[0064] In traditional solutions, since manual query is required, the query frequency is not too high, which may cause the application to fail the review and not be modified for a long time, or pass the review but not be further advanced for a long time. In order to solve this problem, after the system obtains the review status of the target application from the target platform, if the review status is still not completed, the system will further compare the review timing value and the average review duration. If the review timing value is less than the average review duration, it means that the review time of the application has not exceeded the average review time of applications of the same type. In this case, in order to obtain the review status more timely, the system will shorten the trigger interval corresponding to the target application, that is, continue to query the application status more frequently.

[0065] In one of the embodiments, the narrowing method can be to shorten the trigger interval corresponding to the target application according to the difference between the audit timing value and the average audit duration. That is, the closer the audit timing value is to the average audit duration, the smaller the trigger interval used. This method is adopted considering that the closer the audit timing value is to the average audit duration, the greater the probability that the audit status of the target application will change in the next query. The difference between the audit timing value and the average audit duration can reflect the degree of closeness between them, and can also reflect the probability of the audit status change in the next query, which can serve as a basis for shortening the trigger interval.

[0066] In one embodiment, based on the gap between the audit timing value and the average audit duration, the trigger interval corresponding to the target application is shortened, including: multiplying the gap with a preset adjustment coefficient, and subtracting the multiplication result from the current trigger interval to obtain a new trigger interval.

[0067] It can be understood that the audit timing value t and the average audit time are calculated The gap , and then set a linear function based on this gap to reduce the trigger interval. For example, the new trigger interval , where m is the adjustment coefficient. Suppose a game application is under review in the Android App Store, and its trigger interval is originally set to 5 hours, the average review time is 10 hours, the current review timing value is 5 hours, and the preset adjustment coefficient is 0.4. Then the difference between the review timing value and the average review time is 5 hours, and the multiplication result is 2 hours. The new trigger interval is 5-2=3 hours. In this way, the next query will be 3 hours later. That is, when the review timing value is 8 hours, then the difference between the review timing value and the average review time is 2 hours, and the multiplication result is 0.4 hours, and the new trigger interval is 3-0.4=2.6 hours.

[0068] In one of the embodiments, after obtaining the audit status of the target application from the target platform, it also includes: if the audit status of the target application is still not completed, and the audit timing value corresponding to the target application is greater than or equal to the average audit duration corresponding to the target application, then the trigger interval corresponding to the target application is maintained, and a timeout prompt is issued to the user.

[0069] It is understandable that if the audit status is still not completed and the audit timing value is greater than or equal to the average audit duration, this means that the audit time of the application has reached or exceeded the average audit time of applications of the same type. At this time, the system will maintain the trigger interval corresponding to the target application without adjustment, and issue a timeout prompt to the user. This is because although the audit has not been completed, the average duration has been reached, and continued frequent queries may not bring more valid results. Maintaining the original trigger interval can avoid excessive consumption of system resources. At the same time, a timeout prompt is issued to the user to let the user know that the audit situation may be abnormal or require further attention. Still using the above example to illustrate, the next query will be in 2.6 hours, that is, when the audit timing value is 10.6 hours, then the audit timing value is greater than the average audit duration, and the trigger interval of 2.6 hours can be maintained.

[0070] In one embodiment, the process of obtaining the average audit time includes: determining the type of the target application, obtaining the historical audit time of other applications of the same type on the target platform, and calculating the average audit time based on the historical audit time.

[0071] It can be understood that regarding the process of obtaining the average review time, the type of the target application must first be determined, such as a social application, a game application, or a tool application. Then the historical review time of other applications of the same type on the target platform is obtained. Since the review situation on different dates may be affected by various factors such as changes in platform policies and the number of reviewers, when calculating the average review time, it can be calculated based on the historical review time and its corresponding weight. Among them, the farther the date of the review of other applications is from the date of the day, the smaller the weight corresponding to its historical review time. In this way, the average review time can better reflect the actual situation of the current platform's review of this type of application. For example, for a new social application, when calculating its average review time, if there is historical review time data from one year ago and historical review time data from one month ago, the data from one month ago will be given a higher weight because it better represents the current review situation. The average review time calculated in this way can be used as a reference standard for measuring the review progress of the target application more accurately.

[0072] The present application provides an application audit status query device, including a response module, a simulation login module, a status acquisition module, a notification module, a judgment module, a first execution module and a second execution module.

[0073] The response module is used to respond to the user's input, determine more than one target application and more than one target platform, and obtain the login information of the target platform. The simulation login module is used for any target platform, if the audit status record of any target application on the target platform is not completed, if the timing trigger condition corresponding to the target application is met, then log in to the target platform according to the login information. The status acquisition module is used to obtain the audit status of the target application from the target platform according to the preset data acquisition method corresponding to the target platform, and update the audit status record. The notification module is used to send a notification to the user according to the audit status. The judgment module is used to judge whether there are still unaudited target applications according to the audit status record. The first execution module is used to return to any target platform, if the audit status record of any target application on the target platform is not completed, if the timing trigger condition corresponding to the target application is met, then the step of logging in to the target platform continues to be executed according to the login information. The second execution module is used to stop the query on the target platform if the audit status record reflects that there are no unaudited target applications on the target platform.

[0074] For the specific limitations of the application audit status query device, please refer to the limitations of the application audit status query method above, which will not be repeated here. The above-mentioned modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0075] The present application provides a computer device, including one or more processors and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the one or more processors, the steps of the application audit status query method in any of the above embodiments are executed.

[0076] Indicatively, if Figure 2 As shown, Figure 2 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. Figure 2 The computer device 200 includes a processing component 202, which further includes one or more processors, and a memory resource represented by a memory 201, for storing instructions executable by the processing component 202, such as an application. The application stored in the memory 201 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 202 is configured to execute instructions to perform the steps of the application audit status query method of any of the above embodiments.

[0077] The computer device 200 may further include a power supply component 203 configured to perform power management of the computer device 200 , a wired or wireless network interface 204 configured to connect the computer device 200 to a network, and an input / output (I / O) interface 205 .

[0078] The present application provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the application audit status query method in any of the above embodiments.

[0079] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0080] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can refer to each other.

[0081] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for querying application audit status, characterized in that: include: In response to user input, determining one or more target applications and one or more target platforms, and obtaining login information of the target platforms; For any of the target platforms, when the audit status record of any of the target applications on the target platform is not completed, if the timing trigger condition corresponding to the target application is met, log in to the target platform according to the login information; According to a preset data acquisition method corresponding to the target platform, obtaining the audit status of the target application from the target platform, and updating the audit status record; Sending a notification to the user according to the review status; Determining whether there is any target application that has not been reviewed yet according to the review status record; If so, returning to the step of logging into the target platform for any one of the target platforms, if the audit status record of any one of the target applications on the target platform is not completed, and if the timing trigger condition corresponding to the target application is met, then continuing to execute the step of logging into the target platform according to the login information; If not, stop querying the target platform.

2. The method for querying the application audit status according to claim 1, characterized in that: The timing trigger condition includes a trigger interval, and after obtaining the audit status of the target application from the target platform, further includes: If the audit status of the target application is still not completed, and the audit timing value corresponding to the target application is less than the average audit duration corresponding to the target application, then the trigger interval corresponding to the target application is shortened.

3. The method for querying the application audit status according to claim 2, characterized in that: The reducing the trigger interval corresponding to the target application comprises: According to the difference between the audit timing value and the average audit duration, the trigger interval corresponding to the target application is shortened.

4. The method for querying the application audit status according to claim 3, characterized in that: The step of reducing the trigger interval corresponding to the target application according to the gap between the audit timing value and the average audit duration includes: The gap is multiplied by a preset adjustment coefficient, and the multiplication result is subtracted from the current trigger interval to obtain a new trigger interval.

5. The method for querying the application audit status according to claim 2, characterized in that: After obtaining the review status of the target application from the target platform, the method further includes: If the audit status of the target application is still not completed, and the audit timing value corresponding to the target application is greater than or equal to the average audit duration corresponding to the target application, the trigger interval corresponding to the target application is maintained and a timeout prompt is issued to the user.

6. The method for querying the application audit status according to claim 2, characterized in that: The process of obtaining the average review time includes: Determining the type of the target application; Obtain the historical review durations of other applications of the same type on the target platform, and calculate the average review duration based on each of the historical review durations.

7. The method for querying the application audit status according to claim 6, characterized in that: The calculating the average audit duration according to the historical audit records includes: The average review time is calculated based on the historical review time and its corresponding weight; wherein, the farther the date of the review of the other applications is from the date of today, the smaller the weight corresponding to the historical review time of the other applications is.

8. An application audit status query device, characterized in that: include: A response module, for determining one or more target applications and one or more target platforms in response to a user input, and obtaining login information of the target platforms; A simulation login module, for logging into any of the target platforms according to the login information, if the audit status record of any of the target applications on the target platform is not completed and if the timing trigger condition corresponding to the target application is met; A status acquisition module, used to acquire the audit status of the target application from the target platform according to a preset data acquisition method corresponding to the target platform, and update the audit status record; A notification module, used to send a notification to the user according to the review status; A judgment module, used for judging whether there is any target application program that has not been reviewed yet according to the review status record; A first execution module is used for returning to the step of logging into the target platform continuously according to the login information when the audit status record reflects that the target platform still has the target application that has not been audited, and when the audit status record of any target application on the target platform is not completed, if the timing trigger condition corresponding to the target application is satisfied; The second execution module is used to stop querying the target platform when the audit status record reflects that there is no target application program whose audit has not been completed on the target platform.

9. A computer device, characterized in that: It includes one or more processors and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the one or more processors, the steps of the application audit status query method described in any one of claims 1-7 are executed.

10. A storage medium, characterized in that: The storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the application audit status query method as described in any one of claims 1-7.

Images