You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a newbie for Calabash community,
While executing the calabash tests on the emulator Nexus 5X API level 26, the emulator crashes probably because of an appearing pop-up from a different application with the following exception.
Failed to perform gesture. java.lang.SecurityException: Injecting to another application requires INJECT_EVENTS permission
I am also aware that this issue is created and closed before without a concrete solution/fix for that. May be community can help me out about the following questions
Could that pop-up be related to google play services/google play store or it is crashing because of sth else.
Any screenshot is available for this issue
The text was updated successfully, but these errors were encountered:
Hey @huseyinbarin, I know this is a late response... By default, Calabash cant interact with system elements or other apps. Hence you get that message when a pop-up unrelated to the main app running with Calabash receives an action. Very likely some integration with a google service. Now, we have enabled some changes that let you use uiautomator, that lets you interact with this type of element. So you should be able to handle such element if it were to appear, and tap on a dismiss button or whatever.
I wonder if such an element has a specific locator/text where Calabash can automatically close it, not sure how to make test automation always expect an unexpected google service popup 🤔
I am a newbie for Calabash community,
While executing the calabash tests on the emulator
Nexus 5X API level 26
, the emulator crashes probably because of an appearing pop-up from a different application with the following exception.Failed to perform gesture. java.lang.SecurityException: Injecting to another application requires INJECT_EVENTS permission
I am also aware that this issue is created and closed before without a concrete solution/fix for that. May be community can help me out about the following questions
The text was updated successfully, but these errors were encountered: