Giter Site home page Giter Site logo

appium-altunity-plugin's People

Contributors

bipin-k avatar jlipps avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

appium-altunity-plugin's Issues

Not able to write text in textview

We are working on a game which contains textview. We are trying to append some text in that view. But we are getting error.

We are using below code to send text.

self.Driver.find_element('id', 'ConfigJSONKey').send_keys('TestWord')

But we are getting below error:
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] Calling AppiumDriver.findElement() with args: ["id","ConfigJSONKey","e562e43e-7385-465a-97fe-1ff5daedb79b"]
info Appium Plugins which can handle cmd 'findElement': altunity
info Appium Plugin altunity is now handling cmd 'findElement'
[Plugin [altunity]] Sending message 1658163661115 with command findObjects
[debug] [Plugin [altunity]] {"by":"ID","path":"//*[@id=ConfigJSONKey]","cameraBy":"NAME","cameraPath":"//","commandName":"findObjects","messageId":"1658163661115"}
[Plugin [altunity]] Received response for message 1658163661115
[debug] [Plugin [altunity]] {"messageId":"1658163661115","commandName":"findObjects","error":null,"data":"[{"name":"keyInput","id":2262,"x":540,"y":1236,"z":0,"mobileY":1104,"type":"","enabled":true,"worldX":540.0,"worldY":1236.0,"worldZ":0.0,"idCamera":2360,"transformParentId":2646,"transform...
info Appium Command 'findElement' was not handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command was handled by these: ["altunity"].
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] Responding to client with driver.findElement() result: {"ELEMENT":"unity-element-2262","element-6066-11e4-a52e-4f735466cecf":"unity-element-2262"}
info HTTP <-- POST /session/e562e43e-7385-465a-97fe-1ff5daedb79b/element 200 51 ms - 101
info HTTP
info HTTP --> POST /session/e562e43e-7385-465a-97fe-1ff5daedb79b/appium/element/unity-element-2262/replace_value
info HTTP {"id":"unity-element-2262","value":["adsd"]}
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] Calling AppiumDriver.replaceValue() with args: [["adsd"],"unity-element-2262","e562e43e-7385-465a-97fe-1ff5daedb79b"]
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] Matched '/element/unity-element-2262/value' to command name 'setValue'
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] Added 'value' property ["a","d","s","d"] to 'setValue' request body
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] Proxying [POST /element/unity-element-2262/value] to [POST http://127.0.0.1:8235/session/f6e86696-3573-44f7-9fac-064941c1d327/element/unity-element-2262/value] with body: {"elementId":"unity-element-2262","text":"adsd","replace":true,"value":["a","d","s","d"]}
[AndroidUiautomator2Driver@87d4 (e562e43e)] Got response with status 404: {"sessionId":"f6e86696-3573-44f7-9fac-064941c1d327","value":{"error":"no such element","message":"The element identified by 'unity-element-2262' is not present in the cache or has expired. Try to find it again","stacktrace":"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: The element identified by 'unity-element-2262' is not present in the cache or has expired. Try to find it again\n\tat io.appium.uiautomator2.model.ElementsCache.get(ElementsCache.java:160)\n\tat io.appium.uiautomator2.handler.SendKeysToElement.safeHandle(SendKeysToElement.java:104)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:59)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:267)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:261)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:68)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChann...
[debug] [W3C] Matched W3C error code 'no such element' to NoSuchElementError
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] Encountered internal error running command: io.appium.uiautomator2.common.exceptions.ElementNotFoundException: The element identified by 'unity-element-2262' is not present in the cache or has expired. Try to find it again
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.appium.uiautomator2.model.ElementsCache.get(ElementsCache.java:160)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.appium.uiautomator2.handler.SendKeysToElement.safeHandle(SendKeysToElement.java:104)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:59)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:267)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:261)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:68)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:345)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:345)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:435)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:250)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:345)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:266)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:345)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1294)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:911)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:611)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:552)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:466)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:438)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:140)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)] at java.lang.Thread.run(Thread.java:919)
[debug] [AndroidUiautomator2Driver@87d4 (e562e43e)]
info HTTP <-- POST /session/e562e43e-7385-465a-97fe-1ff5daedb79b/appium/element/unity-element-2262/replace_value 404 30 ms - 3934
info HTTP

