Skip to content

Common Issues Observed in Mobile App Automation

This is a documentation for most frequently observed issues while automating and executing test cases for any mobile apps. The solutions provided will be generic and depending on the specificity of the issue you are observing, the solution might differ.

‘Due to an unexpected and rare infrastructure error…’

  • Errors like these are usually the result of backend issues by Worksoft SaaS or one of the cloud providers. But another unlikely case is that there is a mismatch of app operating system and app environment. Different operating systems of the app will be uploaded to different environments. Please make sure that the testing context combinations correctly correspond to the app environment, i.e., testing contexts for Android app should be created for the Android environment and testing contexts for iOS app should be created for iOS environment. Should these issues persist for a long time, please reach out to Worksoft Support.

‘App closed in between the execution’

  • Unless the app has crashed, please check for any swipe commands and the provided co-ordinates around the instructions when the app closes. Different devices have elements placed at different co-ordinates due to differences in display resolutions.

‘Unable to install app…’


  • If you are trying to start an Appium session and experience this error, please try to upload your preferred version of the app in Worksoft SaaS storage.

‘Call to sendKeys failed’


  • You might notice such an exception when you are trying to enter text in Appium session. Chances are you are trying to enter text in a combination with iOS 15 or above configuration. This is a known issue from Appium.

Feedback and Knowledge Base