Method, device, equipment and medium for processing first start of enterprise mobile application

Abstract

The application relates to a processing method and device for the first start of an enterprise mobile application, an equipment and a medium. The method comprises the following steps: obtaining a first mark when the enterprise mobile application is started for the first time; judging whether the first mark meets a first start condition; if the first mark meets the first start condition, automatically writing preset default configuration information in the enterprise mobile application, wherein the default configuration information at least comprises a back-end service address, a communication port and an enterprise internal network WiFi white list; persistently storing the default configuration information, and clearing the first mark. The application can realize automatic configuration without manual input of operation and maintenance personnel, avoids application start-up crash caused by missing or incorrect configuration, ensures that the application can complete basic initialization in various terminal environments, and solves the problems of configuration omission, format error or initialization failure caused by manual configuration or external injection in the prior art.

Description

Technical Field

[0001] This application relates to the field of mobile terminal configuration management technology, and in particular to a method, apparatus, device and medium for processing the first launch of an enterprise mobile application. Background Technology

[0002] In the initial deployment of enterprise-level mobile applications, the application typically needs to pre-configure critical operating parameters, including security policy information such as backend service addresses, communication ports, and trusted Wi-Fi network whitelists. These configurations are prerequisites for the application to start normally and communicate securely.

[0003] In current practice, initialization settings are generally completed by manual input or injection of external configuration files.

[0004] However, manual configuration is prone to errors such as missing or incorrect key parameters due to operational oversights, formatting errors, or version mismatches. Furthermore, if the external configuration mechanism fails to take effect in a timely manner or the network is unreachable, the application will be unable to complete initialization on the first startup due to the lack of necessary configuration, which may lead to problems such as startup failure, abnormal loading of security components, or failure of page stack management. Summary of the Invention

[0005] This application provides a method, apparatus, device, and medium for processing the first launch of an enterprise mobile application, aiming to solve the problems of configuration omissions, format errors, or initialization failures caused by traditional reliance on manual configuration or external injection.

[0006] In a first aspect, embodiments of this application provide a method for processing the initial launch of an enterprise mobile application, characterized in that the method includes: Obtain the initial tag when the enterprise mobile application is launched for the first time; Determine whether the initial marker meets the initial startup conditions; If the initial tag meets the initial launch conditions, then preset default configuration information is automatically written into the enterprise mobile application. The default configuration information includes at least the backend service address, communication port, and enterprise intranet WiFi whitelist. The default configuration information is persistently stored, and the initial tag is cleared.

[0007] A further technical solution is that, after persistently storing the default configuration information, the method further includes: In the main application process, a security component is loaded and a global exception catcher is registered based on the default configuration information; Register Activity lifecycle callbacks and maintain a thread-safe page stack; wherein, the page stack is used to uniformly manage the opening and closing of all Activities; the global exception catcher catches unhandled exceptions in page stack operations, realizing coordinated management of the main process's security capabilities and page lifecycle.

[0008] In response to the exit command, all Activities in the page stack are closed in batches, and the non-main process and the main process are exited.

[0009] A further technical solution is that the exit from the non-main process and the main process includes: Exit the non-main process first; The main process exits only after the non-main process has finished exiting.

[0010] A further technical solution is that, after persistently storing the default configuration information, the method further includes: Create an external log directory; Configure a log rolling strategy based on the default configuration information.

[0011] A further technical solution is that the log rolling strategy adopts a combination of "pre-set directory + periodic file division + capacity / quantity / time constraint cleanup".

[0012] A further technical solution is that, after creating the external log directory, the method further includes: When a single file in the log directory exceeds the threshold or the retention window, cleanup or overwriting is performed; at the same time, historical logs that have exceeded the retention period are deleted to ensure that space is controllable and easy to audit and trace.

[0013] During the log writing process, when the size of a single log file reaches a preset size threshold, writing to the file stops and a new log file is generated; wherein, the log files are generated according to a preset time period, and each log file corresponds to a recording time; In response to log file generation or application startup, scan all log files in the log directory and delete the target historical log file; Wherein, the recording time of the target historical log file exceeds the preset retention period, or the number of files in the target historical log file exceeds the preset retention number.