Interactive with both Native and Unity contexts

Hi,
Can you share an example on switching between native and unity contexts and accessing a certain android view element?
We tried but unfortunately didn't find a way to find the methods when interacting with native android elements.
Where can we find the documentation for accessing the android native elements?

Thanks,
Ayyappa

iOS app not opening when integrating Unity app with AltUnityTester

Hi, I am trying to test the Unity Application on iOS device via appium + altUnity tester, but after integrating AltUnity Tester in the Unity Project, whenever I launch the app on the device it's just a black screen and the application closes after 5-6 seconds. This is happening both manually and via automation scripts.

Unable to use development plugins with flag `--use-plugins`

I made some changes into the plugin code and then followed the same instructions to uninstall the production version plugin and then run clean & build scripts and thereafter used the same version to restart appium server with the altunity plugin but the plugin isn't getting activated after that.

The version was changed to 1.3.3 from 1.3.2.

List Installed Plugins,

➜  appium-altunity-plugin git:(master) ✗ appium plugin list
✔ Listing available plugins
- [email protected] [installed (dev mode)]
- images [not installed]
- execute-driver [not installed]
- relaxed-caps [not installed]
- universal-xml [not installed]

Appium Logs when plugin is enabled with the provided flags,

➜  appium-altunity-plugin git:(master) ✗ appium --use-plugins=altunity
[Appium] Welcome to Appium v2.0.0 (REV 9600617c52d0d2e48493424c529ac6c945d2775b)
[Appium] Non-default server args:
[Appium] {
[Appium]   usePlugins: [
[Appium]     '[email protected]'
[Appium]   ]
[Appium] }
[Appium] Attempting to load driver uiautomator2...
[debug] [Appium] Requiring driver at /Users/bipinchaurasia/Documents/github/appium-altunity-plugin/node_modules/appium-uiautomator2-driver
[Appium] Appium REST http interface listener started on http://0.0.0.0:4723
[Appium] You can provide the following URLS in your client code to connect to this server:
[Appium] 	http://127.0.0.1:4723/ (only accessible from the same host)
[Appium] 	http://172.17.24.170:4723/
[Appium] 	http://192.0.2.1:4723/
[Appium] Available drivers:
[Appium]   - [email protected] (automationName 'UiAutomator2')
[Appium] Available plugins:
[Appium]   - [email protected]
[Appium] No plugins activated. Use the --use-plugins flag with names of plugins to activate

get_property('*') returning 500 "Object not found"

I've been trying to get get_property to work. Calling it from web_element_instance.get_property("propertyName").

For extra testing I have tried calling with parameters '*' and 'UnityEngine.Transform' to eliminate the possibility of misnaming the property I am trying to fetch (as these are the given examples on the docs).

All three cases return the same server errors. Yet, get_attribute works as expected while being called from the same web_element_instance.

