CN111538502A - Installation package processing method and device, electronic equipment and storage medium - Google Patents
Installation package processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111538502A CN111538502A CN202010231582.XA CN202010231582A CN111538502A CN 111538502 A CN111538502 A CN 111538502A CN 202010231582 A CN202010231582 A CN 202010231582A CN 111538502 A CN111538502 A CN 111538502A
- Authority
- CN
- China
- Prior art keywords
- file
- identification information
- installation package
- resource identification
- resource
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/443—Optimisation
- G06F8/4434—Reducing the memory space required by the program code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure relates to a processing method and device of an installation package, an electronic device and a storage medium, wherein the method comprises the following steps: acquiring a detection rule and/or a detection result aiming at the installation package to be processed, wherein the detection rule and/or the detection result comprises file identification information of all markup files to be detected; searching resource identification information meeting preset requirements in all marked files according to the file identification information; storing the resource identification information into a target mark file; and compiling the code of the installation package according to the target mark file. The resource ID information in the resource identification definition file of the BufferKnife is stored into the resource identification storage file, the resource identification storage file is used for storing the resource ID information of each type of resource of the installation package, the resource identification storage file does not belong to useless resources and cannot be deleted, and the problem that compiling is not passed due to the fact that the resource ID information in the resource identification definition file is lost is solved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for processing an installation package, an electronic device, and a storage medium.
Background
With the rapid iterative growth of services, new service logic codes, image resources and third party Software Development Kits (SDKs) are continuously introduced into Application programs (APPs), which directly leads to the continuous growth of installation package volume of the Application programs, and problems caused by the growth of the installation package volume are more and more, for example, the download pressure of an Application market for providing installation package download is increased, and the flow consumed by users for downloading the installation packages is increased.
In the related art, when the volume of an installation package of an application under an Android (Android) system is optimized, Android Lint (a static code detection tool for detecting code quality) is usually adopted to detect useless resources from the installation package, and then the detected useless resources are manually deleted. When bufferKnife (a frame is injected by focusing on views of an Android system (base classes of all controls in the Android system)) is introduced into an installation package, because the detection result of the Android Lint contains the identifier in a resource identifier definition (a file generated by compiling the code of the installation package of the Android system and used for defining the identifier of each type of resource) file of the bufferKnife, if the identifier in the resource identifier definition file is directly deleted, the problem that the code of the installation package cannot be compiled is caused.
Disclosure of Invention
The disclosure provides a processing method and device of an installation package, an electronic device and a storage medium, which are used for solving the problem that the code compiling of the installation package in the related art is not passed. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, a method for processing an installation package is provided, including: acquiring a detection rule and/or a detection result aiming at an installation package to be processed, wherein the detection rule and/or the detection result comprise file identification information of all markup files to be detected; searching resource identification information meeting preset requirements in all marked files according to the file identification information; storing the resource identification information into a target mark file; and compiling the code of the installation package according to the target mark file.
Optionally, the searching for resource identification information meeting preset requirements in all the markup files according to the file identification information includes: and searching the newly added resource identification information of the resource identification definition file in all the marked files according to the file identification information.
Optionally, the storing the resource identification information into a target markup file includes: and storing the resource identification information into a resource identification storage file.
Optionally, the detection rule is used to detect a changed code of the installation package, and/or the detection result represents a detection result of the changed code of the installation package.
Optionally, the method is applied to an automation script, the automation script being configured in a persistent integration CI framework; the method further comprises the following steps: and executing the automation script according to a preset period.
According to a second aspect of the embodiments of the present disclosure, there is provided a processing apparatus for an installation package, including: the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is configured to acquire a detection rule and/or a detection result aiming at an installation package to be processed, and the detection rule and/or the detection result comprise file identification information of all mark files to be detected; the searching module is configured to search the resource identification information meeting the preset requirement in all the marked files according to the file identification information; a storage module configured to store the resource identification information into a target markup file; a compiling module configured to compile the code of the installation package according to the target markup file.
Optionally, the searching module is configured to search the resource identification information newly added to the resource identification definition file in all the markup files according to the file identification information.
Optionally, the storage module is configured to store the resource identification information into a resource identification storage file.
Optionally, the detection rule is used to detect a changed code of the installation package, and/or the detection result represents a detection result of the changed code of the installation package.
Optionally, the apparatus is based on an automation script configured in a persistent integrated CI framework, the automation script being executed according to a preset cycle.
According to a third aspect of the embodiments of the present disclosure, there is provided an electronic apparatus including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the processing method of the installation package according to the first aspect.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium, wherein instructions of the storage medium, when executed by a processor of an electronic device, enable the electronic device to execute the processing method of the installation package according to the first aspect.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising readable program code executable by a processor of an electronic device to perform the method for processing an installation package of the first aspect.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
in the embodiment of the disclosure, a detection rule and/or a detection result for an installation package to be processed is obtained, the detection rule and/or the detection result includes file identification information of all markup files to be detected, all markup files to be detected are determined according to the file identification information of all markup files, resource identification information meeting preset requirements is searched in all markup files to be detected, the searched resource identification information is stored in a target markup file, and then codes of the installation package are compiled according to the target markup file.
In the process of optimizing the volume of the installation package in the Android system by using the technical scheme in the embodiment of the disclosure, when buffer Knife is introduced, all markup files to be detected can be determined according to the detection rule and/or the detection result of the Android Lint, resource Identification (ID) information meeting the preset requirement is searched in all markup files to be detected, the searched resource ID information is stored in a resource identification storage file, and then the code of the installation package is compiled according to the resource identification storage file. The resource ID information in the resource identification definition file of the BufferKnife is stored into the resource identification storage file, the resource identification storage file is used for storing the resource ID information of each type of resource of the installation package, the resource identification storage file does not belong to useless resources and cannot be deleted, and the problem that compiling cannot be passed due to the fact that the resource ID information in the resource identification definition file is lost is solved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a flow diagram illustrating a method of processing an installation package in accordance with an exemplary embodiment.
FIG. 2 is a block diagram illustrating a processing device of an installation package in accordance with an example embodiment.
FIG. 3 is a block diagram illustrating one type of processing electronics for installing a package in accordance with an exemplary embodiment.
FIG. 4 is a block diagram illustrating an electronic device for processing installation packages in accordance with an example embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating a processing method of an installation package according to an exemplary embodiment, and the processing method of the installation package may include the following steps, as shown in fig. 1.
In step S11, a detection rule and/or a detection result for the installation package to be processed is acquired.
In embodiments of the present disclosure, detection rules for pending installation packages may be used to detect useless resources in installation packages. In practical application, the detection rule may be a detection rule of Android Lint. The Android Lint is a static code detection tool provided by the Android SDK, and can be used for detecting the code quality of an installation package. The source Code of Android Lint is integrated in Android SDK, and can be called by a [/gradleew Lint command under an item directory, or can be called by an [ Analyze ] > [ appearance Code ] path of Android Studio. The Android Lint can detect the codes of the installation package based on the detection rule to obtain a detection result. The Android Lint can find and correct the problem of the quality of the code structure without actually executing the code or compiling a test case. The detection results will provide a description of each problem detected and provide a message of the problem and severity level so that critical improvements that need to be prioritized can be quickly determined.
The Android Lint can configure Lint. xml and lintooptions to realize detection rules meeting actual requirements. XML may include file identification information of all Markup files to be detected, such as file identification information of an eXtensible Markup Language (XML) file, and may also specify which check functions are disabled, and a custom Problem Severity level (product security Levels). The LintConfig file in linthops may be used to specify the directory location where the detection rule is located. The Android Lint can generate a detection result after detecting the code of the installation package according to the detection rule, and the detection result can include file identification information of all XML files to be detected.
In practical application, different levels of detection rules can be configured according to practical situations:
a. global (Whole project)
b. Project module
c. Production module
d. Test module
e. Opened file
f. Class hierarchy
g version controls system range
In step S12, resource identification information meeting the preset requirements is searched for among all markup files according to the file identification information.
In the embodiment of the disclosure, when the installation package of the Android system is compiled, an r.java file is automatically generated, and the r.java file is used for storing identification information of all resource files. BufferKnife is a relatively simple and easy-to-understand open source framework in annotations, and is a View injection framework dedicated to an Android system. Since the annotations used by ButterKnife are not reflected at runtime, but are generated at compile time, ButterKnife has substantially no loss in performance. ButterKnife is a framework for dependent injection, and the most central way to use is to use annotations for dependent injection. The ButterKnife needs to copy an r.java file and rename the r.java file to an r2.java file, that is, a resource identifier definition file, so as to convert the identifier information of the static variables in the r.java file into the static variables by adding final keywords in the r2.java file.
In practical application, the resource identification information searched in all XML files may be the resource identification information with the attribute of being newly added in the r2.java file.
In step S13, the resource identification information is stored in the target markup file.
In the embodiment of the present disclosure, the searched resource identification information meeting the preset requirement may be stored in a resource identification storage file, such as an ids. The ids. XML file can manage the resource identification information in all XML files uniformly.
In step S14, the code of the installation package is compiled from the object markup file.
In the embodiment of the disclosure, when the code of the installation package is compiled, the resource identification information can be searched from the ids.xml file, and then the corresponding resource is found in the r2.java file, so that the problem that the compilation is not passed due to the loss of the resource identification information in the r2.java file is avoided.
Generally, when the Android Lint detects an installation package, all codes of the installation package are detected, which consumes a lot of time. In an exemplary embodiment of the disclosure, when the Android Lint detects the installation package, the Android Lint can be used to detect a changed part of the installation package from a changed angle, such as detecting a module with a change, a code of a resource, and the like, so that the detection time of the Android Lint is reduced, and the detection efficiency is improved. Therefore, the preset detection rule can be used for the code changed in the installation package correspondingly, and the detection result can be the detection result of the changed code of the installation package.
When the useless resources of the installation package are deleted, manual deletion is needed. In an exemplary embodiment of the present disclosure, the above processing method for the installation package may be implemented by an automation script, and in practical applications, the automation script may be implemented by Python (a cross-platform computer programming language). Moreover, the automation script may be configured in a Continuous Integration (CI) framework. Continuous integration is a software development practice, i.e., team development members often integrate their work, usually at least once per member per day, meaning that multiple integrations may occur per day. Each integration is verified by automated build (including compile, release, automated testing) to discover integration errors as early as possible.
In practical applications, the automation script may be executed according to a preset period. For example, before each version of the installation package, an automation script is executed once to detect the code of the installation package by using the Android Lint to obtain the useless resource, and then the useless resource is deleted to reduce the volume of the installation package. Embodiments of the present disclosure utilize automation scripts to implement automatic deletion of useless resources of an installation package.
Moreover, when the useless resources of the installation package are deleted, a log record may be generated, and the log record may include a path, an attribute, a deletion time, and the like of each of the useless resources. The useless resource deletion situation for a period of time can be counted according to the log records. If problems such as installation and operation of the installation package occur after the useless resources are deleted, the reason of the problems can be inquired according to the log records.
In the embodiment of the disclosure, a detection rule and/or a detection result for an installation package to be processed is obtained, the detection rule and/or the detection result includes file identification information of all markup files to be detected, all markup files to be detected are determined according to the file identification information of all markup files, resource identification information meeting preset requirements is searched in all markup files to be detected, the searched resource identification information is stored in a target markup file, and then codes of the installation package are compiled according to the target markup file.
In the process of optimizing the volume of the installation package in the Android system by using the technical scheme in the embodiment of the disclosure, when buffer Knife is introduced, all markup files to be detected can be determined according to the detection rule and/or the detection result of the Android Lint, resource Identification (ID) information meeting the preset requirement is searched in all markup files to be detected, the searched resource ID information is stored in a resource identification storage file, and then the code of the installation package is compiled according to the resource identification storage file. According to the method and the device for detecting the BufferKnife resource identifier, the resource ID information in the resource identifier definition file of the BufferKnife is stored into the resource identifier storage file, the resource identifier storage file is used for storing the resource ID information of various types of resources of the installation package, the resource identifier storage file does not belong to useless resources and cannot be deleted, the problem that compiling cannot be passed due to loss of the resource ID information in the resource identifier definition file is avoided, and the compatibility of the detection rule of the BufferKnife and the Android Lint is improved.
FIG. 2 is a block diagram illustrating a processing device of an installation package in accordance with an example embodiment. The apparatus may specifically include the following modules.
The acquisition module 21 is configured to acquire a detection rule and/or a detection result for the installation package to be processed, where the detection rule and/or the detection result includes file identification information of all markup files to be detected;
a searching module 22 configured to search the resource identification information meeting the preset requirement in all the markup files according to the file identification information;
a storage module 23 configured to store the resource identification information into a target markup file;
a compiling module 24 configured to compile the code of the installation package according to the target markup file.
In an exemplary embodiment of the disclosure, the search module 22 is configured to search the whole markup files for resource identification information newly added to the resource identification definition file according to the file identification information.
In an exemplary embodiment of the present disclosure, the storage module 23 is configured to store the resource identification information into a resource identification storage file.
In an exemplary embodiment of the disclosure, the detection rule is used for detecting a changed code of the installation package, and/or the detection result represents a detection result of the changed code of the installation package.
In an exemplary embodiment of the present disclosure, the apparatus is based on an automation script configured in a persistent integrated CI framework, the automation script being executed according to a preset cycle.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
FIG. 3 is a block diagram illustrating one type of processing electronics 300 for installation packages in accordance with an illustrative embodiment. For example, the electronic device 300 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 3, electronic device 300 may include one or more of the following components: a processing component 302, a memory 304, a power component 306, a multimedia component 308, an audio component 310, an input/output (I/O) interface 312, a sensor component 314, and a communication component 316.
The processing component 302 generally controls overall operation of the electronic device 300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 302 may include one or more processors 320 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 302 can include one or more modules that facilitate interaction between the processing component 302 and other components. For example, the processing component 302 may include a multimedia module to facilitate interaction between the multimedia component 308 and the processing component 302.
The memory 304 is configured to store various types of data to support operations at the electronic device 300. Examples of such data include instructions for any application or method operating on the electronic device 300, contact data, phonebook data, messages, images, videos, and so forth. The memory 304 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The power supply component 306 provides power to the various components of the electronic device 300. The power components 306 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the electronic device 300.
The multimedia component 308 comprises a screen providing an output interface between the electronic device 300 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 308 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the electronic device 300 is in an operation mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 310 is configured to output and/or input audio signals. For example, the audio component 310 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 300 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 304 or transmitted via the communication component 316. In some embodiments, audio component 310 also includes a speaker for outputting audio signals.
The I/O interface 312 provides an interface between the processing component 302 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The communication component 316 is configured to facilitate wired or wireless communication between the electronic device 300 and other devices. The electronic device 300 may access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 316 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 316 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the electronic device 300 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a storage medium comprising instructions, such as the memory 304 comprising instructions, executable by the processor 320 of the electronic device 300 to perform the above-described method is also provided. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, a computer program product is also provided, which comprises readable program code executable by the processor 320 of the electronic device 300 to perform the above-described method. Alternatively, the program code may be stored in a storage medium of the electronic device 300, which may be a non-transitory computer-readable storage medium, for example, ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
FIG. 4 is a block diagram illustrating an electronic device 400 for processing installation packages in accordance with an example embodiment. For example, the electronic device 400 may be provided as a server. Referring to fig. 4, electronic device 400 includes a processing component 422 that further includes one or more processors, and memory resources, represented by memory 432, for storing instructions, such as applications, that are executable by processing component 422. The application programs stored in memory 432 may include one or more modules that each correspond to a set of instructions. Further, the processing component 422 is configured to execute instructions to perform the installation package processing methods described above.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A processing method of an installation package is characterized by comprising the following steps:
acquiring a detection rule and/or a detection result aiming at an installation package to be processed, wherein the detection rule and/or the detection result comprise file identification information of all markup files to be detected;
searching resource identification information meeting preset requirements in all marked files according to the file identification information;
storing the resource identification information into a target mark file;
and compiling the code of the installation package according to the target mark file.
2. The method according to claim 1, wherein the searching for resource identification information meeting preset requirements from all markup files according to the file identification information comprises:
and searching the newly added resource identification information of the resource identification definition file in all the marked files according to the file identification information.
3. The method of claim 1, wherein storing the resource identification information in a target markup file comprises:
and storing the resource identification information into a resource identification storage file.
4. The method according to claim 1, wherein the detection rule is used for detecting the changed code of the installation package, and/or the detection result represents the detection result of the changed code of the installation package.
5. The method of claim 1, applied to an automation script configured in a persistent integration CI framework;
the method further comprises the following steps:
and executing the automation script according to a preset period.
6. A processing apparatus for an installation package, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is configured to acquire a detection rule and/or a detection result aiming at an installation package to be processed, and the detection rule and/or the detection result comprise file identification information of all mark files to be detected;
the searching module is configured to search the resource identification information meeting the preset requirement in all the marked files according to the file identification information;
a storage module configured to store the resource identification information into a target markup file;
a compiling module configured to compile the code of the installation package according to the target markup file.
7. The apparatus according to claim 6, wherein the searching module is configured to search the whole markup files for resource identification information newly added to the resource identification definition file according to the file identification information.
8. The apparatus of claim 6, wherein the storage module is configured to store the resource identification information in a resource identification storage file.
9. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of processing the installation package of any one of claims 1 to 5.
10. A storage medium, characterized in that instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the processing method of an installation package according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010231582.XA CN111538502A (en) | 2020-03-27 | 2020-03-27 | Installation package processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010231582.XA CN111538502A (en) | 2020-03-27 | 2020-03-27 | Installation package processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111538502A true CN111538502A (en) | 2020-08-14 |
Family
ID=71978443
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010231582.XA Pending CN111538502A (en) | 2020-03-27 | 2020-03-27 | Installation package processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111538502A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112084747A (en) * | 2020-09-17 | 2020-12-15 | 瑞庭网络技术（上海）有限公司 | Resource management method and device, electronic equipment and storage medium |
| CN112783512A (en) * | 2021-03-15 | 2021-05-11 | 腾讯科技（深圳）有限公司 | Application package processing method, device, equipment and storage medium |
| CN116932012A (en) * | 2023-09-15 | 2023-10-24 | 合肥康芯威存储技术有限公司 | Memory firmware upgrading method, device and medium based on data verification |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050177812A1 (en) * | 1999-12-01 | 2005-08-11 | Microsoft Corporation | External resource files for application development and management |
| CN107783766A (en) * | 2016-08-25 | 2018-03-09 | 腾讯科技（深圳）有限公司 | The method and apparatus cleared up the file of application program |
-
2020
- 2020-03-27 CN CN202010231582.XA patent/CN111538502A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050177812A1 (en) * | 1999-12-01 | 2005-08-11 | Microsoft Corporation | External resource files for application development and management |
| CN107783766A (en) * | 2016-08-25 | 2018-03-09 | 腾讯科技（深圳）有限公司 | The method and apparatus cleared up the file of application program |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112084747A (en) * | 2020-09-17 | 2020-12-15 | 瑞庭网络技术（上海）有限公司 | Resource management method and device, electronic equipment and storage medium |
| CN112084747B (en) * | 2020-09-17 | 2024-02-02 | 瑞庭网络技术（上海）有限公司 | Resource management method and device, electronic equipment and storage medium |
| CN112783512A (en) * | 2021-03-15 | 2021-05-11 | 腾讯科技（深圳）有限公司 | Application package processing method, device, equipment and storage medium |
| CN112783512B (en) * | 2021-03-15 | 2024-05-10 | 腾讯科技（深圳）有限公司 | Application package processing method, device, equipment and storage medium |
| CN116932012A (en) * | 2023-09-15 | 2023-10-24 | 合肥康芯威存储技术有限公司 | Memory firmware upgrading method, device and medium based on data verification |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107423106B (en) | Method and apparatus for supporting multi-frame syntax | |
| CN111221559B (en) | Application updating method, device, storage medium, terminal and server | |
| CN106406956B (en) | Application program installation method and device | |
| CN111538502A (en) | Installation package processing method and device, electronic equipment and storage medium | |
| CN111221733A (en) | Information processing method and device, mobile terminal and storage medium | |
| CN115185717A (en) | Interface calling method and device, electronic equipment and storage medium | |
| CN109344051B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111580824B (en) | Program optimization method, device and storage medium | |
| CN112114814A (en) | Compiled file determining method and device and application program generating method and device | |
| CN106293683B (en) | Project compiling method and device | |
| CN111913756A (en) | Application program optimization method, device and system, electronic equipment and storage medium | |
| CN111209195A (en) | Method and device for generating test case | |
| CN112631695A (en) | Data verification method and device, electronic equipment and storage medium | |
| CN107193622B (en) | Code compiling processing method and device and terminal | |
| CN112306883A (en) | Software testing method, device and medium | |
| CN112333233A (en) | Event information reporting method and device, electronic equipment and storage medium | |
| CN109933357B (en) | Application program upgrading method and device | |
| CN111597106A (en) | Point burying management method and device | |
| CN112711420B (en) | Code conversion method and device | |
| CN117492823B (en) | Code acquisition method, device, electronic equipment and readable storage medium | |
| CN110659081B (en) | File processing method and device for program object and electronic equipment | |
| CN113934452B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110347394B (en) | Software code analysis method and device | |
| CN113535183B (en) | Code processing method, device, electronic equipment and storage medium | |
| CN113885938A (en) | Code modification method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |