WO2019019668A1 - 应用程序启动方法、装置、计算机设备和存储介质 - Google Patents
应用程序启动方法、装置、计算机设备和存储介质 Download PDFInfo
- Publication number
- WO2019019668A1 WO2019019668A1 PCT/CN2018/079885 CN2018079885W WO2019019668A1 WO 2019019668 A1 WO2019019668 A1 WO 2019019668A1 CN 2018079885 W CN2018079885 W CN 2018079885W WO 2019019668 A1 WO2019019668 A1 WO 2019019668A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- page
- application
- startup
- server
- jump
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
Definitions
- the present application relates to the field of computer technologies, and in particular, to an application startup method, apparatus, computer device, and storage medium.
- an application launch method, apparatus, computer device, and storage medium are provided.
- An application startup method including:
- the recording application fails to be started
- the repair page includes a repair control
- An application launching device comprising:
- a detection module configured to acquire an activation identifier and a startup page of the application; track the startup process of the application, and obtain the number of times the startup identifier appears within a preset time or the stay time of the startup page; If the number of occurrences of the startup identifier within the preset time reaches the threshold or the stay time of the startup page exceeds the preset time, the recording application fails to be started;
- a repairing module configured to jump from a startup page to a repairing page, where the repairing page includes a repairing control; acquiring a triggering event corresponding to the repairing control, and repairing the application in response to the triggering event;
- a startup module that is used to launch with the repaired application.
- a computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executable by the processor to cause the one or more processors to execute The following steps:
- the recording application fails to be started
- the repair page includes a repair control
- One or more computer readable non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of:
- the recording application fails to be started
- the repair page includes a repair control
- FIG. 1 is an application scenario diagram of an application launch method in accordance with one or more embodiments
- FIG. 2 is a flow diagram of an application launch method in accordance with one or more embodiments
- FIG. 3 is a schematic structural diagram of a mobile terminal according to one or more embodiments.
- FIG. 4 is a block diagram of an application launch device in accordance with one or more embodiments.
- the application startup method provided in the embodiment of the present application can be applied to the application scenario as shown in FIG. 1 .
- the mobile terminal 102 is connected to the server 104 via a network.
- the application is pre-installed on the mobile terminal 102.
- the mobile terminal 102 acquires the startup identification and launch page of the application.
- the mobile terminal 102 tracks the startup process of the application.
- the mobile terminal 102 detects the corresponding activation identification. If the number of occurrences of the startup identifier within the preset time reaches the threshold or the stay time on the startup page exceeds the preset time, the mobile terminal 102 records that the application startup failed.
- the application fails to launch, the mobile terminal 102 can jump from the launch page to the repair page.
- the user can click on the repair control in the repair page to generate a trigger event corresponding to the repair control.
- the mobile terminal 102 repairs the application in response to the triggering event. There are several ways to fix it, such as clearing the application's data and downloading patches for the application.
- the mobile terminal 102 repairs the application by downloading the patch
- the mobile terminal 102 generates a patch acquisition request and transmits the patch acquisition request to the server 104.
- the server 104 obtains a corresponding patch according to the patch request, and returns the patch to the mobile terminal 102.
- the mobile terminal 102 repairs the application using the patch.
- the repair is complete and the application is restarted. This can effectively increase the probability of successful application startup.
- an application startup method is provided, which is applied to the mobile terminal as an example, and specifically includes the following steps:
- Step 202 Acquire an activation identifier and a startup page of the application.
- Step 204 Tracking the startup process of the application, and obtaining the number of times the startup identifier appears within the preset time or the staying time on the startup page.
- Step 206 If the number of occurrences of the startup identifier within the preset time reaches the threshold or the stay time of the startup page exceeds the preset time, the recording application fails to start.
- the application is pre-installed on the mobile terminal.
- the mobile terminal acquires the startup identification and startup page of the application.
- the startup ID can be the identifier that the developer sets for the application at startup.
- the launch page can be the page that the developer sets for the application to launch.
- the mobile terminal tracks the startup process of the application.
- the mobile terminal detects the corresponding startup identifier. If the startup identifier is detected multiple times within the preset time, that is, the startup identifier appears multiple times within the preset time, the number of occurrences of the startup identifier within the preset time is compared with the threshold. If the threshold is reached, it indicates that the application fails to start, and the mobile terminal performs corresponding recording.
- the mobile terminal can also detect the dwell time of the startup page when the application is started. If the dwell time of the startup page exceeds the budget time, it indicates that the application fails to be started, and the mobile terminal performs corresponding recording.
- Step 208 jump from the startup page to the repair page, and the repair page includes a repair control.
- Step 210 Acquire a trigger event corresponding to the repair control, and repair the application in response to the trigger event.
- Step 212 using the repaired application to start.
- the mobile terminal can jump from the startup page to the repair page.
- the repair control is included in the repair page.
- the user can click on the repair control to generate a trigger event corresponding to the repair control.
- the mobile terminal repairs the application in response to the triggering event.
- the repair method can include various types, such as clearing the application's data and downloading the application's patch.
- the data that affects the application startup may be cleared, and the cleared data includes the locally cached pictures and videos, the data used for user behavior analysis, and the uploaded server for backup. Data, etc. After clearing the application's data, restart the application. This can effectively increase the probability of successful application startup.
- the mobile terminal may also generate a patch acquisition request in response to the trigger event corresponding to the repair control, and send the patch acquisition request to the server.
- the server obtains the corresponding patch according to the patch request, and returns the patch to the mobile terminal.
- the mobile terminal uses the patch to fix the application.
- the repair is complete and the application is restarted. This can effectively increase the probability of successful application startup.
- the mobile terminal can also send a patch acquisition request to the server after the data of the application is cleared, download the patch from the server, and further repair the application. This can further increase the probability of successful application startup.
- the number of times the startup identifier appears within the preset time or the staying time of the startup page may be obtained, and if the number of occurrences of the startup identifier within the preset time reaches a threshold or If the dwell time of the startup page exceeds the preset time, it means that the application failed to start.
- the application fails to start jump from the startup page to the repair page.
- the application is fixed by responding to the trigger event corresponding to the repair control in the repair page. The chances of successful startup are improved when starting with a repaired application. In this process, there is no need to uninstall and reload the application, and the recovery can be effectively improved by the repair.
- steps in the flowchart of FIG. 2 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIG. 2 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, the execution of these sub-steps or stages The order is also not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.
- the step of repairing the application in response to the triggering event comprises: acquiring data of the application in response to the triggering event, the data of the application includes account data; retaining the account data, and clearing other data of the application.
- the mobile terminal when the application fails to start, the mobile terminal can clear the data of the application.
- the mobile terminal can only retain the account data therein, and the account data includes the account and password when the user logs in. Therefore, after the application is successfully started, the user can directly use the retained account data to log in, which provides convenience for the user.
- the account data may also include the user's bank account and the like. The mobile terminal can clear other data in the application's data than the account data. By eliminating the impact of application restarts by clearing the application's data, you can effectively increase the chances of successful application startup.
- the step of repairing the application in response to the triggering event comprises: obtaining version information of the application in response to the triggering event, generating a patch obtaining request by using the version information; and sending the patch obtaining request to the server, so that the server is based on the version The information obtains the corresponding patch, returns the patch, receives the patch, and uses the patch to repair the application.
- the mobile terminal may also download the patch from the server to repair the application. Specifically, when the repair control in the repair page is triggered, the mobile terminal acquires a corresponding trigger event, and obtains version information of the application in response to the trigger event.
- the versions of the applications installed on different mobile terminals can be different.
- the mobile terminal generates a patch acquisition request according to the version information, and sends the patch acquisition request to the server.
- the server receives the patch acquisition request, and obtains a corresponding patch according to the version information of the application carried in the patch acquisition request. Patches for different versions of the application can be different.
- the server returns the obtained patch to the mobile terminal.
- the mobile terminal installs a patch to fix the application. By installing patches, you can effectively fix your application, which can effectively increase the chances of successful application startup.
- the method further includes: sending a page acquisition request to the server, so that the server obtains the corresponding page according to the page acquisition request, and if the page is greater than the threshold, adding the page Cache tag; the page that is added by the server to which the cache tag is added, intercepts the loading process of the page according to the cache tag, caches the intercepted page, loads the cached page, and displays the page.
- the mobile terminal can use the application to send a page acquisition request to the server to display the corresponding page to the user.
- the server receives the page acquisition request, and obtains a corresponding page according to the request. After the server obtains the corresponding page, it can identify whether it needs to add a cache tag. Specifically, if the page includes pictures, audio or video, it may cause the page to be large. If the page is larger than the threshold, you need to add a cache tag.
- the server returns the page with the cache tag back to the mobile terminal.
- the mobile terminal receives the page that adds the cache tag, intercepts the process of loading the page by the application, and caches the intercepted page. After the cache is successful, the mobile terminal loads the cached page through the application, thereby displaying the page.
- the mobile terminal can directly load the page in the cache through the application without sending the page acquisition request to the server again. This not only can effectively improve the page loading speed, but also can effectively save network traffic.
- the method further includes: acquiring a trigger event corresponding to the page jump, generating a page jump request in response to the trigger event; and sending the page jump request to the server, to The server obtains a corresponding page file according to the page jump request, the page file includes a page attribute, and the target page of the jump is obtained according to the page attribute; and the target page after the jump returned by the server is received, and the target page after the jump is displayed.
- the mobile terminal can display the page through the application.
- the page displayed by the mobile terminal may include a page jump link or a page jump control.
- the mobile terminal can obtain a trigger event corresponding to the page jump.
- the mobile terminal generates a page jump request in response to the trigger event, and sends a page jump request to the server.
- the server obtains the page file corresponding to the currently displayed page.
- the page file includes page content and page properties.
- the page attributes include page categories and category identifiers.
- the page type can represent the type of business presented in the page, such as insurance or financial management.
- the category identifier can be the page marker of the target page after the jump. According to the page category and the category identifier, the jump location and the service category of the target page after the jump can be known.
- the server starts the routing interface according to the page jump request, invokes the parameter corresponding to the routing interface according to the page attribute, and obtains the target page after the jump by passing the parameter.
- H5 HyperText Markup Language 5, Hypertext Markup Language Fifth Edition
- Native pages an application's page
- React Native pages an application Page
- H5 HyperText Markup Language 5, Hypertext Markup Language Fifth Edition
- the server needs to start a different routing interface to obtain the corresponding page content. In other words, the routing of each page is different.
- the server needs to configure different routes for different pages, which causes inconvenience to page jumps.
- a plurality of pages can be configured with a unified route, that is, a page jumps from one page to a page of the same type or jumps to a different type of page, and the server can invoke the same routing interface.
- the page jump can be from the H5 page to the H5 page, or from the H5 page to the Native page, or from the H5 page to the React Native page, or from the Native page to React Native page, etc.
- the server can call the same routing interface, and call the parameters corresponding to the routing interface according to the page attribute, so as to obtain the target page after the jump by passing parameters.
- the routing interface of the page jump has strong scalability and flexibility, and is convenient for effectively jumping between different pages.
- the method further includes: receiving an application version update notification pushed by the server; generating an update request according to the update notification, and sending the update request to the server, so that the server is configured according to the server
- the update request obtains the difference data between the latest version application and the current version application, generates the incremental package by using the difference data, receives the incremental package returned by the server, and incrementally updates the application by using the incremental package.
- the mobile terminal can receive an application version update notification pushed by the server.
- the mobile terminal acquires a trigger corresponding to the update control according to the version update notification, and generates an update request in response to the trigger event.
- the mobile terminal sends an update request to the server.
- the server can obtain version information of multiple versions of the application, compare multiple versions of the application with the latest version of the application, generate corresponding difference data, and use the difference data to generate incremental packages corresponding to multiple versions.
- the server When the server receives the update request, the corresponding incremental package is obtained according to the version information of the current version of the application of the mobile terminal carried in the update request.
- the server returns the delta packet to the mobile terminal.
- the mobile terminal receives the incremental package, merges the incremental package with the installation package corresponding to the application of the current current version, and generates the latest version of the installation package. Update the application with the latest version of the installation package.
- the mobile terminal When the application is updated, the mobile terminal only needs to download the incremental package corresponding to the current version information to implement the application update, and does not need to download the entire installation package, thereby not only saving network traffic, but also effectively improving the update. effectiveness.
- a mobile terminal including a processor, memory, network interface, display screen, and input device connected by a system bus.
- the processor of the mobile terminal is used to provide computing and control capabilities.
- the memory of the mobile terminal includes a non-volatile storage medium and an internal memory.
- the non-volatile storage medium can be a computer-readable non-volatile storage medium.
- the non-volatile storage medium of the mobile terminal stores an operating system and computer readable instructions that are executed by the processor to implement an application launch method.
- the internal memory of the mobile terminal provides an environment for operation of an operating system and computer readable instructions in a non-volatile storage medium.
- the network interface of the mobile terminal is used for communicating with an external server through a network connection, for example, sending a patch acquisition request to the server, and receiving a patch returned by the server.
- the display screen of the mobile terminal may be a liquid crystal display or an electronic ink display screen, and the input device may be a touch layer covered on the display screen, or may be a button or a touch pad disposed on the terminal housing.
- the mobile terminal can be a mobile phone, a tablet, a personal digital assistant, or a wearable device.
- FIG. 3 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied.
- the specific server may include a ratio. More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.
- the application further provides an application starting device, and the internal structure of the application starting device may correspond to the structure shown in FIG. 3.
- Each of the following modules may pass all or part of software and hardware. Or a combination of them to achieve.
- Each module may be embedded in or independent of the processor in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules.
- the application launching device includes a detection module 402, a repair module 404, and a launch module 406, wherein:
- the detecting module 402 is configured to acquire a startup identifier and a startup page of the application; track the startup process of the application, and obtain the number of times the startup identifier appears in the preset time or the staying time on the startup page; if the startup identifier is in the preset If the number of occurrences in the time reaches the threshold or the dwell time on the startup page exceeds the preset time, the recording application fails to start.
- the repair module 404 is configured to jump from the startup page to the repair page, the repair page includes a repair control, obtain a trigger event corresponding to the repair control, and repair the application in response to the trigger event.
- the startup module 406 is configured to boot with the repaired application.
- the repair module 404 is further configured to acquire data of the application in response to the trigger event, the data of the application includes account data; the account data is retained, and other data of the application is cleared.
- the repair module 404 is further configured to: obtain the version information of the application in response to the trigger event, generate a patch acquisition request by using the version information, and send the patch acquisition request to the server, so that the server obtains the corresponding patch according to the version information, and returns Patch; receive patches and use patches to fix applications.
- the device further includes: a cache module 408, configured to send a page acquisition request to the server, so that the server acquires a corresponding page according to the page acquisition request, and if the page is greater than the threshold, add a cache label to the page;
- the returned page with the cached tag is intercepted according to the cache tag, and the intercepted page is cached; the cached page is loaded to display the page.
- the device further includes: a jump module 410, configured to acquire a trigger event corresponding to the page jump, generate a page jump request in response to the trigger event, and send the page jump request to the server, so that the server according to the page
- the jump request obtains the corresponding page file, the page file includes the page attribute, and the target page of the jump is obtained according to the page attribute; the target page after the jump returned by the server is received, and the target page after the jump is displayed.
- the apparatus further includes: an update module 412, configured to receive an application version update notification pushed by the server; generate an update request according to the update notification, and send the update request to the server, so that the server acquires the new version according to the update request.
- the difference data between the application and the current version of the application using the difference data to generate incremental packages; receiving the incremental package returned by the server, incrementally updating the application with the incremental package.
- a computer apparatus comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by a processor, cause one or more processors to execute The following steps: obtaining the startup identifier and the startup page of the application; tracking the startup process of the application, obtaining the number of times the startup identifier appears within the preset time or the staying time on the startup page; if the startup identifier appears within the preset time If the number of times reaches the threshold or the waiting time of the startup page exceeds the preset time, the recording application fails to start; from the startup page to the repair page, the repair page includes the repair control; the trigger event corresponding to the repair control is acquired, and the trigger event event is responded to. The application is repaired; and the application is launched using the repaired application.
- the computer readable instructions are executed by the processor such that the one or more processors further perform the steps of: acquiring data of the application in response to the triggering event, the data of the application including account data; and retaining account data, Clear other data from the application.
- the computer readable instructions are executed by the processor such that the one or more processors further perform the steps of: obtaining version information of the application in response to the triggering event, generating a patch acquisition request using the version information; and obtaining the patch request Send to the server, so that the server obtains the corresponding patch according to the version information, returns the patch, and receives the patch, and uses the patch to repair the application.
- the computer readable instructions are executed by the processor such that the one or more processors further perform the step of: transmitting a page fetch request to the server such that The server obtains the corresponding page according to the page obtaining request. If the page is larger than the threshold, the server adds a cache label to the page; the page that is added by the server and adds the cache label, intercepts the loading process of the page according to the cache label, and performs the intercepted page. Cache; and load the cached page for page display.
- the computer readable instructions are executed by the processor such that the one or more processors further perform the step of: acquiring a trigger event corresponding to the page jump, Generating a page jump request in response to the trigger event; sending a page jump request to the server, so that the server obtains a corresponding page file according to the page jump request, the page file includes a page attribute, and the target page of the jump is obtained according to the page attribute; and receiving The target page after the jump returned by the server will display the target page after the jump.
- the computer readable instructions are executed by the processor such that the one or more processors further perform the step of: receiving an application version update notification pushed by the server Generating an update request according to the update notification, sending the update request to the server, so that the server acquires the difference data between the new version application and the current version application according to the update request, generates the incremental package by using the difference data; and receives the returned by the server Incremental package that incrementally updates an application with incremental packages.
- one or more computer readable non-volatile storage media having computer readable instructions, when executed by one or more processors, causing one or more processors Perform the following steps: Obtain the startup ID and startup page of the application; track the startup process of the application, obtain the number of times the startup identifier appears within the preset time or the duration of the startup page; if the startup identifier is within the preset time If the number of occurrences reaches the threshold or the waiting time of the startup page exceeds the preset time, the recording application fails to be started; from the startup page to the repair page, the repair page includes the repair control; the trigger event corresponding to the repair control is acquired, and the trigger event is responded to. Repair the application; and launch it with the repaired application.
- the computer readable instructions are executed by one or more processors such that the one or more processors further perform the steps of: acquiring data of the application in response to the triggering event, the data of the application including account data; Keep account data and clear other data from the application.
- the computer readable instructions are executed by one or more processors such that the one or more processors further perform the steps of: obtaining version information of the application in response to the triggering event, and generating a patch acquisition request using the version information; Send the patch acquisition request to the server, so that the server obtains the corresponding patch according to the version information, returns the patch, and receives the patch, and uses the patch to repair the application.
- the computer readable instructions are executed by one or more processors such that the one or more processors further perform the step of: sending a page capture to the server The request is such that the server obtains the corresponding page according to the page obtaining request, and if the page is larger than the threshold, the cache label is added to the page; the page that is added by the receiving server and added the cache label intercepts the loading process of the page according to the cache label, and intercepts After the page is cached; and the cached page is loaded for page display.
- the computer readable instructions are executed by one or more processors such that the one or more processors further perform the step of: obtaining a page jump corresponding
- the trigger event generates a page jump request in response to the trigger event; the page jump request is sent to the server, so that the server obtains the corresponding page file according to the page jump request, the page file includes the page attribute, and the target of the jump is obtained according to the page attribute.
- the page; and the target page after the jump returned by the receiving server, the target page after the jump is displayed.
- the computer readable instructions are executed by one or more processors such that the one or more processors further perform the steps of: receiving the server pushed application a program version update notification; generating an update request according to the update notification, sending the update request to the server, so that the server obtains the difference data between the new version application and the current version application according to the update request, and generates the incremental package by using the difference data; Receive incremental packages returned by the server, incrementally update the application with incremental packages.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
Claims (20)
- 一种应用程序启动方法,包括:获取应用程序的启动标识和启动页面;对应用程序的启动过程进行跟踪,获取所述启动标识在预设时间内出现的次数或者在所述启动页面的停留时间;若所述启动标识在预设时间内出现的次数达到阈值或者在所述启动页面的停留时间超过预设时间,则记录应用程序启动失败;从启动页面跳转至修复页面,所述修复页面包括修复控件;获取所述修复控件对应的触发事件,响应所述触发事件对应用程序进行修复;及利用修复后的应用程序进行启动。
- 根据权利要求1所述的方法,其特征在于,所述响应所述触发事件对应用程序进行修复的步骤,包括:响应所述触发事件获取应用程序的数据,所述应用程序的数据包括账户数据;及保留所述账户数据,将应用程序的其他数据进行清除。
- 根据权利要求1所述的方法,其特征在于,所述响应所述触发事件对应用程序进行修复的步骤,包括:响应所述触发事件获取应用程序的版本信息,利用所述版本信息生成补丁获取请求;将所述补丁获取请求发送至服务器,以使得服务器根据所述版本信息获取对应的补丁,返回所述补丁;及接收所述补丁,利用所述补丁对应用程序进行修复。
- 根据权利要求1所述的方法,其特征在于,在所述利用修复后的应用程序进行启动的步骤之后,还包括:向服务器发送页面获取请求,以使得服务器根据所述页面获取请求获取对应的页面,若所述页面大于阈值,则对所述页面添加缓存标签;接收服务器返回的添加了缓存标签的页面,根据缓存标签对所述页面的加载过程进行拦截,将拦截后的页面进行缓存;及加载缓存后的页面,进行页面展示。
- 根据权利要求1所述的方法,其特征在于,在所述利用修复后的应用程序进行启动的步骤之后,还包括:获取页面跳转对应的触发事件,响应所述触发事件生成页面跳转请求;将所述页面跳转请求发送至服务器,以使得服务器根据所述页面跳转请求获取对应的页面文件,所述页面文件包括页面属性,根据所述页面属性获取跳转的目标页面;及接收服务器返回的跳转后的目标页面,将跳转后的目标页面进行展示。
- 根据权利要求1-5任一项所述的方法,其特征在于,在所述利用修复后的应用程序进行启动的步骤之后,还包括:接收服务器推送的应用程序版本更新通知;根据所述更新通知生成更新请求,将所述更新请求发送至服务器,以使得服务器根据所述更新请求获取新版本应用程序与当前版本应用程序之间的差异数据,利用差异数据生成增量包;及接收服务器返回的增量包,利用所述增量包对应用程序进行增量更新。
- 一种应用程序启动装置,包括:检测模块,用于获取应用程序的启动标识和启动页面;对应用程序的启动过程进行跟踪,获取所述启动标识在预设时间内出现的次数或者在所述启动页面的停留时间;若所述启动标识在预设时间内出现的次数达到阈值或者在所述启动页面的停留时间超过预设时间,则记录应用程序启动失败;修复模块,用于从启动页面跳转至修复页面,所述修复页面包括修复控件;获取所述修复控件对应的触发事件,响应所述触发事件对应用程序进行修复;及启动模块,用于利用修复后的应用程序进行启动。
- 根据权利要求7所述的装置,其特征在于,所述装置还包括:跳转模块,用于获取页面跳转对应的触发事件,响应所述触发事件生成页面跳转请求;将所述页面跳转请求发送至服务器,以使得服务器根据所述页面跳转请求获取对应的页面文件,所述页面文件包括页面属性,根据所述页面属性获取跳转的目标页面;及接收服务器返回的跳转后的目标页面,将跳转后的目标页面进行展示。
- 根据权利要求7所述的装置,其特征在于,所述修复模块还用于响应所述触发事件获取应用程序的数据,所述应用程序的数据包括账户数据;及保留所述账户数据,将应用程序的其他数据进行清除。
- 根据权利要求7-9任一项所述的装置,其特征在于,所述装置还包括:缓存模块,用于向服务器发送页面获取请求,以使得服务器根据所述页面获取请求获取对应的页面,若所述页面大于阈值,则对所述页面添加缓存标签;接收服务器返回的添加了缓存标签的页面,根据缓存标签对所述页面的加载过程进行拦截,将拦截后的页面进行缓存;及加载缓存后的页面,进行页面展示。
- 一种计算机设备,包括存储器和一个或多个处理器,所述存储器中储存有计算机可读指令,所述计算机可读指令被所述处理器执行时,使得所述一个或多个处理器执行以下步骤:获取应用程序的启动标识和启动页面;对应用程序的启动过程进行跟踪,获取所述启动标识在预设时间内出现的次数或者在所述启动页面的停留时间;若所述启动标识在预设时间内出现的次数达到阈值或者在所述启动页面的停留时间超过预设时间,则记录应用程序启动失败;从启动页面跳转至修复页面,所述修复页面包括修复控件;获取所述修复控件对应的触发事件,响应所述触发事件对应用程序进行修复;及利用修复后的应用程序进行启动。
- 根据权利要求11所述的计算机设备,其特征在于,所述计算机可读指令被所述处理器执行时,使得所述一个或多个处理器还执行以下步骤:响应所述触发事件获取应用程序的数据,所述应用程序的数据包括账户数据;及保留所述账户数据,将应用程序的其他数据进行清除。
- 根据权利要求11所述的计算机设备,其特征在于,所述计算机可读指令被所述处理器执行时,使得所述一个或多个处理器还执行以下步骤:响应所述触发事件获取应用程序的版本信息,利用所述版本信息生成补丁获取请求;将所述补丁获取请求发送至服务器,以使得服务器根据所述版本信息获取对应的补丁,返回所述补丁;及接收所述补丁,利用所述补丁对应用程序进行修复。
- 根据权利要求11所述计算机设备,其特征在于,在所述利用修复后的应用程序进行启动的步骤之后,所述计算机可读指令被所述处理器执行时,使得所述一个或多个处理器还执行以下步骤:向服务器发送页面获取请求,以使得服务器根据所述页面获取请求获取对应的页面,若所述页面大于阈值,则对所述页面添加缓存标签;接收服务器返回的添加了缓存标签的页面,根据缓存标签对所述页面的加载过程进行拦截,将拦截后的页面进行缓存;及加载缓存后的页面,进行页面展示。
- 根据权利要求11所述计算机设备,其特征在于,在所述利用修复后的应用程序进行启动的步骤之后,所述计算机可读指令被所述处理器执行时,使得所述一个或多个处理器还执行以下步骤:获取页面跳转对应的触发事件,响应所述触发事件生成页面跳转请求;将所述页面跳转请求发送至服务器,以使得服务器根据所述页面跳转请求获取对应的页面文件,所述页面文件包括页面属性,根据所述页面属性获取跳转的目标页面;及接收服务器返回的跳转后的目标页面,将跳转后的目标页面进行展示。
- 根据权利要求11-15任一项所述的计算机设备,其特征在于,在所述利用修复后的应用程序进行启动的步骤之后,所述计算机可读指令被所述处理器执行时,使得所述一个或多个处理器还执行以下步骤:接收服务器推送的应用程序版本更新通知;根据所述更新通知生成更新请求,将所述更新请求发送至服务器,以使得服务器根据所述更新请求获取新版本应用程序与当前版本应用程序之间的差异数据,利用差异数据生成增量包;及接收服务器返回的增量包,利用所述增量包对应用程序进行增量更新。
- 一个或多个存储有计算机可读指令的计算机可读非易失性存储介质,计算机可读指令被一个或多个处理器执行时,使得一个或多个处理器执行以下步骤:获取应用程序的启动标识和启动页面;对应用程序的启动过程进行跟踪,获取所述启动标识在预设时间内出现的次数或者在所述启动页面的停留时间;若所述启动标识在预设时间内出现的次数达到阈值或者在所述启动页面的停留时间超过预设时间,则记录应用程序启动失败;从启动页面跳转至修复页面,所述修复页面包括修复控件;获取所述修复控件对应的触发事件,响应所述触发事件对应用程序进行修复;及利用修复后的应用程序进行启动。
- 根据权利要求17所述的存储介质,其特征在于,所述计算机可读指令被一个或多个处理器执行时,使得一个或多个处理器还执行以下步骤:响应所述触发事件获取应用程序的版本信息,利用所述版本信息生成补丁获取请求;将所述补丁获取请求发送至服务器,以使得服务器根据所述版本信息获取对应的补丁,返回所述补丁;及接收所述补丁,利用所述补丁对应用程序进行修复。
- 根据权利要求17所述的存储介质,其特征在于,在所述利用修复后的应用程序进行启动的步骤之后,所述计算机可读指令被一个或多个处理器执行时,使得一个或多个处理器还执行以下步骤:向服务器发送页面获取请求,以使得服务器根据所述页面获取请求获取对应的页面,若所述页面大于阈值,则对所述页面添加缓存标签;接收服务器返回的添加了缓存标签的页面,根据缓存标签对所述页面的加载过程进行拦截,将拦截后的页面进行缓存;及加载缓存后的页面,进行页面展示。
- 根据权利要求17-19任一项所述的存储介质,其特征在于,在所述利用修复后的应用程序进行启动的步骤之后,所述计算机可读指令被一个或多个处理器执行时,使得一个或多个处理器还执行以下步骤:接收服务器推送的应用程序版本更新通知;根据所述更新通知生成更新请求,将所述更新请求发送至服务器,以使得服务器根据所述更新请求获取新版本应用程序与当前版本应用程序之间的差异数据,利用差异数据生成增量包;及接收服务器返回的增量包,利用所述增量包对应用程序进行增量更新。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710619943.6 | 2017-07-26 | ||
CN201710619943.6A CN107783795B (zh) | 2017-07-26 | 2017-07-26 | 应用程序启动方法、装置、计算机设备和存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019019668A1 true WO2019019668A1 (zh) | 2019-01-31 |
Family
ID=61437736
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/079885 WO2019019668A1 (zh) | 2017-07-26 | 2018-03-21 | 应用程序启动方法、装置、计算机设备和存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN107783795B (zh) |
WO (1) | WO2019019668A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112764958A (zh) * | 2021-01-27 | 2021-05-07 | 上海淇玥信息技术有限公司 | 一种辅助修复页面故障的方法、装置和电子设备 |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107783795B (zh) * | 2017-07-26 | 2021-05-28 | 深圳壹账通智能科技有限公司 | 应用程序启动方法、装置、计算机设备和存储介质 |
CN108710496A (zh) * | 2018-05-17 | 2018-10-26 | 腾讯科技(深圳)有限公司 | 应用程序的配置更新方法、装置、设备及存储介质 |
CN109408139A (zh) * | 2018-09-26 | 2019-03-01 | 平安普惠企业管理有限公司 | 应用程序的开启方法、装置、计算机设备及存储介质 |
CN109669736A (zh) * | 2018-12-18 | 2019-04-23 | 北京城市网邻信息技术有限公司 | 一种小程序的加载方法、装置、终端设备和存储介质 |
CN110162725A (zh) * | 2019-04-10 | 2019-08-23 | 浙江口碑网络技术有限公司 | 在线页面加载方法、装置、存储介质及计算机设备 |
CN110244977A (zh) * | 2019-05-21 | 2019-09-17 | 深圳壹账通智能科技有限公司 | 定制化软件生成方法、系统、电子设备及存储介质 |
CN110308951B (zh) * | 2019-06-28 | 2022-07-19 | Oppo广东移动通信有限公司 | 一种启动界面卡顿的处理方法及装置、设备、存储介质 |
CN110413341A (zh) * | 2019-07-02 | 2019-11-05 | 上海上湖信息技术有限公司 | 一种应用程序的启动方法、装置、终端及介质 |
CN110377365B (zh) * | 2019-07-19 | 2022-06-07 | 腾讯科技(深圳)有限公司 | 展示小程序的方法和装置 |
CN110750284B (zh) * | 2019-10-15 | 2023-03-28 | Oppo(重庆)智能科技有限公司 | 一种应用快速启动方法、终端及计算机可读存储介质 |
CN110727479A (zh) * | 2019-10-22 | 2020-01-24 | 北京字节跳动网络技术有限公司 | 执行应用启动代码的方法、装置、终端及存储介质 |
CN111399947B (zh) * | 2020-06-02 | 2020-09-04 | 平安国际智慧城市科技股份有限公司 | 应用程序引导页优化推送方法、装置及计算机设备 |
CN112905375A (zh) * | 2021-02-07 | 2021-06-04 | 南方电网数字电网研究院有限公司 | 双芯智能电表管理单元的自恢复方法、装置和计算机设备 |
CN113849391B (zh) * | 2021-10-08 | 2024-08-09 | 珠海格力电器股份有限公司 | 一种程序性能的确定方法和装置、电子设备和存储介质 |
CN118093272B (zh) * | 2024-04-07 | 2024-09-13 | 荣耀终端有限公司 | 音频服务启动方法及电子设备 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103995715A (zh) * | 2014-05-06 | 2014-08-20 | 百度在线网络技术(北京)有限公司 | 应用程序的修复方法、装置及服务器 |
CN104881299A (zh) * | 2014-02-28 | 2015-09-02 | 可牛网络技术(北京)有限公司 | 一种应用程序冻结方法及装置 |
CN106453509A (zh) * | 2013-10-22 | 2017-02-22 | 北京奇虎科技有限公司 | 浏览器异常关闭的处理方法、系统、浏览器和服务器 |
CN106843928A (zh) * | 2016-12-22 | 2017-06-13 | 北京五八信息技术有限公司 | 应用程序的远程修复方法及设备 |
CN107783795A (zh) * | 2017-07-26 | 2018-03-09 | 上海壹账通金融科技有限公司 | 应用程序启动方法、装置、计算机设备和存储介质 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103530199B (zh) * | 2012-07-02 | 2015-12-02 | 腾讯科技(深圳)有限公司 | 一种修复软件运行错误的方法、装置及系统 |
CN103678032B (zh) * | 2012-09-17 | 2017-10-31 | 腾讯科技(深圳)有限公司 | 系统文件的修复方法及装置 |
-
2017
- 2017-07-26 CN CN201710619943.6A patent/CN107783795B/zh active Active
-
2018
- 2018-03-21 WO PCT/CN2018/079885 patent/WO2019019668A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106453509A (zh) * | 2013-10-22 | 2017-02-22 | 北京奇虎科技有限公司 | 浏览器异常关闭的处理方法、系统、浏览器和服务器 |
CN104881299A (zh) * | 2014-02-28 | 2015-09-02 | 可牛网络技术(北京)有限公司 | 一种应用程序冻结方法及装置 |
CN103995715A (zh) * | 2014-05-06 | 2014-08-20 | 百度在线网络技术(北京)有限公司 | 应用程序的修复方法、装置及服务器 |
CN106843928A (zh) * | 2016-12-22 | 2017-06-13 | 北京五八信息技术有限公司 | 应用程序的远程修复方法及设备 |
CN107783795A (zh) * | 2017-07-26 | 2018-03-09 | 上海壹账通金融科技有限公司 | 应用程序启动方法、装置、计算机设备和存储介质 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112764958A (zh) * | 2021-01-27 | 2021-05-07 | 上海淇玥信息技术有限公司 | 一种辅助修复页面故障的方法、装置和电子设备 |
Also Published As
Publication number | Publication date |
---|---|
CN107783795B (zh) | 2021-05-28 |
CN107783795A (zh) | 2018-03-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019019668A1 (zh) | 应用程序启动方法、装置、计算机设备和存储介质 | |
US11868785B2 (en) | Application program page processing method and device | |
CN107729041B (zh) | 应用程序热更新方法、装置、终端和存储介质 | |
CN106708557B (zh) | 一种针对终端应用的更新处理方法及装置 | |
US10127057B2 (en) | Method and apparatus for dynamically implementing application function | |
US9244673B2 (en) | System and method for updating application archive files | |
US8667487B1 (en) | Web browser extensions | |
US9032383B2 (en) | Automatically updating applications on a client's device without interrupting the user's experience | |
US9367403B2 (en) | Terminal and application restoring method | |
WO2018227822A1 (zh) | 异常堆栈信息获取方法、装置及计算机可读存储介质 | |
US20160224207A1 (en) | Method and system for freezing and unfreezing applications | |
US20130219383A1 (en) | Using an Application Cache to Update Resources of Installed Applications | |
US9516094B2 (en) | Event-responsive download of portions of streamed applications | |
KR101674934B1 (ko) | 오류 보고 방법 및 장치 | |
US10546126B2 (en) | Method for detecting the tampering of application code and electronic device supporting the same | |
WO2022247301A1 (zh) | 检测方法、图形界面及相关装置 | |
CN112394906B (zh) | 一种应用切换运行的方法及设备 | |
WO2016082450A1 (zh) | 一种用户终端的升级方法和用户终端 | |
CN115454827B (zh) | 兼容性检测方法、系统、设备和介质 | |
US20150212866A1 (en) | Management system for service of multiple operating environments, and methods thereof | |
CN115562732A (zh) | 一种开机方法、电子设备及计算机存储介质 | |
CN110727945A (zh) | 病毒扫描方法、设备以及计算机可读介质 | |
US20230401047A1 (en) | Graphical user interface for reducing vulnerabilities associated with legacy software | |
KR20200006841A (ko) | 어플리케이션의 포그라운드 서비스 실행시 보안을 제공하기 위한 통신 단말 및 방법 | |
CN116257278B (zh) | 一种应用软件的补丁执行方法和存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18838145 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18838145 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28.05.2020) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18838145 Country of ref document: EP Kind code of ref document: A1 |