# AppCenter Generate App Crash

Generates an App Crash. Use this with care, since it will really make your App crash.

{% hint style="danger" %}
Don't forget to remove this call in production releases.
{% endhint %}

Action available for the following operating systems:

![](/files/-MGIiDGuNcrVFP-DbUma)

### Parameters

* **Crash Description** \<string> - The string to associated with the App Crash.
* **KClient Only**
  * If *Yes* , then this crash will only be executed while running with KClient.
  * If *No* , then this crash will always be executed, either with KClient or with your compiled App.

{% hint style="info" %}
This action is intended to be used while testing AppCenter integration with the Crashes module, so you can forcea crash for your App and check in AppCenter if the crash log was received.
{% endhint %}

{% hint style="info" %}
The Crash Description parameter was not being captured by iOS AppCenter SDK, but this can Change in thefuture.
{% endhint %}

{% hint style="info" %}
This action will also work in Win32 environments, although there is no AppCenter integration available for thisplatform.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-code-flow/appcenter-generate-app-crash.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.