Server Logs for the wildcard call:

 [HTTP] --> GET /session/f3b9e4ca-1c1a-4d00-9463-573f6ef64127/element/unity-element--1694/property/*
[HTTP] {}
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)] Would have proxied command directly, but a plugin exists which might require its value, so will let its value be collected internally and made part of plugin chain
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)] Calling AppiumDriver.getProperty() with args: ["*","unity-element--1694","f3b9e4ca-1c1a-4d00-9463-573f6ef64127"]
[AppiumDriver@0e70] Plugins which can handle cmd 'getProperty': altunity
[AppiumDriver@0e70] Plugin altunity is now handling cmd 'getProperty'
[Plugin [altunity]] Sending message 1689885383698 with command getAllComponents
[debug] [Plugin [altunity]] {"altUnityObjectId":"-1694","commandName":"getAllComponents","messageId":"1689885383698"}
[Plugin [altunity]] Received response for message 1689885383698
[debug] [Plugin [altunity]] {"messageId":"1689885383698","commandName":"getAllComponents","error":{"type":"notFound","message":"Object not found","trace":"  at Altom.AltTester.AltRunner.GetGameObject (System.Int32 objectId) [0x00000] in <00000000000000000000000000000000>:0 \n  at Altom.AltTester.Commands.AltGetAllComponents...
[AppiumDriver@0e70] Command 'getProperty' was *not* handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command *was* handled by these: ["altunity"].
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)] Encountered internal error running command: Error: Object not found
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AltUnityClient._sendCommand (C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\client\index.ts:163:23)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at processTicksAndRejections (node:internal/process/task_queues:95:5)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AltUnityClient.sendSimpleCommand (C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\client\index.ts:171:23)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AltUnityClient.getElementComponents (C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\client\commands\element.ts:10:17)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AltElement.getComponents (C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\client\alt-element.ts:81:16)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\commands\element.ts:97:31
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\commands\element.ts:40:16
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AltUnityPlugin.unityContextGuard (C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\index.ts:144:16)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AltUnityPlugin.unityElementGuard (C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\commands\element.ts:35:12)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AltUnityPlugin.getProperty (C:\Users\usr\.appium\node_modules\appium-altunity-plugin\src\commands\element.ts:89:12)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at C:\Users\usr\.nvm\versions\node\v19.2.0\bin\node_modules\appium\lib\appium.js:734:18
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AppiumDriver.executeWrappedCommand (C:\Users\usr\.nvm\versions\node\v19.2.0\bin\node_modules\appium\lib\appium.js:774:16)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at AppiumDriver.executeCommand (C:\Users\usr\.nvm\versions\node\v19.2.0\bin\node_modules\appium\lib\appium.js:696:17)
[debug] [AndroidUiautomator2Driver@5d5d (f3b9e4ca)]     at asyncHandler (C:\Users\usr\.nvm\versions\node\v19.2.0\bin\node_modules\appium\node_modules\@appium\base-driver\lib\protocol\protocol.js:393:19)
[HTTP] <-- GET /session/f3b9e4ca-1c1a-4d00-9463-573f6ef64127/element/unity-element--1694/property/* 500 81 ms - 697

Make AltUnityClient connect maxTries dynamic

Actually, the number of retries is hardcoded (equal to 15):

async connect() {
        let numTries = 0
        const maxTries = 15
        await retryInterval(maxTries, 1000, async () => {
            numTries++
            this.log.info(`Attempting to connect to AltUnity server. This is attempt ${numTries}/${maxTries}`)
            try {
                await this.conn.connect()
            } catch (err: any) {
                throw new Error(`Could not connect to the AltUnity server. Original error was: ${err.message}`)
            }
        })
        this.log.info(`Connection to AltUnity server established`)
    }

It might be very helpful to have it dynamic and pass using capability.

Unable to rotate screen in Android through alt unity

  1. We able to get orientation using orientation = self.driver.orientation
  2. Unable to rotate app >> self.driver.orientation = 'LANDSCAPE'
    Error facing >> selenium.common.exceptions.InvalidElementStateException: Message: Screen rotation cannot be changed to ROTATION_270 after 2000ms. Is it locked programmatically?
  3. Appium log has been attached

appium_rotate_log.txt

Error: There is no websocket connection active

Unable to execute driver.getPageSource() while setting the driver context to UNITY with Appium v2.0.0-beta.57 while running with plugins as, appium --use-plugins=altunity,relaxed-caps,element-wait --relaxed-security.

Also, I have forwarded the port to 13000 with adb command before running appium script as well,

➜  ~ adb forward --list
2ae9c69c tcp:13000 tcp:13000
2ae9c69c tcp:1300 tcp:1300

Following are the appium server logs,

[HTTP] --> POST /session/ef36be43-7f9d-48f4-9fdd-db08233b96ab/context
[HTTP] {"name":"UNITY"}
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)] Calling AppiumDriver.setContext() with args: ["UNITY","ef36be43-7f9d-48f4-9fdd-db08233b96ab"]
[AppiumDriver@1597] Plugins which can handle cmd 'setContext': altunity,element-wait
[AppiumDriver@1597] Plugin element-wait is now handling cmd 'setContext'
[AppiumDriver@1597] Plugin altunity is now handling cmd 'setContext'
[AppiumDriver@1597] Executing default handling behavior for command 'setContext'
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Running '/Users/bipinchaurasia/Library/Android/sdk/platform-tools/adb -P 5037 -s 2ae9c69c shell cat /proc/net/unix'
[debug] [AndroidDriver] Found no active devtools sockets
[debug] [AndroidDriver] Other sockets are: [
[debug] [AndroidDriver]   "0000000000000000: 00000002 00000000 00010000 0001 01 39713 @oiface",
[debug] [AndroidDriver]   "0000000000000000: 00000002 00000000 00010000 0001 01 19784 @time_genoff",
[debug] [AndroidDriver]   "0000000000000000: 00000002 00000000 00010000 0001 01 34752 @com.android.internal.os.WebViewZygoteInit/ce9d2907-2fad-4516-8e9d-f694c6825a25",
[debug] [AndroidDriver]   "0000000000000000: 00000002 00000000 00010000 0001 01 20371338 @Unity-com.mpl.androidapp",
[debug] [AndroidDriver]   "0000000000000000: 00000002 00000000 00010000 0001 01 24121 @THERMALE_UI",
[debug] [AndroidDriver]   "0000000000000000: 00000002 00000000 00010000 0005 01 26038 @jdwp-control",
[debug] [AndroidDriver]   "0000000000000000: 00000002 00000000 00010000 0001 01 20343569 @com.android.internal.os.AppZygoteInit/2153d0fc-9c69-49ad-a2d3-6fff96853d51",
[debug] [AndroidDriver]   "0000000000000000: 00000002 00000000 00000000 0002 01  2334 @gplisnr\u0000",
[debug] [AndroidDriver]   "0000000000000000: 00000003 00000000 00000000 0005 03 20342381 @jdwp-control",
[debug] [AndroidDriver]   "0000000000000000: 00000003 00000000 00000000 0001 03 20346462 @com.android.internal.os.AppZygoteInit/2153d0fc-9c69-49ad-a2d3-6fff96853d51",
[debug] [AndroidDriver]   "0000000000000000: 00000003 00000000 00000000 0001 03 35590 @com.android.internal.os.WebViewZygoteInit/ce9d2907-2fad-4516-8e9d-f694c6825a25",
[debug] [AndroidDriver]   "0000000000000000: 00000003 00000000 00000000 0005 03 19870990 @jdwp-control"
[debug] [AndroidDriver] ]
[debug] [AndroidDriver] Found 0 webviews: []
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)] Available contexts: ["NATIVE_APP"]
[Plugin [altunity]] Default behavior failed handling setContext, ignoring
[Plugin [altunity]] Original error: NoSuchContextError: No such context found.
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)] Responding to client with driver.setContext() result: null
[HTTP] <-- POST /session/ef36be43-7f9d-48f4-9fdd-db08233b96ab/context 200 76 ms - 14
[HTTP]

[HTTP] --> GET /session/ef36be43-7f9d-48f4-9fdd-db08233b96ab/context
[HTTP] {}
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)] Calling AppiumDriver.getCurrentContext() with args: ["ef36be43-7f9d-48f4-9fdd-db08233b96ab"]
[AppiumDriver@1597] Plugins which can handle cmd 'getCurrentContext': altunity,element-wait
[AppiumDriver@1597] Plugin element-wait is now handling cmd 'getCurrentContext'
[AppiumDriver@1597] Plugin altunity is now handling cmd 'getCurrentContext'
[AppiumDriver@1597] Command 'getCurrentContext' was *not* handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command *was* handled by these: ["altunity","element-wait"].
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)] Responding to client with driver.getCurrentContext() result: "UNITY"
[HTTP] <-- GET /session/ef36be43-7f9d-48f4-9fdd-db08233b96ab/context 200 2 ms - 17
[HTTP]
[HTTP] --> GET /session/ef36be43-7f9d-48f4-9fdd-db08233b96ab/source
[HTTP] {}
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)] Would have proxied command directly, but a plugin exists which might require its value, so will let its value be collected internally and made part of plugin chain
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)] Calling AppiumDriver.getPageSource() with args: ["ef36be43-7f9d-48f4-9fdd-db08233b96ab"]
[AppiumDriver@1597] Plugins which can handle cmd 'getPageSource': altunity,element-wait
[AppiumDriver@1597] Plugin element-wait is now handling cmd 'getPageSource'
[AppiumDriver@1597] Plugin altunity is now handling cmd 'getPageSource'
[Plugin [altunity]] Sending message 1679294925232 with command findObjects
[debug] [Plugin [altunity]] {"by":"PATH","path":"//*","cameraBy":"NAME","cameraPath":"//","enabled":true,"commandName":"findObjects","messageId":"1679294925232"}
[AppiumDriver@1597] Command 'getPageSource' was *not* handled by the following behaviours or plugins, even though they were registered to handle it: ["default"]. The command *was* handled by these: ["altunity","element-wait"].
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)] Encountered internal error running command: Error: There is no websocket connection active
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at /Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/client/connection.ts:223:27
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at new Promise (<anonymous>)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at Connection.sendMessage (/Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/client/connection.ts:220:22)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at AltUnityClient._sendCommand (/Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/client/index.ts:159:43)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at AltUnityClient.sendSimpleCommand (/Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/client/index.ts:171:34)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at AltUnityClient.findObjects (/Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/client/commands/find.ts:21:28)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at AltUnityClient.findAllObjects (/Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/client/commands/find.ts:32:23)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at /Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/commands/source.ts:39:42
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at AltUnityPlugin.unityContextGuard (/Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/index.ts:144:22)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at AltUnityPlugin.getPageSource (/Users/bipinchaurasia/node_modules/appium-altunity-plugin/src/commands/source.ts:38:23)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at /Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/lib/appium.js:735:35
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at WaitCommandPlugin.<anonymous> (/Users/bipinchaurasia/node_modules/appium-wait-plugin/lib/plugin.js:48:26)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at Generator.next (<anonymous>)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at /Users/bipinchaurasia/node_modules/appium-wait-plugin/lib/plugin.js:8:71
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at new Promise (<anonymous>)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at __awaiter (/Users/bipinchaurasia/node_modules/appium-wait-plugin/lib/plugin.js:4:12)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at WaitCommandPlugin.handle (/Users/bipinchaurasia/node_modules/appium-wait-plugin/lib/plugin.js:41:16)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at /Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/lib/appium.js:738:29
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at AppiumDriver.executeWrappedCommand (/Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/lib/appium.js:775:22)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at AppiumDriver.executeCommand (/Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/lib/appium.js:697:28)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at asyncHandler (/Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:387:32)

[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at /Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:503:15
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at Layer.handle [as handle_request] (/Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at next (/Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/node_modules/express/lib/router/route.js:144:13)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at Route.dispatch (/Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/node_modules/express/lib/router/route.js:114:3)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at Layer.handle [as handle_request] (/Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5)
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at /Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/node_modules/express/lib/router/index.js:284:15
[debug] [AndroidUiautomator2Driver@a4d7 (ef36be43)]     at param (/Users/bipinchaurasia/.nvm/versions/node/v16.15.0/lib/node_modules/appium/node_modules/express/lib/router/index.js:365:14)
[HTTP] <-- GET /session/ef36be43-7f9d-48f4-9fdd-db08233b96ab/source 500 31 ms - 767

What could be the issue with the appium script?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.