fleet

Files

T

Juan Fernandez e1512dacc9 Fix nil-pointer panic in Android Enterprise Pub/Sub endpoint (#45520 )

Fixes #45520 

The Pub/Sub status-report and enrollment handlers dereferenced
device.HardwareInfo before any nil check, so a payload from Google's
Android Management API with hardwareInfo omitted panicked the request
goroutine.

2026-05-18 13:29:45 -04:00

mock

…

service

Fix nil-pointer panic in Android Enterprise Pub/Sub endpoint (#45520 )

2026-05-18 13:29:45 -04:00

tests

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

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

android.go

…

arch_test.go

…

datastore.go

…

errors.go

…

onc_test.go

Android Wi-Fi profile withheld until cert installed on device (#42877 )

2026-04-07 16:26:09 -05:00

onc.go

Android Wi-Fi profile withheld until cert installed on device (#42877 )

2026-04-07 16:26:09 -05:00

pubsub.go

…

README.md

…

service.go

…

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.