> 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/mcp/mozark-mcp-docs/security-and-help/troubleshooting.md). # Troubleshooting Resolve connection, context, device, and test-run errors. ## "The assistant says it has no Mozark tools" * **The connector is off for this chat.** In Claude, open the tools menu next to the message box and toggle **Mozark** on, then ask again. * **Tools are loaded lazily.** Ask the assistant to search for the tool by name: *"Load the Mozark TCM tools."* * **Not authenticated.** Disconnect and reconnect the server in your client settings to trigger sign-in again. ## `missing_context` The tool needs an organisation, project or app that isn't set. The assistant should run discovery automatically and retry. If it doesn't, say *"Set my context to , , ."* ## `403 INVALID_APP_CONTEXT` or `APP_CONTEXT_MISMATCH` The active app doesn't belong to the active organisation/project—usually because your account-wide default app is in a different organisation. Ask the assistant to list apps in the current organisation and switch to the right one. ## Test cases were saved to the wrong project The context wasn't switched before saving. Move or delete them, then explicitly set the context (*"Switch to project X"*) before regenerating. The assistant is required to call the switch tool—if it only replied conversationally, ask it to confirm the active context. ## Optics: `Unable to resolve the launchable activity` / `Failed to launch: ` The app package was wrong. Don't retry on another device. Give the assistant the exact package or bundle ID, or ask it to open the app from the drawer and read the real package from the device. ## Optics: `No valid strategies found` Template-image matching isn't available in MCP-started sessions. Use text, XPath or AI fallback locators. ## Optics: step reported success but nothing changed on screen A `SUCCESS` keyword status only means the command ran. The assistant judges the real effect from the screenshot and will retry via the locator ladder. If you see this often, check whether the element is covered by a banner, permission prompt or login gate. ## Appium: `INSTALL_FAILED_*` The upload worked; the device rejected the build (version downgrade, ABI mismatch, user restriction). Try a different device or a compatible build—no need to re-upload. ## IPA won't install right after upload IPA files are re-signed after upload, which takes 1–3 minutes. Wait and retry. ## Session start says no free devices Ask for the full device list (`appium_list_devices`) to see which are busy, or try again shortly. Sessions left open hold devices—ask the assistant to stop any it started. ## Test run shows "Incomplete" Steps were left unmarked. Ask the assistant to set each remaining step's status and finish the test case in the run. ## Still stuck? Contact Mozark support with the tool name, the error text, and the approximate time. Never paste tokens or the curl upload command into a ticket—it contains a live credential. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mozark.ai/mcp/mozark-mcp-docs/security-and-help/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.