[0014] A further technical solution is that, after loading the security component and registering the global exception catcher based on the default configuration information in the application's main process, the method further includes: In the main process, the current application version number is synchronized to the application version, and a location monitoring service for the application is started.

[0015] Get the current application version number; Write the version number of the current application to the local database; Start the location monitoring service for the application; Location information is collected using the location monitoring service. The location information is encrypted using the security component.

[0016] Secondly, embodiments of this application also provide a processing apparatus for the first launch of an enterprise mobile application, which includes a unit for performing the above-described method.

[0017] Thirdly, embodiments of this application also provide a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described method.

[0018] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the above-described method.

[0019] This application provides a method, apparatus, device, and medium for processing the first launch of an enterprise mobile application. The method includes: upon the first launch of the enterprise mobile application, obtaining a first-launch marker; determining whether the first-launch marker meets the first-launch conditions; if the first-launch marker meets the first-launch conditions, automatically writing preset default configuration information into the enterprise mobile application, the default configuration information including at least a backend service address, a communication port, and an enterprise intranet WiFi whitelist; persistently storing the default configuration information; and clearing the first-launch marker.

[0020] This application's embodiments automatically detect the first-time flag when an enterprise mobile application is launched for the first time. After confirming that it is the first launch, it automatically writes and persistently stores the preset default configuration information (including key parameters such as backend service address, communication port, and enterprise intranet WiFi whitelist). Automatic configuration can be achieved without relying on manual input by operation and maintenance personnel, avoiding application startup crashes due to missing or incorrect configurations, and ensuring that the application can complete basic initialization in various terminal environments. It solves the problems of configuration omissions, format errors, or initialization failures caused by reliance on manual configuration or external injection in the prior art. Attached Figure Description

[0021] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0024] Figure 1 A flowchart illustrating a first embodiment of a method for processing the initial launch of an enterprise mobile application provided in this application; Figure 2 A flowchart illustrating the initial self-healing configuration and verification process provided for this application; Figure 3 A schematic diagram of the timing interaction between page stack listening and exit control provided in this application; Figure 4 A flowchart illustrating another embodiment of the processing method for the first launch of an enterprise mobile application provided in this application; Figure 5 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0027] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0028] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0029] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0030] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."

[0031] To address the aforementioned issues, this application provides a method for handling the initial launch of an enterprise mobile application. This method enables automatic configuration without relying on manual input from operations and maintenance personnel, preventing application startup crashes due to missing or incorrect configurations and ensuring that the application can complete basic initialization in various terminal environments. It also solves the problems of configuration omissions, format errors, or initialization failures caused by reliance on manual configuration or external injection in existing technologies.

[0032] See Figure 1 , Figure 1 This application provides a flowchart illustrating a first embodiment of a method for processing the initial launch of an enterprise mobile application. The method includes the following steps: Step 110: Obtain the initial tag when the enterprise mobile application is launched for the first time.

[0033] Step 120: Determine whether the initial mark meets the initial start conditions.

[0034] Step 130: If the initial tag meets the initial startup conditions, then the enterprise mobile application is automatically written with preset default configuration information, which includes at least the backend service address, communication port and enterprise intranet WiFi whitelist.

[0035] Step 140: Persistently store the default configuration information and clear the initial tag.

[0036] This embodiment automatically detects the first-time flag when an enterprise mobile application is launched for the first time. After confirming that it is the first launch, it automatically writes and persistently stores the preset default configuration information (including key parameters such as backend service address, communication port, and enterprise intranet WiFi whitelist). It can achieve automatic configuration without relying on manual input by operation and maintenance personnel, avoiding application startup crashes due to missing or incorrect configurations, and ensuring that the application can complete basic initialization in various terminal environments. It solves the problems of configuration omission, format errors, or initialization failure caused by manual configuration or external injection in the prior art.

[0037] Combination Figures 2-4 Referring to a second embodiment of a method for processing the first launch of an enterprise mobile application provided in this application, it may specifically include the following steps: Step 210: Obtain the initial tag when the enterprise mobile application is launched for the first time.

