Application version difference analysis method, device, equipment, medium and product

Abstract

This application discloses a method, apparatus, device, medium, and product for analyzing version differences of an application. The method, in response to a user's import operation of multiple versions of a first application package while a front-end interface is displayed, obtains multiple versions of the first application package; displays preset controls on the front-end interface; receives a first input from the user to the preset controls; in response to the first input, compares the differences of preset files in each version of the package to obtain difference information between the multiple versions of the first application; and displays the difference information. According to embodiments of this application, it is possible to analyze differences between versions, providing a more user-friendly human-computer interaction interface and enhancing portability and interactivity.

Description

Technical Field

[0001] This application belongs to the field of big data intelligent analysis technology, and in particular relates to a method, apparatus, device, medium and product for analyzing version differences of application programs. Background Technology

[0002] With the development of technology, application versions are updated frequently. In order to analyze the differences between different versions of an application, it is necessary to perform a difference analysis on the application package.

[0003] Typically, in existing application version difference analysis solutions, one approach is to use Spring to package the application, which requires loading the application package first and then analyzing the application version dependencies. Another approach is to read the files in the application package using the getServletContext method and then resolve the application version dependencies.

[0004] However, the output of Spring's package is too simple, and manual statistical analysis is still required. The interactivity is poor, and the getServletContext method is only applicable to the analysis of the current application version, which is not good for analyzing different versions. Summary of the Invention

[0005] This application provides a method, apparatus, device, medium, and product for analyzing version differences of applications, which can analyze the differences between versions of different applications, provide a more user-friendly human-computer interaction interface, and enhance portability and interactivity.

[0006] In a first aspect, embodiments of this application provide a method for analyzing version differences of an application, the method comprising: When a front-end interface is displayed, in response to the user's import operation of multiple versions of the first application package, the multiple versions of the first application package are obtained. Display preset controls on the front-end interface; Receive the user's first input to the preset control; In response to the first input, the differences between preset files in different versions of the application package are compared to obtain the difference information between multiple versions of the first application. Display the difference information.

[0007] Secondly, embodiments of this application provide an application version difference analysis apparatus, the apparatus comprising: The acquisition module is used to acquire multiple versions of the application package in response to the user's import operation of multiple versions of the application package when a front-end interface is displayed. The first display module is used to display preset controls on the front-end interface; The receiving module is used to receive the user's first input to the preset control; The comparison module is used to compare the differences of preset files in different versions of the application package in response to the first input, and obtain the difference information between multiple versions of the first application. The second display module is used to display difference information.

[0008] Thirdly, embodiments of this application provide an electronic device, which includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the steps of the application version difference analysis method as described in any embodiment of the first aspect.

[0009] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the steps of the application version difference analysis method as described in any embodiment of the first aspect.

[0010] Fifthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform the steps of the application version difference analysis method as described in any embodiment of the first aspect.

[0011] This application provides a method, apparatus, device, medium, and product for analyzing version differences of an application. By having a user import multiple versions of a first application package, multiple versions of the first application package are obtained. Preset controls are displayed on a front-end interface. By inputting the first value of these preset controls, the user can compare preset files within each version of the application package. Thus, this application allows users to import different versions of application packages for comparison through the front-end interface. Users can then compare different application versions by inputting the first value of the preset controls on the front-end interface, and the differences are displayed on the front-end interface. Therefore, the application version difference analysis method provided in this application provides a more user-friendly human-computer interaction interface, enhancing the portability and interactivity of application version difference analysis. Attached Figure Description

