Granted Patent B2

US 12,693,934 · App. 18/568,509 · Granted Jul 28, 2026

Inventors: Jakob Schneider (London, GB); Martin David Churchill (London, GB); Lidia Gaymond (London, GB)

Assignee: Google LLC

G06F11/1415G06F11/3612G06F2201/865

Abstract

Claims (54)

1 . A method comprising:

receiving, by one or more processors of a server computing device hosting distribution of a plurality of applications, a faulty application indication identifying a faulty application of the plurality of applications, the faulty application having an issue that occurs during execution of the faulty application by a user computing device;

in response to receiving the faulty application indication, automatically generating, by one or more processors of the server computing device and based on the faulty application indication, a dedicated recovery module that extends functionality of the faulty application without modifying existing code of the faulty application, wherein generating the dedicated recovery module comprises:

selecting, based on the faulty application indication, a template code that targets the issue that occurs during execution of the faulty application by a user computer computing device;

populating the selected template code to obtain populated template code configured to resolve the issue; and

compiling the populated template code to generate the dedicated recovery module, wherein the dedicated recovery module is a sub-package separate from the faulty application, is generated to target the faulty application, and compiles separately from the faulty application;

linking the dedicated recovery module to the faulty application by at least modifying, by the one or more processors, a manifest file associated with the faulty application with instructions to add the dedicated recovery module as a sub-package, wherein the manifest file lists a plurality of sub-packages associated with the faulty application and causes the dedicated recovery module to be executed before any other sub-package in the plurality sub-packages associated with the faulty application; and

sending, by the one or more processors and to the user computing device, the manifest file, wherein the manifest file is configured to cause the user computing device, upon initiation of execution of the faulty application, to:

determine that the dedicated recovery module has been linked to the faulty application and is to be executed first before any other sub-packages associated with the faulty application based on the manifest file;

retrieve the dedicated recovery module; and

execute the dedicated recovery module to resolve the issue that occurs during execution of the faulty application.

2 . The method of claim 1 ,

wherein the faulty application indication identifies a name and a version associated with the faulty application, and

wherein generating the dedicated recovery module comprises generating the dedicated recovery module to target the faulty application identified by the name and the version associated with the faulty application.

3 . The method of claim 1 , wherein the dedicated recovery module is configured to delete or edit a file installed by the faulty application.

4 . The method of claim 1 , wherein the dedicated recovery module is configured to delete or edit a cache associated with the faulty application.

5 . The method of claim 1 , wherein the dedicated recovery module is configured to delete or edit a database associated with the faulty application.

6 . The method of claim 1 , wherein the dedicated recovery module is configured to delete or edit an experimental parameter associated with the faulty application.

7 . The method of claim 1 , wherein the dedicated recovery module is configured to prompt an update to the faulty application.

8 . The method of claim 1 , wherein receiving a faulty application indication comprises:

presenting a user interface configured to prompt a developer of the faulty application to enter the faulty application indication; and

receiving, via the user interface, the faulty application indication.

9 . The method of claim 1 ,

wherein the faulty application indication includes an issue indication that identifies the issue experienced during execution of the faulty application by the user computing device.

10 . The method of claim 1 , wherein the issue occurring during execution of the faulty application by the user computing device includes a failure to execute the faulty application in a manner that enables user interaction with the faulty application.

11 . A server computing device comprising:

a memory configured to store a faulty application indication identifying a faulty application of a plurality of applications hosted for distribution by the server computing device, the faulty application having an issue occurring during execution of the faulty application by a user computing device; and

one or more processors configured to:

in response to receiving the faulty application indication, automatically generate, based on the faulty application indication, a dedicated recovery module that extends functionality of the faulty application without modifying existing code of the faulty application, wherein the dedicated recovery module is a sub-package separate from the faulty application, is generated to target the faulty application, and compiles separately from the faulty application wherein, to generate the dedicated recovery module, the one or more processors are configured to:

select, based on the faulty application indication, a template code that targets the issue that occurs during execution of the faulty application by a user computer computing device;

populate the selected template code to obtain populated template code configured to resolve the issue; and

compile the populated template code to generate the dedicated recovery module

link the dedicated recovery module to the faulty application by at least modifying a manifest file associated with the faulty application with instructions to add the dedicated recovery module as a sub-package, wherein the manifest file causes the dedicated recovery module to be executed before any other sub-package associated with the faulty application; and

send to the user computing device, the manifest file, wherein the manifest file is configured to cause the user computing device, upon initiation of execution of the faulty application, to:

determine that the dedicated recovery module has been linked to the faulty application and is to be executed first before any other sub-packages associated with the faulty application based on the manifest file;

retrieve the dedicated recovery module; and

execute the dedicated recovery module to resolve the issue occurring during execution of the faulty application.

12 . The server computing device of claim 11 ,

wherein the faulty application indication identifies a name and a version associated with the faulty application, and

wherein the one or more processors are, when configured to generate the dedicated recovery module, configured to generate the dedicated recovery module to target the faulty application identified by the name and the version associated with the faulty application.

13 . The server computing device of claim 11 , wherein the dedicated recovery module is configured to delete or edit a file installed by the faulty application.

14 . The server computing device of claim 11 , wherein the dedicated recovery module is configured to delete or edit a cache associated with the faulty application.

15 . The server computing device of claim 11 , wherein the dedicated recovery module is configured to perform one or more of delete or edit a database associated with the faulty application, and delete or edit an experimental parameter associated with the faulty application.

16 . A non-transitory computer-readable storage medium having instructions stored thereon that, when executed, cause one or more processors of a server computing device to:

receive a faulty application indication identifying a faulty application of a plurality of applications hosted for distribution by the server computing device, the faulty application having an issue occurring during execution of the faulty application by a user computing device;

in response to receiving the faulty application indication, automatically generate, based on the faulty application indication, a dedicated recovery module that extends functionality of the faulty application without modifying existing code of the faulty application, wherein the dedicated recovery module is a sub-package separate from the faulty application, is generated to target the faulty application, and compiles separately from the faulty application, wherein, to generate the dedicated recovery module, the one or more processors are configured to:

select, based on the faulty application indication, a template code that targets the issue that occurs during execution of the faulty application by a user computer computing device;

populate the selected template code to obtain populated template code configured to resolve the issue; and

compile the populated template code to generate the dedicated recovery module;

link the dedicated recovery module to the faulty application by at least modifying a manifest file associated with the faulty application with instructions to add the dedicated recovery module as a sub-package, wherein the manifest file causes the dedicated recovery module to be executed before any other sub-package associated with the faulty application; and

send to the user computing device, the manifest file, wherein the manifest file is configured to cause the user computing device, upon initiation of execution of the faulty application, to:

determine that the dedicated recovery module has been linked to the faulty application and is to be executed first before any other sub-packages associated with the faulty application based on the manifest file;

retrieve the dedicated recovery module; and

execute the dedicated recovery module to resolve the issue occurring during execution of the faulty application.

Assignments (1)

Continuity (1)

References Cited (116)