> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/device-applications/wear-launcher/release-notes.md).
# Release Notes
### Release 1.2.13
Released Jun 2026
#### Highlights
This release includes updates to improve battery life and responsiveness of the application, additional scanner button configurations, and improved error toasts when the login fails or times out.
#### Details
* Reduced number of calls to Zebra MX functions to occur only on boot and on logout.
* Added a listener for L2 button press to activate scanner.
* Increased logging-in timeout from 30 seconds to 120 seconds.
### Release 1.2.10
Released March 2026
#### Highlights
Initial release of the BlueFletch Wear Launcher. Fully implemented the Zebra's Workcloud Sync sign-in flow from signing into a tablet such as a CC610, scanning the sign-in QR code, and logging into both the Wear Launcher and Sync.
#### Details
* Implemented a launcher that is specific to wearables whose purpose is to broker the authentication flow with Workcloud Sync.
* Implemented Config Watcher similar to BF Launcher, which watches for a launcher.json file to get the necessary org info, urls, MQTT servers, Sync client info, and more.
* Added QR Scan Screen when in open zone, which displays while waiting for user to scan the QR code on the host device.
* Added authenticated view, which shows configured apps while logged-in.
* Implemented logic to get necessary information from the QR code to authenticate with both the Wear Launcher and Workcloud Sync.
* Added logic to sign out of Workcloud Sync when the user logs out of launcher.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/device-applications/wear-launcher/release-notes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.