[0012] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This is a flowchart illustrating a method for analyzing version differences of an application provided in an embodiment of this application; Figure 2 This is a flowchart illustrating another application version difference analysis method provided in this application embodiment; Figure 3 This is a schematic diagram of the structure of an application version difference analysis device provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0014] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0015] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0016] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0017] As described in the background section, the inventors discovered that existing methods for analyzing application version differences often utilize the `dependency:tree` command. This command analyzes dependencies throughout its lifecycle. Using Spring package loading, the application package needs to be loaded first, followed by analysis of application version dependencies. However, Spring's output is overly simplistic, still requiring manual statistical analysis and lacking user-friendliness and interactivity. Another method for analyzing application version differences involves reading files from the application package using the `getServletContext` method and then resolving application version dependencies. This method has significant limitations, only applicable to the current version and poor at analyzing differences between versions.

[0018] To address the problems of existing technologies, this application provides a method for analyzing version differences in applications. By importing multiple versions of a first application package from a user, multiple versions of the application package are obtained. Preset controls are displayed on the front-end interface. By inputting the first value of these preset controls, the user can compare preset files within each version of the application package. Thus, in this application embodiment, users can import different versions of the application package to be compared through the front-end interface. Then, by inputting the first value of the preset controls on the front-end interface, users can compare versions of different applications and display the differences on the front-end interface. Therefore, the application version difference analysis method provided by this application embodiment offers a more user-friendly human-computer interaction interface, enhancing the portability and interactivity of application version difference analysis.

[0019] The version difference analysis method for the application provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0020] Figure 1 This is a flowchart illustrating a method for analyzing version differences in an application provided in an embodiment of this application. Figure 1 As shown, the application version difference analysis method provided in this application embodiment may include the following steps S110 to S150: S110. When a front-end interface is displayed, in response to the user's import operation of multiple versions of the first application package, obtain multiple versions of the first application package. S120. Display preset controls on the front-end interface; S130, Receive the user's first input to the preset control; S140. In response to the first input, compare the differences of preset files in each version of the program package to obtain the difference information between multiple versions of the first application. S150, Display difference information.

[0021] Therefore, by importing multiple versions of the application package into the user's application, multiple versions of the application package are obtained, and preset controls are displayed on the front-end interface. Users can compare preset files in each version of the application package by inputting the first input to the preset controls on the front-end interface. Thus, in this embodiment, users can import different versions of the application package to be compared through the front-end interface, and then compare versions of different applications by inputting the first input to the preset controls on the front-end interface, displaying the differences on the front-end interface. Therefore, the application version difference analysis method provided in this embodiment offers a more user-friendly human-computer interaction interface, enhancing the portability and interactivity of application version difference analysis.

[0022] The specific implementation methods for each of the above steps are described below.

[0023] It should be noted that, in this embodiment of the application, the front-end interface displays an option to import multiple versions of the first application package, allowing the user to import multiple versions of the package. In some embodiments, in S110, when the front-end interface is displayed, the user imports multiple versions of the first application package into the application version difference analysis device by inputting the import option, thereby enabling the application version difference analysis device to obtain multiple versions of the first application package.

[0024] It should be noted that in this embodiment, there can be two, three, or more version packages. The number depends on the user's needs, and this embodiment does not impose a limit.

[0025] In some implementations, in S120, after the user imports multiple versions of the program package according to the import options, a preset control needs to be displayed on the front-end interface. The preset control can be a comparison button or a run button, which is not limited here.

[0026] In some implementations, in S130, the user clicks on a preset control displayed on the front-end interface to receive the user's operation command, thus requiring the user's input to the preset control.

[0027] In some implementations, in S140, after the user makes a first input to a preset control on the front-end interface, the application version difference analysis device compares the differences between preset files in multiple versions of the first application package to obtain difference information.

[0028] In some implementations, in S150, the differences between preset files in the packages of multiple versions of the first application can be displayed on the front-end interface.

[0029] To more intuitively and clearly display the differences between different versions of the program package, as an example of S150, the differences can be displayed in the form of a data chart, which can be a table or a line graph. This application embodiment does not limit the data chart.

[0030] In order to find the differences between multiple versions of an application more accurately and efficiently, this application also provides another implementation of the application version difference analysis method, as detailed in the following embodiments.

