> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/component-basics/simple-components/webview-component/troubleshooting-webview/webview-crashing-in-native-app.md).

# Webview crashing in Native App

In the event your Webview component is causing your native build to crash, it's likely related to the site you are attempting to load.

### Possible causes:

1. Website being loaded is attempting to access the Microphone permissions of the device.
   * Websites are not able to access anything that uses the Microphone of the device including the video camera. This is to prevent malicious apps from circumventing the permission system by just adding Webviews.
2. Website being loaded is an app not made in Adalo. 
   * This is not possible using the Webview Component and may cause the native app to crash.

### Resolution:

Remove any URL that matches the description above and push a new build. 

## **Still Need Help?**

If you're stuck, don't worry! Check out our [Adalo Community Forum](https://forum.adalo.com/) for tips and tricks from other makers who have successfully implemented the Webview Component.


---

# 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://help.adalo.com/component-basics/simple-components/webview-component/troubleshooting-webview/webview-crashing-in-native-app.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.