> For the complete documentation index, see [llms.txt](https://docs.cubilock.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubilock.com/faq/frequently-asked-questions/how-to-fix-app-visibility-issues.md).

# How to fix app visibility issues?

Sometimes due to poor internet connection or any unforeseen situation, the device fails to communicate with the server results in un-synced changes. This guide will help you identify those issues and provide some solution(s) to fix them. These are as follows:

### Troubleshooting Steps:

1. Click on the **Settings** icon at the top right corner of your Android device to open kiosk settings

2. Choose **Exit Profile,** this will open up a dialog and ask for exit pass code

3. Enter the exit pass code and press **Exit.** This will take you to the launcher screen where you will be able to see some more apps for debugging (Settings, Play Store, Chrome)

4. Open Play Store and find your app in the list or search your app by typing in its name in the search bar. 

5. Follow these steps if you are unable to find your app

   1. Click on the settings icon at the top right corner of your Android device to open kiosk settings 
   2. Choose **Google's Device Policy,** this will take you to the details screen
   3. Click on the **Sync** icon, the device will sync all the changes with the CubiLock console
   4. Open Play Store to see if the app starts downloading

6. Follow these steps if you find your app but its not visible on launcher
   1. Click on the settings icon at the top right corner of your Android device to open kiosk settings 
   2. Choose **Clear Profile Data,** this will clear the profile data and take you to welcome screen
   3. Click on the Lets Go, the device will sync its changes and take you to launcher screen


---

# 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.cubilock.com/faq/frequently-asked-questions/how-to-fix-app-visibility-issues.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.