[0038] Step 220: Determine whether the initial mark meets the initial start conditions.

[0039] Step 230: If the initial tag meets the initial startup conditions, then the enterprise mobile application is automatically written with preset default configuration information, which includes at least the backend service address, communication port and enterprise intranet WiFi whitelist.

[0040] For steps 210-230, in some embodiments of this application, the initial marking may employ a local persistent switch (initial start flag). This flag is in an "incomplete" state by default.

[0041] Each time the enterprise mobile application is launched, this flag is read first. If the flag is "incomplete", it is determined to be the first launch and the injection operation of the default configuration is automatically executed. The default configuration includes key operating parameters such as backend host address, communication port, service interface address and enterprise intranet WiFi whitelist.

[0042] After all configuration items have been successfully written and verified to be correct, set the initial startup flag to "Completed".

[0043] If an exception occurs during the configuration writing process (such as insufficient storage space or missing permissions) and the flag fails to update, the flag will remain in an "incomplete" state. Upon the next application startup, the system will re-detect that the initial startup conditions are met and execute the complete configuration injection process again.

[0044] Through the above mechanism, this solution achieves idempotency (consistent results across multiple executions) and self-healing capability (automatic recovery after abnormal interruption), effectively ensuring that enterprise mobile applications can reliably complete the initial initialization in various deployment environments, avoiding startup failures or functional abnormalities caused by missing configurations.

[0045] Step 240: Persistently store the default configuration information and clear the initial tag.

[0046] The default configuration is persisted immediately after being written, ensuring that the configuration information is not lost even if the process terminates unexpectedly. Step 250: In the main application process, load the security component and register the global exception catcher based on the default configuration information.

[0047] In traditional solutions, crash capture and security component loading are not isolated from the master channel, making them prone to repeated initialization or conflicts.

[0048] Based on this, this application avoids conflicts and improves stability by limiting security components and crash capture to the main process channel.

[0049] In some embodiments, to ensure that exceptions in each module are collected consistently, crash capture can be uniformly registered as a global exception handling mechanism during the application startup phase.

[0050] In addition, to avoid repeated reporting by multiple processes, a strategy of "each process can capture, but only the main process is responsible for reporting / summarizing" can be adopted; at the same time, heavy capabilities such as security components are limited to the initialization of the main channel, and other processes skip them, thereby reducing repeated initialization and resource consumption.

[0051] Step 260: Register Activity lifecycle callbacks and maintain a thread-safe page stack; wherein, the page stack is used to uniformly manage the opening and closing of all Activities; the global exception catcher catches unhandled exceptions in page stack operations, realizing coordinated management of the main process's security capabilities and page lifecycle.

[0052] Step 270: In response to the exit command, close all Activities in the page stack in batches, and exit the non-main process and the main process.

[0053] Traditional management methods, lacking unified stack management, can lead to issues such as incomplete exits and page leaks. Therefore, this embodiment unifies and deeply couples the maintenance of the page stack with the exit control mechanism, enabling the cleanup of all pages at once and preventing residual Activities from running in the background. All page state changes are handled through a unified entry point, facilitating auditing and anomaly analysis. By combining process exit strategies, we can ensure that applications release system resources cleanly and completely, reducing the risk of stack disorder and leakage.

[0054] In some embodiments, step 270, exiting the non-main process and the main process, includes: Step 271: Exit the non-main process first.

[0055] Step 272: After the non-main process has finished exiting, exit the main process.

[0056] By terminating non-main processes first when the application exits, and then closing the main process only after the non-main processes have completely exited, an orderly end to the application lifecycle in a multi-process environment is achieved.

[0057] If the main process exits before non-main processes, child processes may fail to complete cleanup properly due to the loss of their parent process or interruption of communication channels, thus becoming "orphan processes" in the system or lingering in the background, consuming memory and power. Therefore, this embodiment ensures that all child processes release resources before the main process is destroyed by forcing sequential exits, completely eliminating residual processes. This reduces system lag, abnormal battery consumption, or subsequent startup conflicts caused by abnormal process remnants, especially in enterprise device batch management scenarios, improving the stability and maintainability of terminal operation.

