> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/download/build-failure/android-build-failure.md).

# Android build failure

### Android build failure: Special characters in app name

If your app build is failing, your build is stuck, or your download is not completing during the Android build process, the issue may be caused by unsupported special characters in the app name.

Certain special characters can prevent the Android build pipeline from compiling the app successfully.

#### Why this build failure happens

1. Unsupported special characters in the app name
   * Symbols such as emojis or uncommon characters may not be supported
   * The build system may fail to process these characters
2. Encoding or formatting conflicts
   * Special characters can cause compilation errors
   * The Android build process may stop unexpectedly

#### How to fix this Android build failure

1. Review your app name
   * Go to your app dashboard
   * Navigate to the app settings section
   * Check the app name field
2. Remove special characters
   * Remove emojis
   * Remove decorative symbols
   * Keep only standard letters and numbers

{% hint style="warning" %}
Use only standard alphanumeric characters in the app name to avoid Android build failures.
{% endhint %}

3. Save the changes
   * Update the app name
   * Save your settings
4. Rebuild your app
   * Go to the [Download dashboard](https://app.appmysite.com/app/download)
   * Click Rebuild under the Android app card

Once the app name is updated to remove unsupported characters, the Android build should complete successfully.


---

# 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.appmysite.com/app/download/build-failure/android-build-failure.md?ask=<question>&goal=<user_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.