application requires INJECT_EVENTS permission

Mobile Testing, Android App Testing.
grekha
Posts: 7
Joined: Fri Jun 12, 2020 1:10 am

application requires INJECT_EVENTS permission

Post by grekha » Tue Jun 23, 2020 9:12 pm

Hi,

Ranorex isn't identifying the enter button of the app i'm testing and when running the scripts i see the error the following error.

Injecting to another application requires INJECT_EVENTS permission


Ranorex.Plugin.Mobile.XmlRpc.XmlRpcProtocolChannel.Call(MethodCall mc, TimeSpan responseTimeout)at Ranorex.Plugin.Mobile.Device.Channels.AppLogicChannel.Touch(String loc, Int32 elementIdentifier, Boolean isLongClick, Int32 duration)at Ranorex.Plugin.Mobile.Device.Channels.AppLogicChannel.Touch(IElementWithId element, TouchEvent evt)at Ranorex.Plugin.Mobile.RxIntegration.Elements.MobileFlavorElement.Touch(TouchEvent evt)at Ranorex.Touch.Tap(Element element, Int32 pointer, Location location, Duration touchDuration)at Ranorex.Adapter.Touch()at latest_solution.nextlogin.Ranorex.Core.Testing.ITestModule.Run() in c:\Users\reeee.re\Documents\Ranorex\RanorexStudio Projects\latest solution\latest solution\Login_again.cs:line 115at Ranorex.Core.Testing.TestModuleLeaf.RunInternal(DataContext parentDataContext, Int32 iteration, Int32 iterationCount, Boolean skipIteration)

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 6190
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: application requires INJECT_EVENTS permission

Post by odklizec » Wed Jun 24, 2020 7:39 am

Hi,

Could you please tell us more about the tested app and what exactly you are trying to do? Ideally, post also the snapshot of the problematic element.

Also, I think you should see this post:
https://www.ranorex.com/forum/viewtopic ... NTS#p35252

Basically, if the element you are trying to access is a part of system process or another (non-instrumented) app, you can see this error. And there is unfortunately nothing you or Ranorex can do about this.
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration