Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix proxy error for activate and terminate app #139

Merged
merged 2 commits into from
Feb 5, 2018

Conversation

KazuCocoa
Copy link
Member

Fix the following proxy error for terminate_app and activate_app

[HTTP] --> POST /wd/hub/session/c579c9fc-32cc-49b8-9dc5-3ad46c4fe80f/appium/device/terminate_app {"appId":"io.appium.android.apis"}
[W3C] Driver proxy active, passing request on via HTTP proxy
[debug] [JSONWP Proxy] Proxying [POST /wd/hub/session/c579c9fc-32cc-49b8-9dc5-3ad46c4fe80f/appium/device/terminate_app] to [POST http://localhost:8200/wd/hub/session/328f5c81-65c3-41dd-9c8b-ad819dbf29fc/appium/device/terminate_app] with body: {"appId":"io.appium.android.apis"}
[W3C] Encountered internal error running command: Error: Could not proxy. Proxy error: Could not proxy command to remote server. Original error: 404 - undefined
    at doJwpProxy$ (/Users/kazuaki/GitHub/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:404:13)
    at tryCatch (/Users/kazuaki/GitHub/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/Users/kazuaki/GitHub/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (/Users/kazuaki/GitHub/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21)
    at GeneratorFunctionPrototype.invoke (/Users/kazuaki/GitHub/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
    at <anonymous>
[HTTP] <-- POST /wd/hub/session/c579c9fc-32cc-49b8-9dc5-3ad46c4fe80f/appium/device/terminate_app 500 49 ms - 1315
[HTTP] --> POST /wd/hub/session/c579c9fc-32cc-49b8-9dc5-3ad46c4fe80f/appium/device/activate_app {"bundleId":"io.appium.android.apis"}
[W3C] Driver proxy active, passing request on via HTTP proxy
[debug] [JSONWP Proxy] Proxying [POST /wd/hub/session/c579c9fc-32cc-49b8-9dc5-3ad46c4fe80f/appium/device/activate_app] to [POST http://localhost:8200/wd/hub/session/328f5c81-65c3-41dd-9c8b-ad819dbf29fc/appium/device/activate_app] with body: {"bundleId":"io.appium.android.apis"}
[W3C] Encountered internal error running command: Error: Could not proxy. Proxy error: Could not proxy command to remote server. Original error: 404 - undefined
    at doJwpProxy$ (/Users/kazuaki/GitHub/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:404:13)
    at tryCatch (/Users/kazuaki/GitHub/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/Users/kazuaki/GitHub/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (/Users/kazuaki/GitHub/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21)
    at GeneratorFunctionPrototype.invoke (/Users/kazuaki/GitHub/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
    at <anonymous>
[HTTP] <-- POST /wd/hub/session/c579c9fc-32cc-49b8-9dc5-3ad46c4fe80f/appium/device/activate_app 500 15 ms - 1315
[HTTP] --> POST /wd/hub/session/c579c9fc-32cc-49b8-9dc5-3ad46c4fe80f/appium/device/app_installed {"bundleId":"io.appium.android.apis"}
[debug] [W3

appium/ruby_lib_core#58

@mykola-mokhnach
Copy link
Contributor

mykola-mokhnach commented Feb 5, 2018

There is also app_state endpoint.
Here's the whole list /~https://github.com/appium/appium-base-driver/blob/2933fe45ecead1283f13825c0e64e799bfabd2ba/lib/protocol/routes.js#L401

@KazuCocoa KazuCocoa merged commit 56d6ff8 into appium:master Feb 5, 2018
@KazuCocoa KazuCocoa deleted the fix-proxy-error branch February 5, 2018 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants