> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/gangs/cuxial-gang-app/troubleshooting.md).

# Troubleshooting

Common Cuxial Gang App problems, with their cause and fix.

The most frequent problems after installing Cuxial Gang App, with the cause and the fix for each one.

<details>

<summary>The resource does not start</summary>

**Cause.** A dependency is missing or starts later than the app. Cuxial Gang App needs `ox_lib`, `oxmysql`, `qbx_core`, `lb-phone` and `cuxial_gang`.

**Fix.** Start the dependencies first:

{% code title="server.cfg" %}

```cfg
ensure ox_lib
ensure oxmysql
ensure qbx_core
ensure lb-phone
ensure cuxial_gang
ensure cuxial_gang_app
```

{% endcode %}

</details>

<details>

<summary>The app is not on the phone</summary>

**Cause.** One of these:

* `DefaultApp` is `false`, so the app waits in the phone's app store.
* lb-phone rejected the app. The client console (F8) shows `AddCustomApp failed` with the reason.

**Fix.** Install it from the app store of the phone, or set `DefaultApp = true` in `shared/config.lua`. If the console shows the error, the reason given by lb-phone is printed next to it.

</details>

<details>

<summary>The app opens blank</summary>

**Cause.** The interface is not loading. The folder `ui/dist` is missing or incomplete, usually after a partial upload.

**Fix.** Make sure `ui/dist/index.html` and the folder `ui/dist/assets` exist inside the resource. If they do not, copy the resource again from the original package and restart the server.

</details>

<details>

<summary>A gang member does not see "Mi Banda"</summary>

**Cause.** The app could not get the role from Cuxial Gang and fell back to the screen of a player without organization. Cuxial Gang is stopped, failed to start, or the character is an active mule, which takes priority over membership.

**Fix.** Check that `cuxial_gang` starts without errors and before `cuxial_gang_app`.

</details>

<details>

<summary>Gang notifications or chat messages do not reach the phone</summary>

**Cause.** `Identifier` was changed in `shared/config.lua`. Cuxial Gang sends them to the app `cuxial-gang`.

**Fix.** Set `Identifier = "cuxial-gang"` again and restart the resource.

</details>

<details>

<summary>The booking is rejected for lack of money</summary>

**Cause.** The full price is charged up front from `PaymentAccount`, which is `'cash'` by default. With `DirtyPayout = true` the app charges the `black_money` item through `ox_inventory` instead.

**Fix.** Set `PaymentAccount` to the account you want. With `DirtyPayout = true`, make sure `ox_inventory` is running and the `black_money` item exists.

</details>

<details>

<summary>The companion does not get into the vehicle</summary>

**Cause.** All of these must be true at once:

* The player is the driver.
* The vehicle is closer than `MaxDistance` and slower than `MaxVehicleSpeed`.
* The front passenger seat is free.
* The vehicle class is not in `BlackListedVehicleClasses` and the model is not in `BlackListedVehicles`.
* The horn is held for `HornHoldTime` milliseconds.

**Fix.** Stop next to her in a car with a free passenger seat and hold the horn. An on-screen hint warns when the vehicle is not valid or the seat is taken.

</details>

<details>

<summary>The companion leaves before the services start</summary>

**Cause.** After the pickup the player has `FindAreaTimeout` (two minutes by default) to stop at least `MinSecludedDistance` metres away, in a place where no other ped within 75 metres can see the vehicle. She also leaves if the player gets out of the vehicle.

**Fix.** Drive to an empty spot and stop. To make it easier, raise `FindAreaTimeout` or lower `MinSecludedDistance` in `data/kokka.lua`.

</details>

<details>

<summary>The companion does not appear at the meeting point</summary>

**Cause.** The `zone` of the profile has no entry in `MeetPoints`, or `pedModel` is not a valid model.

**Fix.** Review that profile in `data/kokka.lua`. Each `zone` must match a key of `MeetPoints` exactly.

</details>

<details>

<summary>A profile added to data/kokka.lua does not show in the app</summary>

**Cause.** The list of profiles the player sees is part of the interface. `Escorts` only sets the model, zone, tier and services of the profiles that already exist.

**Fix.** Edit the existing entries instead of adding new keys.

</details>

<details>

<summary>/kokkaduo answers that there is no permission, or nothing happens</summary>

**Cause.** The command is restricted to `group.admin`. If it runs but no animation plays, one of the two players is not in their seat: the client drives and the escort sits in the front passenger seat of the same vehicle.

**Fix.** Add the staff member to `group.admin` in `server.cfg` and seat both players before running the command.

</details>

<details>

<summary>Sharing a location with a contact does nothing</summary>

**Cause.** The app sends the player's GPS waypoint, and there is none set.

**Fix.** Place a waypoint on the map first.

</details>


---

# 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.cuxial.com/scripts/gangs/cuxial-gang-app/troubleshooting.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.