[0058] For steps 271-272, by terminating the non-main process first and then the main process during exit, it can be ensured that no resident processes remain.

[0059] In some embodiments, after persistently storing the default configuration information, the method further includes: 1) Create an external log directory.

[0060] 2) Configure the log rolling strategy based on the default configuration information.

[0061] In some embodiments, the log rolling strategy adopts a combination of "pre-defined directory + periodic file splitting + capacity / quantity / time constraint cleanup".

[0062] In some embodiments, after creating the external log directory, the method further includes: 1) When a single file in the log directory exceeds the threshold or the retention window, cleanup or overwriting is performed; at the same time, historical logs that have exceeded the retention period are deleted to ensure that space is controllable and easy to audit and trace.

[0063] 2) During the log writing process, when the size of a single log file reaches a preset size threshold, writing to the file stops and a new log file is generated; wherein, the log files are generated according to a preset time period, and each log file corresponds to a recording time.

[0064] 3) In response to log file generation or application startup, scan all log files in the log directory and delete the target historical log files.

[0065] Wherein, the recording time of the target historical log file exceeds the preset retention period, or the number of files in the target historical log file exceeds the preset retention number.

[0066] In other words, when the application starts, in order to ensure that the log directory exists, logs can generate new files at fixed preset time periods (e.g., daily); when a single file exceeds the threshold or the retention window, it is cleaned up or overwritten; at the same time, target historical log files that exceed the retention period are deleted to ensure that space is controllable and easy to audit and trace.

[0067] In some embodiments, after loading the security component and registering the global exception catcher based on the default configuration information in the application main process, the method further includes: 1) In the main process, synchronize the current application version number to the application version and start the location monitoring service for the application.

[0068] 2) Obtain the current application version number; 3) Write the version number of the current application to the local database; 4) Start the location monitoring service for the application; 5) Collect location information using the location monitoring service; 6) The location information is encrypted using the security component.

[0069] In this way, a complete operation and location audit chain is provided through logs and location data, while the synchronization mechanism between database version and application version significantly alleviates upgrade compatibility issues caused by version inconsistency.

[0070] Based on the above embodiments, combined with Figures 2-4 This application provides a "stable state upon first startup" management framework, wherein the system architecture of this application consists of an application entry point, a configuration assistant, a logging module, a crash catcher, a security component, a database version management module, a location module, and a page stack management module.

[0071] Specifically, the method for processing the initial launch of an enterprise mobile application provided in this application may include the following process: 1) First activation of self-healing Upon startup, the initial flag is detected. If it is determined to be the first startup, the default configuration information, such as host, port, service address and WiFi whitelist, is automatically written and stored in the database. After the configuration is successfully stored in the database, the initial flag is cleared, thereby ensuring that the entire initialization process is idempotent.

[0072] Once the initial configuration is stored locally, it can be verified for consistency with the server-side configuration, providing a basis for subsequent configuration rollback, dynamic correction, or incremental updates.

[0073] 2) Log and storage provisioning When the application starts, an external log directory is automatically created, and the log rolling strategy is initialized according to the default configuration information, including the maximum size of a single log file and the number of files to be retained, to ensure that the log content can be used for debugging and also meets the audit traceability requirements.

[0074] In some embodiments, the log directory can dynamically select a storage location based on device permissions: external storage is used first to facilitate debugging; if the corresponding permissions are not available, it falls back to the application's private directory, thus balancing compatibility and user privacy protection.

[0075] In some embodiments, a log rolling strategy can also be configured based on default configuration information.

[0076] For example, logs are managed by rolling over based on file size, and a fixed number of historical files are retained. This avoids unlimited storage growth while making it easier for operations and maintenance personnel to quickly locate and retrieve key log information.

[0077] 3) Crash capture and security component loading In some embodiments, the global exception catcher is configured to simultaneously perform encrypted upload of exception data and local user prompts after capturing an unhandled exception, thereby constructing a fault self-healing closed loop with self-feedback capabilities.

[0078] 4) Version and Positioning Synchronize and align the current database version with the application version; enable location monitoring to provide location information for security and compliance.