[0031] like Figure 2 As shown, the application version difference analysis method mentioned above may specifically include the following steps S210 to S270: S210. When a front-end interface is displayed, in response to the user's import operation of multiple versions of the first application package, obtain multiple versions of the first application package. S220. Display preset controls on the front-end interface; S230, Receive the user's first input to the preset control; S240. Locate the preset folder for each program package; In some embodiments, the packages of multiple versions of the first application contain a preset folder, such as a META-INF folder. The META-INF folder exists in file (Java Archive, jar) packages, but not in compressed (Zone Improvement Plan, zip) packages. The difference between JAR and ZIP is that the contents of a JAR file contain a META-INF folder, which is automatically created when the JAR file is generated.

[0032] S250: Search for a preset file named after a preset file in the preset folder; In some embodiments, the preset folder searched above, namely the META-INF folder, also includes a MANIFEST.MF file. The preset file needs to be found in the preset folder, for example, it can be a MANIFEST.MF file. The version identifier of the MANIFEST.MF file and the creator of the file are defined. This is achieved through the jar command-line tool. The MANIFEST.MF file includes at least one of the following: general attributes, application-related attributes, applet-related attributes, extension identifier attributes, package extension attributes, signature-related attributes, and custom attributes.

[0033] As an example, general attributes can define the version identifier of the MANIFEST.MF file and the file's generator (generated by the jar command-line tool), and can also define the jar file's signature version identifier and class search path; application-related attributes can define the jar file's entry class, which must be an executable class; once this attribute is defined, the jar file can be run; mini-program-related attributes specify a list of extended information required by the mini-program, with each tag in the list having corresponding attributes; extension identifier attributes define the jar file identifier; package extension attributes define the extension implementation title, extension implementation version identifier, extension implementation organization, organization identifier, download URL, extension specification title, extension specification version identifier, and extension specification organization; signature attributes define the jar file's entry class name, jar file algorithm name, and corresponding jar file content, encoded using 64 printable characters to represent binary data; custom attributes allow adding your own attributes to the MANIFEST.MF file to better annotate package information.

[0034] S260. In response to the first input, compare the differences of preset files in each version of the program package to obtain the difference information between multiple versions of the first application. S270, Display difference information.

[0035] S210 to S230 and S260 to S270 are the same as S110 to S150 in the above embodiments, and will not be described in detail here for the sake of brevity.

[0036] To enable the target audience to promptly view the differences between multiple versions of the first application and present them to the target audience in the form of an analysis report, this application embodiment also provides another implementation of the application version difference analysis method. Specifically, after S140, it may further include the following steps: Step A: Based on the difference information and analysis report template, generate a difference analysis report for multiple versions of the first application package; Step B: Send the difference analysis report to the target audience.

[0037] In some embodiments, after displaying the difference information between multiple versions of the package, a difference analysis report of multiple versions of the first application package can be generated by combining the built-in analysis report template.

[0038] As an example, a difference analysis report of multiple versions of the generated first application package is sent to the target object so that the target object can more easily distinguish the differences between different versions and better locate the problems in the versions by analyzing the report. The target object can be a user or a technician, and this application embodiment does not limit it.

[0039] To ensure data security, the application version difference analysis method provided in this embodiment may further include the following steps before S150: Obtain user permissions; Display information that differs from the user's permissions.

[0040] In some embodiments, such as performing differential analysis on multiple versions of the first application package, different users will have different permissions. It is necessary to obtain the user's permission information and present the visualization results. After obtaining the user's permission information, the differential results corresponding to the user's permission information can be displayed on the front-end interface.

[0041] Therefore, by importing multiple versions of the application package into the user's application, multiple versions of the application package are obtained, and preset controls are displayed on the front-end interface. Users can compare preset files in each version of the application package by inputting the first input to the preset controls on the front-end interface. Thus, in this embodiment, users can import different versions of the application package to be compared through the front-end interface, and then compare versions of different applications by inputting the first input to the preset controls on the front-end interface, displaying the differences on the front-end interface. Therefore, the application version difference analysis method provided in this embodiment offers a more user-friendly human-computer interaction interface, enhancing the portability and interactivity of application version difference analysis.

