fleet

Files

T

Victor Lyuboslavsky fa7d928235 Remove unenroll pending and add Android COBO wipe to Free (#46653 )

<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** Resolves #41683 

Unenroll/wipe Android on Fleet Free:
https://www.youtube.com/watch?v=JvsD3WBcDgE

# Checklist for submitter

- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.

## Testing

- [x] Added/updated automated tests
- [x] QA'd all new/changed functionality manually


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Android Lock, Wipe, and Clear passcode commands supported; Lock and
Clear for both personal (BYO) and company-owned (COBO) devices, Wipe for
COBO only.
  * Android COBO Wipe exposed in Fleet Free (UI and API).

* **Bug Fixes**
* Personal Android unenroll now removes only the work profile (personal
data preserved) and no longer shows a transient “wiping” status in the
UI.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-06-02 18:59:13 -05:00

mock

Android commands backend (#46031 )

2026-05-26 12:16:03 -05:00

service

Remove unenroll pending and add Android COBO wipe to Free (#46653 )

2026-06-02 18:59:13 -05:00

tests

Move mysql/testing_utils.go to a separate mysql/mysqltest package (#45406 )

2026-05-14 11:18:20 -03:00

android.go

Android commands backend (#46031 )

2026-05-26 12:16:03 -05:00

arch_test.go

…

datastore.go

…

errors.go

…

onc_test.go

…

onc.go

…

pubsub.go

…

README.md

…

service.go

Android commands backend (#46031 )

2026-05-26 12:16:03 -05:00

README.md

The MDM Android package attempts to decouple Android-specific service and datastore implementations from the core Fleet server code.

Any tightly coupled code that needs both the core Fleet server and the Android-specific features must live in the main server/fleet, server/service, and server/datastore packages. Typical example are MySQL queries. Any code that implements Android-specific functionality should live in the server/mdm/android package. For example, the common code from server/datastore package can call the android datastore methods as needed.

This decoupled approach attempts to achieve the following goals:

Easier to understand and find Android-specific code.
Easier to fix Android-specific bugs and add new features.
Easier to maintain Android-specific feature branches.
Faster Android-specific tests, including ability to run all tests in parallel.