Timeouts
Timeouts for Flutter integration test cases in the running state on BrowserStack may occur due to either idle timeout or reaching the session limit.
Idle timeout
To prevent tests from running excessively in case of issues, BrowserStack imposes limits on how long a test can remain idle or how long the app can wait for a test to send a new command.
The default setting for the idleTimeout parameter is 900 seconds, but you can customize this limit according to your needs.
To specify the custom idle timeout value (whose value is in seconds), pass the idleTimeout parameter in the REST API request and start the Flutter integration test execution.
Example cURL request :
Session limit reached
The maximum duration allowed for session execution on BrowserStack is 2 hours. If this time limit is exceeded, the session execution will be halted, and the session status on the dashboard will be changed to TIMED OUT. If you have any queries, get in touch with us.
Related topics
-
Manage your uploaded test package using our REST API.
-
Use the list test package API endpoint to list your recently uploaded test package.
-
Delete your uploaded test package using the delete test package API endpoint.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!