We have an iOS 8 app on an iPhone 5S where our automated test script can perform 3 taps, and then the app hangs. If we test manually, the app behaves normally. The app hangs only when we use automated testing. When the app hangs, any taps (manual and automated) do not cause any response from the app or device. Pressing the home key returns us to the home screen, but this then leaves us unable to launch any other application. I tried looking into the issue by creating a quick test script using the Instruments Automation GUI, and I ran into the same issue: 3 taps and then a freeze.
If I terminate Appium or Instruments, the app is closed on the device, and the device’s behavior returns to normal (responds to taps, able to launch apps from home screen).
I am hoping someone has encountered this same issue and would like to offer some advice. Help is gladly appreciated.
I have exactly the same as yours, the app freezes after 3 or 4 tap actions even though I can run the app smoothly with Xcode.
I am glad that I am not the only one who got the issue
Does your app ask to be allowed to access the device location before it freezes, or does the app present any sort of pop-up at startup?
I did some more troubleshooting and I made a simple app with a simple test to see if I can get Appium running. The simple app and test ran fine, so I think the issue might either be with the app, Xcode and Instruments, or iOS 8.
Ah, that’s interesting. Our app presents a couple of pop-ups before freezing which we dismiss with taps. We make 2 other taps after tapping the pop-ups, which causes the app to hang.
Right now, we’re glad that we’re not the only ones with the problem.
@awang, I finally have a workaround for this issue, it turned out the app got frozen because the dev guy logged all the received json data. and somehow the app ran to racing condition with that logging. If I turn the log off then everything is ok.
I guess probably your app has faced the same issue too, here are steps that I made to figured it out:
Run the app until it get frozen, then open activity monitor to print the sample of the app process.
You can find the waiting thread in there, and track back to the code which called to that.
Try to disable that called function and try with the app again to see if it solves the problem.
Although I can have a workaround here but there are still 3 questions that I cannot answer:
Why the app run well with xcode?
Why the app run well with command line ( exactly the same command line as Appium)?
Why the app run well with ios 7.1 on Appium?
I’ll investigate this when I have time. Good luck
I just tested out what you said with a sample app by adding in a big log line. Amazingly, the app did freeze after adding in the giant log statement. We created a build of our actual app with the logging commented out, and we are very relieved to see automation running on it without the app freezing.
Thank you for your excellent analysis, @tbao! Definitely glad to have learned something new from you!
This is not all about 3-4 taps. We observed Appium(1.3.1) itself freezes after some hours of script run. So to stop/restart appium we had to force quit it (As Stop button goes unresponsive ). In last 3-4 attempts a complete test suite which was taking around 7 hours with iOS 6, now it is getting freeze just after 30-40% of tests run. Also 30-40% tests of the test suite is now consuming around 9 hours.
I tried that out with the sample application, and it seems that Appium gets slower and slower as it sends commands. I added in a counter to my test script, and it seems that Appium can send several hundred taps before its performance comes to a crawl. I would recommend posting this as a separate issue.
I still have the same issue that freeze my app at the beginning or after 2-3 clicks.
Appium 1.3.5
Robot Framework 2.8.6 (Python 2.7.6 on darwin)
IOS 8.1
@denny_home, did you try to take a look at the sample of the app process when it’s frozen?
There you can find the information of what process is blocking the app, and make some twist in the app’s source code to eliminate that blocking code.
@tbao, thanks for you comments. They are clear and handy. Could you give me some clues how to recognise which process is blocking my app? I’m analyzing my app process sample and looking some info in Call Graph section.
I’m having same issue with my 8.1 iOS sim. It’s very probably thats issue is also caused by loging json data
@stefan, I don’t think there is a general way to recognize if a thread is blocking, but this is what I did when looking into the Call Graph:
Track down each thread to the very bottom of the called tree. At the bottom is the function / method of “current” stage of the thread when the sample of the entire process is created.
If there is some function / method related to “wait” then it is possibly the cause of deadlock
Track up from that function / method until you can find where your code actually call it, and disable that call and retry again.
While automating our app, strangely few pages failed to load as the loader kept on running without displaying anything on page. @tbao Thanks to this post I was finally able to run my code on IOS8.
It was happening due to API NSlogs being printed. So I just commented the line out & app started working fine.
