> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/known-limitations-and-edge-cases.md). # Known Limitations and Edge Cases ## Known Limitations and Edge Cases Use this page to review current constraints and behaviors in this release. {% hint style="info" %} These items are known in the current release. They are expected to improve in future versions. Check release notes for updates. {% endhint %} ### Session and testing * **One Interact session at a time** The Optics AI **Interact** page supports only one active AI session per user. End the current session before starting another. * **Device availability reflects real hardware state** Devices appear as unavailable when they are powered off, unplugged, or experiencing a hardware fault. Controllers poll device reachability continuously. A device is marked unavailable only after three failed reachability samples to reduce false alarms from brief connectivity issues. * **Session redirect timing** After you click **Launch** on a Web, Mobile, or TV selection page, the portal redirects you to the live session runner. On slower connections, this can take a few seconds. Do not click **Launch** more than once. Repeating the action can allocate multiple sessions. * **Stream startup time** Interactive sessions can take two to eight seconds to initialize video streaming. During this window, the video panel can show a connecting state while the controller starts the streaming pipeline and establishes the session. * **Video processing delay** Session recordings are not available immediately after a session ends. Processing usually completes within one to three minutes. Refresh the Session Details page after that window to check for the video. * **Video recording length depends on controller storage** Long-running sessions depend on available disk space on the controller machine. The platform checks minimum free space before starting new sessions. If storage is too low, new session requests can be rejected. * **Search scope on the Sessions list** Plain text search and JQL search apply only to the currently loaded page of data. To search across a larger set, increase the page size to the maximum value before searching. * **TV session routing** TV sessions use a different infrastructure path than web and mobile sessions. If TV sessions fail to launch, the issue can be limited to TV device capacity rather than the wider platform. * **Smart TV interactions are key-based** TV sessions support key events such as D-pad, media keys, and number keys. Coordinate-based touch input does not apply to TV devices. Test flows and scripts should use key-event interactions. ### Automation and scheduling * **iOS app installation requires device-specific signing** IPA files must be signed for the target device UDID. An IPA signed for a different device will fail to install. Make sure provisioning profiles include the UDIDs for target devices. * **Browser session concurrency is limited per controller** Each controller machine supports a configurable maximum number of concurrent browser sessions. The default limit is typically four. Additional sessions wait in a queue until capacity is available. * **Scheduled tests are not exact to the second** Scheduled runs usually start within about `±60 seconds` of the configured time. Timing depends on the scheduler polling interval. If a device is busy at the scheduled start time, the test waits until the device becomes free, up to the configured wait timeout. ### File Management * **No multi-file upload** Upload files one at a time. Batch upload is not currently supported. * **Re-signing delay** Some file types require a server-side re-signing step after upload. During this time, the file status shows as `Re-signing`. This step can take up to five minutes. The file is not available for download until it completes. * **Permanent deletion** Deleted files cannot be recovered. There is no end-user recycle bin or soft-delete flow. ### UI and navigation * **Sidebar collapse resets on reload** Sidebar collapse state persists only for the current session. It resets on page reload. * **Desktop-first layout** The portal is designed for desktop screens, especially widths of `1280px` and above. Tablet landscape mode is usable, but session launch pages and Optics AI canvases work best on a full desktop display. * **Internet Explorer is not supported** The portal depends on modern browser APIs such as `WebSocket`, `BroadcastChannel`, `Canvas`, and `crypto.randomUUID`. These APIs are not available in Internet Explorer or legacy Edge. --- # 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://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/known-limitations-and-edge-cases.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.