[0042] It should be noted that the application scenarios described in the above embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0043] Based on the same inventive concept, this application also provides a device for analyzing version differences of applications, specifically combined with... Figure 3 Please provide a detailed explanation.

[0044] Figure 3 This is a schematic diagram of the structure of an application version difference analysis device provided in an embodiment of this application.

[0045] like Figure 3 As shown, the version difference analysis device 300 of the application may include: The acquisition module 301 is used to acquire multiple versions of the application package in response to the user's import operation of multiple versions of the application package when a front-end interface is displayed. The first display module 302 is used to display preset controls on the front-end interface; The receiving module 303 is used to receive the user's first input to the preset control; The comparison module 304 is used to compare the differences of preset files in different versions of the program package in response to the first input, and obtain the difference information between multiple versions of the first application. The second display module 305 is used to display difference information.

[0046] Therefore, by importing multiple versions of the application package into the user's application, multiple versions of the application package are obtained, and preset controls are displayed on the front-end interface. Users can compare preset files in each version of the application package by inputting the first input to the preset controls on the front-end interface. Thus, in this embodiment, users can import different versions of the application package to be compared through the front-end interface, and then compare versions of different applications by inputting the first input to the preset controls on the front-end interface, displaying the differences on the front-end interface. Therefore, the application version difference analysis method provided in this embodiment offers a more user-friendly human-computer interaction interface, enhancing the portability and interactivity of application version difference analysis.

[0047] The version difference analysis device 300 for the above application will be described in detail below: In some embodiments, in order to more accurately find the differences between multiple versions of an application, the application version difference analysis device 300 may further include the following modules: The first search module is used to search for a preset folder in each program package before obtaining the difference information between multiple versions of the first application. The preset folder is a folder that exists in the Jar package of the first application but does not exist in the compressed Zip package. The second search module is used to search for preset files in preset folders whose filenames are preset filenames.

[0048] In some embodiments, in order to present the obtained difference information between multiple versions of the first application to relevant personnel in the form of an analysis report, the version difference analysis device 300 of the application may further include the following modules: The generation module is used to obtain the difference information between multiple versions of the first application, and then generate a difference analysis report of the program package for multiple versions of the first application based on the difference information and the analysis report template. The sending module is used to send the difference analysis report to the target object.

[0049] In some embodiments, to describe the application version difference analysis method provided in this application embodiment more comprehensively and in detail, the application version difference analysis device 300 may further include the following modules: The acquisition module 301 is used to acquire user permissions before displaying the difference information; The second display module 305 is used to display difference information corresponding to the user's permissions.

[0050] Therefore, by importing multiple versions of the application package into the user's application, multiple versions of the application package are obtained, and preset controls are displayed on the front-end interface. Users can compare preset files in each version of the application package by inputting the first input to the preset controls on the front-end interface. Thus, in this embodiment, users can import different versions of the application package to be compared through the front-end interface, and then compare versions of different applications by inputting the first input to the preset controls on the front-end interface, displaying the differences on the front-end interface. Therefore, the application version difference analysis method provided in this embodiment offers a more user-friendly human-computer interaction interface, enhancing the portability and interactivity of application version difference analysis.

[0051] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0052] The electronic device 400 may include a processor 401 and a memory 402 storing computer program instructions.

[0053] Specifically, the processor 401 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0054] Memory 402 may include mass storage for data or instructions. For example, and not limitingly, memory 402 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 402 may include removable or non-removable (or fixed) media. Where appropriate, memory 402 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 402 is non-volatile solid-state memory.

[0055] In a particular embodiment, memory 402 includes read-only memory (ROM). Where suitable, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these. Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. Thus, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.

[0056] The processor 401 reads and executes computer program instructions stored in the memory 402 to implement the version difference analysis method of any application in the above embodiments.