[0079] 5) Page Stack Guardian The page stack is maintained using a thread-safe data structure and automatically manages page push and pop operations by registering Activity lifecycle callbacks. It also exposes a unified interface to support capabilities such as batch closing by page type, querying the current top page of the stack, retrieving a list of active pages, and performing a full exit.

[0080] In some implementations, the page stack is configured to record the timestamps of an Activity entering / exiting the foreground, and based on this, generate foreground / background switching logs and page dwell time metrics.

[0081] 6) Process determination and result caching It distinguishes between main and remote processes, allowing non-main processes to skip heavy initialization; it returns results in a globally cached page, supporting cross-page data transfer and avoiding the problem of easily losing results in traditional solutions.

[0082] In some embodiments, the type of process can be determined by comparing the current process name with the application package name.

[0083] For example, if the current process name matches the application package name, it is the main process; otherwise, it is a remote / other process.

[0084] The process type determination result can be cached and used for branch control in the subsequent startup process. For example, non-main processes can skip high-overhead initializations such as push notifications, antivirus, and database migration, and only retain lightweight logic to avoid resource redundancy and repeated loading.

[0085] In some embodiments, the results can be cached in the global scope, independent of the lifecycle of a single page.

[0086] 7) Secure exit mechanism.

[0087] When exiting, first terminate the non-main processes, then terminate the main process and complete the process cleanup.

[0088] Upon initial startup, the system automatically writes core configuration and performs a self-check; loads security components and crash capture only on the main channel; synchronizes database and application versions; enables geolocation for compliance auditing; and maintains the page stack, result cache, and secure exit through lifecycle callbacks. This addresses issues such as missing initial configuration, conflicts between crash protection and security components, and a chaotic page stack, providing a self-healing solution for initial startup, main channel-limited security component loading, and lifecycle protection to ensure stable startup and secure exit. For enterprise initial deployment: after a cold start, the system automatically writes the default host, port, and WiFi whitelist and saves it to the database, clearing the initial setup flag; registers crash capture and loads security components only on the main channel, synchronizing database version and location monitoring; lifecycle callbacks maintain the page stack and result cache; and when a user exits, the remote process terminates first, then the main process, ensuring no remnants remain.

[0089] Thus, upon initial launch, the application automatically writes the default core configuration (i.e., default configuration information), including the backend host, port, and enterprise WiFi whitelist, and persists this default configuration information. The initial launch flag is then cleared, resolving the issue of missing initial configuration causing initial launch failure. Furthermore, security components are loaded and a global crash catcher is registered only in the main process to avoid multi-process conflicts. The application version and database version are synchronized to ensure upgrade compatibility, and geolocation is enabled for compliance auditing. Page stacks and page result caches are maintained uniformly through Activity lifecycle callbacks to ensure reliable data transfer across pages. When the user exits, non-main processes are terminated first, followed by the main process, to completely release resources and prevent process remnants.

[0090] This solution comprehensively addresses issues such as configuration deficiencies, security capability conflicts, chaotic page management, and incomplete exits faced by enterprise mobile applications in cold start scenarios, achieving an integrated mechanism of self-healing upon initial startup, main channel security control, and full lifecycle protection.

[0091] Corresponding to the above-described method for processing the first launch of an enterprise mobile application, this application also provides a processing apparatus for the first launch of an enterprise mobile application. This processing apparatus includes a unit for executing the above-described method for processing the first launch of an enterprise mobile application, and can be configured in a terminal such as a desktop computer, tablet computer, or laptop computer.

[0092] like Figure 5 As shown in the figure, this application provides a computer device including a processor 111, a communication interface 112, a memory 113, and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114. Memory 113 is used to store computer programs; In one embodiment of this application, when the processor 111 executes the program stored in the memory 113, it implements the processing method for the first launch of an enterprise mobile application provided in any of the foregoing method embodiments, including: Obtain the initial tag when the enterprise mobile application is launched for the first time; Determine whether the initial marker meets the initial startup conditions; If the initial tag meets the initial launch conditions, then preset default configuration information is automatically written into the enterprise mobile application. The default configuration information includes at least the backend service address, communication port, and enterprise intranet WiFi whitelist. The default configuration information is persistently stored, and the initial tag is cleared.

