Reviewed on: 2021-10-01
session_manager is the component that runs and manages session components.
Add the session_manager component to builds by including --with-base //src/session/bin/session_manager in the fx set invocation followed by rebuilding and re-paving the device.
Product configurations built on Session Framework (such as fx set workstation_eng.x64) include //src/session/bin/session_manager by default.
session_manager is launched in one of two ways: manually or automatically on system boot.
In general, running manually is useful during development, while running on boot is desirable for a production configuration.
Use the ffx session tool to launch a specific session:
ffx session launch fuchsia-pkg://fuchsia.com/your_session#meta/your_session.cm
session_manager attempts to launch a session on boot based on the contents of its product.session.url configuration parameter.
To boot into a session, include session_manager and the session component in the base package set and assign the URL of the session component to the product configuration, update your //local/BUILD.gn file to use the assembly_developer_overrides template:
Then include the new build target in your fx set:
fx set minimal.x64 --assembly-override=//local:<var>custom_session</var>
Re-build and ota, and the device will boot into session_manager and autolaunch your session.
If your development device runs a product that specifies product.session.url, you may nonetheless want to stop the session from launching (e.g., to avoid log spam from the session, or make changes to the device's state before the session launches).
You can disable autolaunching by updating your //local/BUILD.gn accordingly:
Unit tests for session_manager are included in the session_manager_tests package, and integration tests are included in the session_manager_integration_tests package.
Both can be included in your build by adding --with //src/session:tests to your fx set.
fx test session_manager_tests fx test session_manager_integration_tests
The entry point for session_manager is in src/main.rs with implementation details in other files within src/.
Unit tests are co-located with the code, while integration tests are in //src/session/tests.