• 您好 ,我这格式 APPIUM 的输出日志,从日志上看是可以看到 PID 的 ,您说的这种方式是在执行时去查看进程情况吗?

  • 请楼主帮我看看这个问题,主要是加粗那一段。万分感谢🙏 🙏 🙏 !@ 碎冰之殇

    • cmd C:\Users\Administrator>cnpm i macaca-android -g Downloading macaca-android to D:\Program Files\nodejs\node_global\node_modules\macaca-android_tmp Copying D:\Program Files\nodejs\node_global\node_modules\macaca-android_tmp_macaca-android@2.1.0@macaca-android to D:\Program Files\nodejs\node_global\node_modules\macaca-android Installing macaca-android's dependencies to D:\Program Files\nodejs\node_global\node_modules\macaca-android/node_modules [1/10] webdriver-dfn-error-code@~1.0.1 installed at node_modules_webdriver-dfn-error-code@1.0.4@webdriver-dfn-error-code [2/10] driver-base@~0.1.0 installed at node_modules_driver-base@0.1.4@driver-base [3/10] macaca-utils@1.0.0 installed at node_modules_macaca-utils@1.0.1@macaca-utils [4/10] xml2map@1.0.2 installed at node_modules_xml2map@1.0.2@xml2map [5/10] unlock-apk@1.1.1 installed at node_modules_unlock-apk@1.1.2@unlock-apk [6/10] macaca-adb@~1.0.3 installed at node_modules_macaca-adb@1.0.34@macaca-adb [7/10] xlogger@~1.0.0 installed at node_modules_xlogger@1.0.6@xlogger [8/10] temp@~0.8.3 installed at node_modules_temp@0.8.4@temp [9/10] uiautomatorwd@1.1.0 installed at node_modules_uiautomatorwd@1.1.1@uiautomatorwd [10/10] macaca-chromedriver@~1.0.1 installed at node_modules_macaca-chromedriver@1.0.45@macaca-chromedriver execute post install 3 scripts... [1/3] scripts.install unlock-apk@1.1.1 run "node ./script/build.js", root: "D:\Program Files\nodejs\node_global\node_modules\macaca-android\node_modules\_unlock-apk@1.1.2@unlock-apk" (node:3620) UnhandledPromiseRejectionWarning: ,Starting a Gradle Daemon, 1 incompatible and 1 stopped Daemons could not be reused, use --status for details

    Configure project :app
    WARNING: The specified Android SDK Build Tools version (25.0.2) is ignored, as it is below the minimum supported version (28.0.3) for Android Gradle Plugin 3.2.1.
    Android SDK Build Tools 28.0.3 will be used.
    To suppress this warning, remove "buildToolsVersion '25.0.2'" from your build.gradle file, as each version of the Android Gradle Plugin now has a default version of the build tools.
    Checking the license for package Android SDK Build-Tools 28.0.3 in E:\SDK\android-sdk-windows\licenses
    License for package Android SDK Build-Tools 28.0.3 accepted.
    Preparing "Install Android SDK Build-Tools 28.0.3 (revision: 28.0.3)".
    "Install Android SDK Build-Tools 28.0.3 (revision: 28.0.3)" ready.
    Installing Android SDK Build-Tools 28.0.3 in E:\SDK\android-sdk-windows\build-tools\28.0.3
    "Install Android SDK Build-Tools 28.0.3 (revision: 28.0.3)" complete.
    "Install Android SDK Build-Tools 28.0.3 (revision: 28.0.3)" finished.
    Checking the license for package Android SDK Platform 26 in E:\SDK\android-sdk-windows\licenses
    License for package Android SDK Platform 26 accepted.
    Preparing "Install Android SDK Platform 26 (revision: 2)".
    "Install Android SDK Platform 26 (revision: 2)" ready.
    Installing Android SDK Platform 26 in E:\SDK\android-sdk-windows\platforms\android-26
    "Install Android SDK Platform 26 (revision: 2)" complete.
    "Install Android SDK Platform 26 (revision: 2)" finished.

    Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
    Use '--warning-mode all' to show the individual deprecation warnings.
    See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
    ,
    FAILURE: Build failed with an exception.

    • What went wrong:
      A problem occurred configuring project ':app'.
      > Failed to notify project evaluation listener.
      >org.gradle.api.file.ProjectLayout.fileProperty(Lorg/gradle/api/provider/Provider;) Lorg/gradle/api/file/RegularFileProperty;

    • Try:
      Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

    • Get more help at https://help.gradle.org

    BUILD FAILED in 1m 13s

    (node:3620) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
    (node:3620) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    [1/3] scripts.install unlock-apk@1.1.1 finished in 1m
    [2/3] scripts.install uiautomatorwd@1.1.0 run "node ./scripts/build.js", root: "D:\Program Files\nodejs\node_global\node_modules\macaca-android\node_modules\_uiautomatorwd@1.1.1@uiautomatorwd"
    (node:13532) UnhandledPromiseRejectionWarning: ,

    Configure project :app
    WARNING: Configuration 'androidTestCompile' is obsolete and has been replaced with 'androidTestImplementation' and 'androidTestApi'.
    It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html
    WARNING: Configuration 'androidTestApi' is obsolete and has been replaced with 'androidTestImplementation'.
    It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html
    WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
    It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html
    WARNING: The specified Android SDK Build Tools version (25.0.2) is ignored, as it is below the minimum supported version (28.0.3) for Android Gradle Plugin 3.2.1.
    Android SDK Build Tools 28.0.3 will be used.
    To suppress this warning, remove "buildToolsVersion '25.0.2'" from your build.gradle file, as each version of the Android Gradle Plugin now has a default version of the build tools.

    Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
    Use '--warning-mode all' to show the individual deprecation warnings.
    See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
    ,
    FAILURE: Build failed with an exception.

    • What went wrong:
      A problem occurred configuring project ':app'.

      Failed to notify project evaluation listener.
      org.gradle.api.file.ProjectLayout.fileProperty(Lorg/gradle/api/provider/Provider;) Lorg/gradle/api/file/RegularFileProperty;

    • Try:
      Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

    • Get more help at https://help.gradle.org

    BUILD FAILED in 1s

    (node:13532) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
    (node:13532) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    [2/3] scripts.install uiautomatorwd@1.1.0 finished in 2s
    [3/3] scripts.install macaca-chromedriver@~1.0.1 run "node ./bin/macaca-chromedriver install", root: "D:\Program Files\nodejs\node_global\node_modules\macaca-android\node_modules\_macaca-chromedriver@1.0.45@macaca-chromedriver"

    version: 2.33
    chromedriver cdn url: https://cdn.npm.taobao.org/dist/chromedriver/2.33/chromedriver_win32.zip
    chromedriver local in D:\Program Files\nodejs\node_global\node_modules\macaca-android\node_modules_macaca-chromedriver@1.0.45@macaca-chromedriver\exec\chromedriver2.33.exe
    [3/3] scripts.install macaca-chromedriver@~1.0.1 finished in 3s
    deprecate macaca-chromedriver@1.0.45 › request@2.69.0 › node-uuid@~1.4.7 Use uuid module instead
    deprecate macaca-chromedriver@1.0.45 › request@2.69.0 › hawk@~3.1.0 This version has been deprecated. Please upgrade to the latest version to get the best features, bug fixes, and security patches.
    deprecate macaca-chromedriver@1.0.45 › request@2.69.0 › hawk@3.1.3 › sntp@1.x.x This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
    deprecate macaca-chromedriver@1.0.45 › request@2.69.0 › hawk@3.1.3 › cryptiles@2.x.x This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    deprecate macaca-chromedriver@1.0.45 › request@2.69.0 › hawk@3.1.3 › boom@2.x.x This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    deprecate macaca-chromedriver@1.0.45 › request@2.69.0 › tough-cookie@~2.2.0 ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
    deprecate macaca-chromedriver@1.0.45 › request@2.69.0 › hawk@3.1.3 › hoek@2.x.x This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    All packages installed (156 packages installed from npm registry, used 1m(network 3s), speed 1.04MB/s, json 139(290.53kB), tarball 3.21MB)

  • 请问楼主这个问题解决了吗?
    我也是这个问题 ,OPPO R11st

  • 请问有人解决了这个问题吗,我在这里卡了好久了,谷歌也没有相关的问题答案!
    手机内核 webview 版本已升级为:66.0.3359.126
    手机 chrome 浏览器版本:66.0.3359.126
    微信内嵌版本:66.0.3359.126
    chromedriver 版本:2.4

  • 请问这个问题你解决了吗?我也是遇到了这个问题.

  • 微信 webview 的自动化技术 at 2020年01月10日

    已解决
    1、浏览器看不到设备或访问资源
    确保打开 x5 内核调试开关
    2、添加代码
    ChromeOptions.setCapability("browserName","");

  • 微信 webview 的自动化技术 at 2020年01月09日

    @ 思寒_seveniruby 楼主,你好,请问一下这个错误有什么解决方法吗?error: The desired should not include both of an 'appPackage' and a 'browserName'