[0093] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program may be stored in a storage medium, which is a computer-readable storage medium. The computer program is executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0094] Therefore, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, wherein when the computer program is executed by a processor, it implements the steps of the processing method for the first launch of an enterprise mobile application as provided in any of the foregoing method embodiments, including: Obtain the initial tag when the enterprise mobile application is launched for the first time; Determine whether the initial marker meets the initial startup conditions; If the initial tag meets the initial launch conditions, then preset default configuration information is automatically written into the enterprise mobile application. The default configuration information includes at least the backend service address, communication port, and enterprise intranet WiFi whitelist. The default configuration information is persistently stored, and the initial tag is cleared.

[0095] The storage medium is a physical, non-transient storage medium, such as a USB flash drive, external hard drive, read-only memory (ROM), magnetic disk, or optical disk, or any other physical storage medium capable of storing program code. The computer-readable storage medium can be non-volatile or volatile.

[0096] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0097] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0098] The steps in the methods of this application embodiment can be adjusted, merged, or deleted according to actual needs. The units in the apparatus of this application embodiment can be merged, divided, or deleted according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0099] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0100] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0101] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Since these modifications and variations fall within the scope of the claims and their equivalents, this application also intends to include these modifications and variations.

[0102] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for processing the first launch of an enterprise mobile application, characterized in that, The method includes: Obtain the initial tag when the enterprise mobile application is launched for the first time; Determine whether the initial marker meets the initial startup conditions; If the initial tag meets the initial launch conditions, then preset default configuration information is automatically written into the enterprise mobile application. The default configuration information includes at least the backend service address, communication port, and enterprise intranet WiFi whitelist. The default configuration information is persistently stored, and the initial tag is cleared.

2. The method according to claim 1, characterized in that, After persistently storing the default configuration information, the method further includes: In the main application process, a security component is loaded and a global exception catcher is registered based on the default configuration information; Register Activity lifecycle callbacks and maintain a thread-safe page stack; wherein, the page stack is used to uniformly manage the opening and closing of all Activities; the global exception catcher catches unhandled exceptions in page stack operations, realizing coordinated management of the main process's security capabilities and page lifecycle. In response to the exit command, all Activities in the page stack are closed in batches, and the non-main process and the main process are exited.

3. The method according to claim 2, characterized in that, The exiting of non-main processes and main processes includes: Exit the non-main process first; The main process exits only after the non-main process has finished exiting.

4. The method according to claim 1, characterized in that, After persistently storing the default configuration information, the method further includes: Create an external log directory; Configure a log rolling strategy based on the default configuration information.

5. The method according to claim 4, characterized in that, The log rolling strategy adopts a combination of "pre-defined directory + periodic file splitting + capacity / quantity / time constraint cleanup".

6. The method according to claim 4, characterized in that, After creating the external log directory, the method further includes: When a single file in the log directory exceeds the threshold or the retention window, cleanup or overwriting is performed; at the same time, historical logs that have exceeded the retention period are deleted to ensure that space is controllable and easy to audit and trace. During the log writing process, when the size of a single log file reaches a preset size threshold, writing to the file stops and a new log file is generated; wherein, the log files are generated according to a preset time period, and each log file corresponds to a recording time; In response to log file generation or application startup, scan all log files in the log directory and delete the target historical log file; Wherein, the recording time of the target historical log file exceeds the preset retention period, or the number of files in the target historical log file exceeds the preset retention number.

7. The method according to claim 4, characterized in that, After loading the security component and registering the global exception catcher based on the default configuration information in the application's main process, the method further includes: In the main process, the current application version number is synchronized to the application version, and a location monitoring service for the application is started. Get the current application version number; Write the version number of the current application to the local database; Start the location monitoring service for the application; Location information is collected using the location monitoring service. The location information is encrypted using the security component.

8. A processing device for the initial launch of an enterprise mobile application, characterized in that, Includes a unit for performing the method as described in any one of claims 1-7.

9. A computer device, characterized in that, The computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, can implement the method as described in any one of claims 1-7.

Images