Back up and share Android emulator macros

A useful Android emulator macro is more than a list of taps. It can contain conditional paths, waits, reference images, detection regions, and actions refined over many test runs. If that work exists only on one Windows installation, moving to another computer or collaborating with someone else creates unnecessary rework.

EmuloAgent includes two separate cloud workflows for this situation: sync keeps your own macros available in your Sertta account, while sharing creates a one-time token so another person can add a copy to their account. This guide explains what each workflow does, what travels with a macro, and what still needs to be configured locally.

Cloud features require sign-in and an active subscription. During the free trial, you can create, edit, save, and test macros locally, but cloud upload, download, and sharing remain disabled.

Use cloud sync when the macro belongs to you and you want it available on another Windows installation signed in to the same account. The cloud copy keeps the macro flow and its packaged visual assets together.

Use sharing when another EmuloAgent user needs their own copy. The owner generates a token, sends it to the recipient, and the recipient redeems it inside the app. The received macro is added as a separate automation in the recipient’s account.

Neither workflow is a live collaborative editor. EmuloAgent does not merge two independently edited copies. On download, a macro that already exists locally is skipped rather than overwritten, which protects local work from an automatic replacement.

What is included in the cloud package

When EmuloAgent sends a macro to the cloud, it packages the flow, metadata, and visual assets used by its conditions and actions. Reference images therefore travel with the automation instead of leaving the recipient with an empty sequence.

The macro’s declared resolution also travels with the package. That matters because an image captured at one emulator resolution may not match the same interface rendered at another size. Before moving a macro, keep the source and destination emulator resolution consistent. The emulator preparation guide explains why fixed resolution and DPI improve visual automation reliability.

One sensitive item is intentionally excluded: saved virtual-keyboard passwords are removed before a macro leaves the computer. After restoring or receiving a macro that uses the virtual-keyboard action, register that password again for the destination profile.

How to keep your macros in the cloud

Start with a macro that already runs correctly on its local profile. If its detections still need tuning, use the image, color, and text detection guide before treating the cloud copy as your reusable version.

Then follow this workflow:

Sign in to EmuloAgent. Cloud operations are tied to your Sertta account.
Confirm that the subscription is active. Cloud upload and download are subscriber features, not trial features.
Open the macro and save your changes. For eligible subscribers, saving starts a background upload so the latest saved version is sent without blocking the editor.
Use “Upload to cloud” when you want an explicit upload. The action is available on the selected automation and confirms whether the transfer succeeded.
Wait for completion before closing the app or disconnecting the network. A cloud copy only helps after its upload finishes.

If a save happens while the same macro is already being uploaded, EmuloAgent queues a follow-up upload instead of running two competing transfers. A temporary network failure receives one background retry; authentication, subscription, quota, or version-conflict errors require user action.

How to restore macros on another Windows PC

On the destination computer, install EmuloAgent, sign in with the same Sertta account, and prepare the emulator connection. Then open Automations and choose Download from cloud.

EmuloAgent lists the macros in your account and downloads those that do not yet exist in the local vault. At the end, it reports how many were downloaded, skipped because they were already present, or failed.

After the download:

create or confirm the emulator profile that will run the automation;
keep the emulator resolution equal to the resolution used to capture the macro assets;
pin or assign the automation to the appropriate profile;
re-enter any virtual-keyboard password used by the flow;
run a short controlled test before starting a long routine.

This last test is important. The macro and images can travel, but emulator performance, installed app state, language, theme, and screen scale can still differ between computers.

Sharing begins from a macro you own. If it has not reached the cloud yet, upload it first. Then:

Select the automation and choose Share macro.
EmuloAgent generates a share token and displays it in a copyable field.
Send the token only to the intended recipient.
The recipient opens Redeem token, pastes the value, and confirms.
EmuloAgent downloads the package and adds the received automation to the recipient’s list.

Each token can be redeemed only once, and it stops working if the original cloud macro is removed. A recipient cannot redeem their own token, and a received macro cannot be reshared as though the recipient were its original owner.

A practical handoff checklist

Imagine that a QA analyst built a visual smoke routine for an Android app in BlueStacks. The flow waits for the home-screen image, opens a settings panel, checks a status color, and confirms a label through OCR.

Before sending it to a teammate, the analyst should:

run the complete flow once on the source profile;
record the emulator resolution and app language;
upload the latest saved version;
generate a fresh one-time share token;
tell the teammate which screen should be open at the start;
ask the teammate to use the same resolution and test one pass manually;
point out any virtual-keyboard password that must be registered locally.

That context prevents the most common handoff mistake: assuming that transferring the macro also reproduces the entire emulator environment.

Use the cloud without losing local control

Cloud sync reduces the risk of leaving a carefully tuned macro on a single Windows installation. One-time sharing makes a controlled handoff possible without sending loose flow files and image folders. Both work best when you preserve resolution, understand that existing local macros are not overwritten on download, and reconfigure sensitive values on the destination profile.

Download EmuloAgent from the Microsoft Store, build your automation locally, and use the cloud when you are ready to keep or share the tested version.