> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/no-code-studio/reference/troubleshooting.md). # Troubleshooting Common problems, grouped by where you meet them. Each entry says what is usually behind it and how to fix it. ## Starting and authoring | Symptom | Usually means | Fix | | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The upload is refused before it starts | The file does not match the platform tab (`.apk` on Android, `.ipa` on iOS) | Switch tab, or pick the right build | | An iOS build stays at *processing* | Re-signing is slow or failed | Wait a couple of minutes; if it is still processing after several minutes, re-upload | | App Studio stops when you click **Start Testing** and mentions a platform mismatch | The selected app and the device are on different platforms | Clear the app and start anyway, or go back and pick a matching build | | A step cannot find its element | None of the recorded locators matched on this screen or device | See below | | A step is flagged with an amber **variable scope** badge | It uses a variable captured later, or outside its module | Move the capturing step earlier, or put the value in a data set or static variable. See [Modules](https://docs.mozark.ai/no-code-studio/authoring-tests/modules) | ### A step cannot find its element 1. Re-record the step on the current screen and compare the locators with the old one. 2. If the same text appears more than once, set **Match index** or narrow the **Search area**. See [Recording tests](https://docs.mozark.ai/no-code-studio/authoring-tests/recording-tests). 3. If the element only appears sometimes, wrap the step in a [Condition](https://docs.mozark.ai/no-code-studio/authoring-tests/conditions). 4. Check that the element is in the UI tree, with **Inspect → Elements** or **Page Source**. ## Running | Symptom | Usually means | Fix | | -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | **DID NOT RUN** several minutes after submitting | The Application was left on *Auto* and the test does not remember a build, so nothing was installed or launched | Re-run with the **Application** chosen explicitly. See [Running tests](https://docs.mozark.ai/no-code-studio/running-and-reporting/running-tests) | | Run rejected: *Some ${references} could not be resolved* | A variable, data-set column, element or module a step uses no longer exists | The unresolved names are listed under the form. Fix them and submit again | | You got more than one report from one submission | The selection spans several platforms or apps, so it was split into jobs | Expected: one job per platform and app | | A scheduled run produced no report | Scheduled runs do not open a report immediately | Check **Test Reports** after the scheduled time | ## Test data | Symptom | Cause | Fix | | ---------------------------------------------------------- | ------------------------------------------- | ------------------------------------------------------------- | | A step types nothing, or types the literal `${movie_name}` | No row matched this device | Check the serial in the key column matches the device exactly | | Every device types the same value | The data set is keyed on something constant | Key it on `device_serial` | | The picker will not let you insert | The data set has no key column | Open it and set one | | A number comparison behaves oddly | Numeric comparisons use whole numbers | Use integers, not decimals | ## Reports | Symptom | Fix | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- | | A whole **row** failed | It is a test problem. Open any cell in the row and find the first failed step | | A whole **column** failed | It is usually a device or build problem. Check the **Info** tab and the build you selected | | The later steps all failed | Only the first failure matters. Fix it and re-run | | No video or logs in the report | The capability was off when the session started. See [Reports](https://docs.mozark.ai/no-code-studio/running-and-reporting/reports) | ## Importing a script See the error and warning tables in [Importing an existing script](https://docs.mozark.ai/no-code-studio/authoring-tests/importing-an-existing-script). --- # 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.mozark.ai/no-code-studio/reference/troubleshooting.md?ask=&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.