When the session has themjpegServerPort capability set, then the image will be loaded directly using the MJPEG stream. If themjpegServerPort is not configured, the system will fall back to using the screenshot API.
Suggested Solution
Using mjpegServerPort for image streaming is effective only when the inspector and device are on the same machine. In scenarios where users connect to a device on a remote Appium server, the image will not render due to an unreachable MJPEG stream URL. Additionally, any issues with the streaming server will prevent the image from loading.
To address this, we can offer a fallback mechanism, allowing users to choose between using the MJPEG stream or the screenshot API based on their requirements. This will enable users to utilize remote devices without interruptions.
Current Behavior
When the session has the
mjpegServerPort
capability set, then the image will be loaded directly using the MJPEG stream. If themjpegServerPort
is not configured, the system will fall back to using the screenshot API.Suggested Solution
Using mjpegServerPort for image streaming is effective only when the inspector and device are on the same machine. In scenarios where users connect to a device on a remote Appium server, the image will not render due to an unreachable MJPEG stream URL. Additionally, any issues with the streaming server will prevent the image from loading.
To address this, we can offer a fallback mechanism, allowing users to choose between using the MJPEG stream or the screenshot API based on their requirements. This will enable users to utilize remote devices without interruptions.
Additional Information
No response