Can't launch Appium from cmd
I use appium-desktop-setup-1.8.2.
On Windows I start it from the console with such options:
appium
appium -p 4724
start appium
But I only have the Appium launch window open. Appium doesn't start automatically. It have to run it manually.
What am I doing wrong?
I don't understand this response:
C:Program Files (x86)Appium>appium -U 0b36774b032fbdba -p 4724
C:Program Files (x86)Appium>
Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://github.com/facebook/prop-types#prop-types
Warning: Accessing createClass via the main React package is deprecated, and will be removed in React v16.0. Use a plain JavaScript class instead. If you're not yet ready to migrate, create-react-class v15.* is available on npm as a temporary, drop-in replacement. For more info see https://github.com/facebook/prop-types#prop-types
(node:10212) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
appium
add a comment |
I use appium-desktop-setup-1.8.2.
On Windows I start it from the console with such options:
appium
appium -p 4724
start appium
But I only have the Appium launch window open. Appium doesn't start automatically. It have to run it manually.
What am I doing wrong?
I don't understand this response:
C:Program Files (x86)Appium>appium -U 0b36774b032fbdba -p 4724
C:Program Files (x86)Appium>
Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://github.com/facebook/prop-types#prop-types
Warning: Accessing createClass via the main React package is deprecated, and will be removed in React v16.0. Use a plain JavaScript class instead. If you're not yet ready to migrate, create-react-class v15.* is available on npm as a temporary, drop-in replacement. For more info see https://github.com/facebook/prop-types#prop-types
(node:10212) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
appium
Thanks to all for response. I found the same issue on github.com/appium/appium-desktop/issues/181 There's no automatic server startup configuration for Appium Desktop. The only way is to run it from the command line which requires a Node installation.
– lunin
Nov 23 at 16:00
add a comment |
I use appium-desktop-setup-1.8.2.
On Windows I start it from the console with such options:
appium
appium -p 4724
start appium
But I only have the Appium launch window open. Appium doesn't start automatically. It have to run it manually.
What am I doing wrong?
I don't understand this response:
C:Program Files (x86)Appium>appium -U 0b36774b032fbdba -p 4724
C:Program Files (x86)Appium>
Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://github.com/facebook/prop-types#prop-types
Warning: Accessing createClass via the main React package is deprecated, and will be removed in React v16.0. Use a plain JavaScript class instead. If you're not yet ready to migrate, create-react-class v15.* is available on npm as a temporary, drop-in replacement. For more info see https://github.com/facebook/prop-types#prop-types
(node:10212) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
appium
I use appium-desktop-setup-1.8.2.
On Windows I start it from the console with such options:
appium
appium -p 4724
start appium
But I only have the Appium launch window open. Appium doesn't start automatically. It have to run it manually.
What am I doing wrong?
I don't understand this response:
C:Program Files (x86)Appium>appium -U 0b36774b032fbdba -p 4724
C:Program Files (x86)Appium>
Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://github.com/facebook/prop-types#prop-types
Warning: Accessing createClass via the main React package is deprecated, and will be removed in React v16.0. Use a plain JavaScript class instead. If you're not yet ready to migrate, create-react-class v15.* is available on npm as a temporary, drop-in replacement. For more info see https://github.com/facebook/prop-types#prop-types
(node:10212) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
appium
appium
edited Nov 23 at 11:47
Wasiq Bhamla
62159
62159
asked Nov 22 at 17:15
lunin
12
12
Thanks to all for response. I found the same issue on github.com/appium/appium-desktop/issues/181 There's no automatic server startup configuration for Appium Desktop. The only way is to run it from the command line which requires a Node installation.
– lunin
Nov 23 at 16:00
add a comment |
Thanks to all for response. I found the same issue on github.com/appium/appium-desktop/issues/181 There's no automatic server startup configuration for Appium Desktop. The only way is to run it from the command line which requires a Node installation.
– lunin
Nov 23 at 16:00
Thanks to all for response. I found the same issue on github.com/appium/appium-desktop/issues/181 There's no automatic server startup configuration for Appium Desktop. The only way is to run it from the command line which requires a Node installation.
– lunin
Nov 23 at 16:00
Thanks to all for response. I found the same issue on github.com/appium/appium-desktop/issues/181 There's no automatic server startup configuration for Appium Desktop. The only way is to run it from the command line which requires a Node installation.
– lunin
Nov 23 at 16:00
add a comment |
2 Answers
2
active
oldest
votes
As from official APPIUM documentation -U options is deprecated now!! Thats why you are getting error
to start appium , you can simply type
appium -p 4723
However , it seems that your objective is to create an appium session with a device as well.
in below blog i have mentioned how to make request to appium using Robot Framework, However, you can just have a look and implement in any language.
https://automationlab0000.wordpress.com/2018/08/21/first-automation-script-using-robot-framework/
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
add a comment |
To start appium server you can use
appium -a 127.0.0.1 -p 4723
Make sure port 4723 is not used by any other process. To check use
netstat –aon | find "4723"
You can find processId from above code. To terminate the process:
taskkill /F /pid processID
Then you can use appium -a 127.0.0.1 -p 4723 to start appium server.
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
To start appium server in appium desktop, First you need to open appium desktop app. Then you need to set host = 127.0.0.1 and port = 4723. And Click start server button in appium desktop.
– Suban Dhyako
Nov 24 at 17:13
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53435701%2fcant-launch-appium-from-cmd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
As from official APPIUM documentation -U options is deprecated now!! Thats why you are getting error
to start appium , you can simply type
appium -p 4723
However , it seems that your objective is to create an appium session with a device as well.
in below blog i have mentioned how to make request to appium using Robot Framework, However, you can just have a look and implement in any language.
https://automationlab0000.wordpress.com/2018/08/21/first-automation-script-using-robot-framework/
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
add a comment |
As from official APPIUM documentation -U options is deprecated now!! Thats why you are getting error
to start appium , you can simply type
appium -p 4723
However , it seems that your objective is to create an appium session with a device as well.
in below blog i have mentioned how to make request to appium using Robot Framework, However, you can just have a look and implement in any language.
https://automationlab0000.wordpress.com/2018/08/21/first-automation-script-using-robot-framework/
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
add a comment |
As from official APPIUM documentation -U options is deprecated now!! Thats why you are getting error
to start appium , you can simply type
appium -p 4723
However , it seems that your objective is to create an appium session with a device as well.
in below blog i have mentioned how to make request to appium using Robot Framework, However, you can just have a look and implement in any language.
https://automationlab0000.wordpress.com/2018/08/21/first-automation-script-using-robot-framework/
As from official APPIUM documentation -U options is deprecated now!! Thats why you are getting error
to start appium , you can simply type
appium -p 4723
However , it seems that your objective is to create an appium session with a device as well.
in below blog i have mentioned how to make request to appium using Robot Framework, However, you can just have a look and implement in any language.
https://automationlab0000.wordpress.com/2018/08/21/first-automation-script-using-robot-framework/
answered Nov 23 at 5:50
pankaj mishra
1,0092415
1,0092415
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
add a comment |
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
add a comment |
To start appium server you can use
appium -a 127.0.0.1 -p 4723
Make sure port 4723 is not used by any other process. To check use
netstat –aon | find "4723"
You can find processId from above code. To terminate the process:
taskkill /F /pid processID
Then you can use appium -a 127.0.0.1 -p 4723 to start appium server.
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
To start appium server in appium desktop, First you need to open appium desktop app. Then you need to set host = 127.0.0.1 and port = 4723. And Click start server button in appium desktop.
– Suban Dhyako
Nov 24 at 17:13
add a comment |
To start appium server you can use
appium -a 127.0.0.1 -p 4723
Make sure port 4723 is not used by any other process. To check use
netstat –aon | find "4723"
You can find processId from above code. To terminate the process:
taskkill /F /pid processID
Then you can use appium -a 127.0.0.1 -p 4723 to start appium server.
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
To start appium server in appium desktop, First you need to open appium desktop app. Then you need to set host = 127.0.0.1 and port = 4723. And Click start server button in appium desktop.
– Suban Dhyako
Nov 24 at 17:13
add a comment |
To start appium server you can use
appium -a 127.0.0.1 -p 4723
Make sure port 4723 is not used by any other process. To check use
netstat –aon | find "4723"
You can find processId from above code. To terminate the process:
taskkill /F /pid processID
Then you can use appium -a 127.0.0.1 -p 4723 to start appium server.
To start appium server you can use
appium -a 127.0.0.1 -p 4723
Make sure port 4723 is not used by any other process. To check use
netstat –aon | find "4723"
You can find processId from above code. To terminate the process:
taskkill /F /pid processID
Then you can use appium -a 127.0.0.1 -p 4723 to start appium server.
answered Nov 23 at 9:18
Suban Dhyako
585216
585216
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
To start appium server in appium desktop, First you need to open appium desktop app. Then you need to set host = 127.0.0.1 and port = 4723. And Click start server button in appium desktop.
– Suban Dhyako
Nov 24 at 17:13
add a comment |
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
To start appium server in appium desktop, First you need to open appium desktop app. Then you need to set host = 127.0.0.1 and port = 4723. And Click start server button in appium desktop.
– Suban Dhyako
Nov 24 at 17:13
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
Thanks, but it's only suitable only for Node installation, not for Desktop. I don't understand why.
– lunin
Nov 23 at 16:02
To start appium server in appium desktop, First you need to open appium desktop app. Then you need to set host = 127.0.0.1 and port = 4723. And Click start server button in appium desktop.
– Suban Dhyako
Nov 24 at 17:13
To start appium server in appium desktop, First you need to open appium desktop app. Then you need to set host = 127.0.0.1 and port = 4723. And Click start server button in appium desktop.
– Suban Dhyako
Nov 24 at 17:13
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53435701%2fcant-launch-appium-from-cmd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Thanks to all for response. I found the same issue on github.com/appium/appium-desktop/issues/181 There's no automatic server startup configuration for Appium Desktop. The only way is to run it from the command line which requires a Node installation.
– lunin
Nov 23 at 16:00