[0057] In some examples, electronic device 400 may also include communication interface 403 and bus 410. For example, Figure 4 As shown, the processor 401, memory 402, and communication interface 403 are connected through bus 410 and complete communication with each other.

[0058] The communication interface 403 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0059] Bus 410 includes hardware, software, or both, that couples components of an application version difference analysis device together. For example, and not as a limitation, bus 410 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 410 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0060] For example, the electronic device 400 can be a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc.

[0061] The electronic device 400 can execute the version difference analysis method of the application in the embodiments of this application, thereby achieving a combination Figure 1 and Figure 3 The described method and apparatus for version difference analysis of applications.

[0062] Furthermore, in conjunction with the application version difference analysis method in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when executed by a processor, these computer program instructions implement any of the application version difference analysis methods in the above embodiments. Examples of computer-readable storage media include non-transitory computer-readable storage media, such as portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, etc.

[0063] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0064] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0065] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0066] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0067] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope 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 protection scope of this application.

Claims

1. A method for analyzing version differences in an application, characterized in that, The method includes: When a front-end interface is displayed, in response to the user's import operation of multiple versions of the first application package, the multiple versions of the first application package are obtained; Preset controls are displayed on the front-end interface; Receive the user's first input to the preset control; In response to the first input, the differences between preset files in each version of the application package are compared to obtain the difference information between multiple versions of the first application. Display the difference information; The program package is a file JAR file. Before comparing the differences of preset files in different versions of the program package to obtain the difference information between multiple versions of the first application, the method further includes: Search for a preset folder in each program package. The preset folder is a folder that exists in the Jar package of the first application, but does not exist in the compressed Zip package. Locate the preset file with the preset file name in the preset folder, the preset file including the MANIFEST.MF file in the META-INF folder which is automatically created when the Jar package is generated; The preset file includes attribute information for at least one of the following attributes: Version identifier; Application-related properties; Mini Program related attributes; Extended identifier attributes; Package extended attributes; Signature-related attributes; Custom attributes.

2. The method according to claim 1, characterized in that, The display of the difference information includes: The differences are displayed in the form of data charts.

3. The method according to claim 1, characterized in that, After obtaining the difference information between multiple versions of the first application, the method further includes: Based on the difference information and analysis report template, generate a difference analysis report for multiple versions of the first application package; Send the difference analysis report to the target object.

4. The method according to claim 1, characterized in that, Before displaying the difference information, the method further includes: Obtain the user's permissions; The display of the difference information includes: Based on the user's permissions, display the difference information corresponding to the user's permissions.

5. A device for analyzing version differences of an application, characterized in that, The device includes: The acquisition module is used to acquire multiple versions of the application package in response to the user's import operation of multiple versions of the application package when a front-end interface is displayed. The first display module is used to display preset controls on the front-end interface; The receiving module is used to receive the user's first input to the preset control; The comparison module is used to respond to the first input by comparing the differences of preset files in different versions of the application package to obtain the difference information between multiple versions of the first application. The second display module is used to display the difference information; The device further includes a first search module and a second search module; The first search module is used to search for a preset folder in each program package before obtaining the difference information between multiple versions of the first application. The preset folder is a folder that exists in the Jar package of the first application but does not exist in the compressed Zip package. The second search module is used to search for a preset file with a preset file name from a preset folder. The preset file includes the MANIFEST.MF file in the META-INF folder, which is automatically created when the Jar package is generated. The preset file includes attribute information for at least one of the following attributes: Version identifier; Application-related properties; Mini Program related attributes; Extended identifier attributes; Package extended attributes; Signature-related attributes; Custom attributes.

6. An electronic device, characterized in that, The electronic device includes: A processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the steps of the application version difference analysis method as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the steps of the application version difference analysis method as described in any one of claims 1-4.

8. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the steps of the version difference analysis method for the application as described in any one of claims 1-4.

Images