> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/mobile/android/older/android-version-14.1.2.md).

# Android Version 14.1.2

## Enhancements & Benefits <a href="#enhancements-and-benefits" id="enhancements-and-benefits"></a>

* ​Support for Dolphin web browser in KeeperFill
* Improved handling of password masking enforcement policy
* Upgrade to latest SQLite 3.26.0.

## Known Limitations <a href="#known-limitations" id="known-limitations"></a>

* ​Enforcement policies for Admin Console v13.1 are not yet fully supported.

## Bug Fixes <a href="#bug-fixes" id="bug-fixes"></a>

* ​Ensure that masked passwords can only be filled into password fields
* "Object does not exist" error message with deleted records that don't sync
* Small UI design fixes on Version History screen

## Coming Soon <a href="#coming-soon" id="coming-soon"></a>

* Android Release 14.1.3 is a bug fix release
* Android Release 14.2.0 is a feature release with Admin Console v13.1 enforcement support


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/mobile/android/older/android-version-14.1.2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.