Is anyone else facing this problem?
I can generate Debug and Release versions of my App in Bundle Package. No gradle erros during the Assemble.
Dependencies:
// Litho
implementation 'com.facebook.litho:litho-core:0.19.0'
implementation 'com.facebook.litho:litho-widget:0.19.0'
compileOnly 'com.facebook.litho:litho-annotations:0.19.0'
annotationProcessor 'com.facebook.litho:litho-processor:0.19.0'
// Sections
implementation 'com.facebook.litho:litho-sections-core:0.19.0'
implementation 'com.facebook.litho:litho-sections-widget:0.19.0'
compileOnly 'com.facebook.litho:litho-sections-annotations:0.19.0'
annotationProcessor 'com.facebook.litho:litho-sections-processor:0.19.0'
// SoLoader
implementation 'com.facebook.soloader:soloader:0.5.1'
But when I run it on the Android Device, app crashes and logcat shows it:
2019-03-22 12:59:40.128 18103-18103/br.com.hinorede.app D/SoLoader: libyoga.so not found on /data/app/br.com.hinorede.app-aqB3syBNAjQg9cbzWpXDQg==/lib/arm64
2019-03-22 12:59:40.129 18103-18103/br.com.hinorede.app D/SoLoader: libyoga.so not found on /system/vendor/lib
2019-03-22 12:59:40.129 18103-18103/br.com.hinorede.app D/SoLoader: libyoga.so not found on /system/lib
2019-03-22 12:59:40.131 18103-18103/br.com.hinorede.app E/SoLoader: couldn't find DSO to load: libyoga.so
2019-03-22 12:59:40.131 18103-18103/br.com.hinorede.app D/AndroidRuntime: Shutting down VM
2019-03-22 12:59:40.137 18103-18103/br.com.hinorede.app E/AndroidRuntime: FATAL EXCEPTION: main
Process: br.com.hinorede.app, PID: 18103
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libyoga.so
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:703)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:564)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:500)
at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:455)
If I run the app using the traditional method (Apk File) it works fine. But when I run from the bundle it crashes.
Anyone?
Thanks.
Launching lib\main.dart on Snap 4G2 in debug mode...
Initializing gradle...
Resolving dependencies...
Gradle task 'assembleDebug'...
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:processDebugResources'.
Android resource linking failed
Output: error: resource android:attr/fontVariationSettings not found.
C:\Users\rajesh.yadav\AndroidStudioProjects\microfinance\build\app\intermediates\incremental\mergeDebugResources\merged.dir\values\values.xml:337: error: resource android:attr/ttcIndex not found.
error: failed linking references.
Command: C:\Users\rajesh.yadav.gradle\caches\transforms-1\files-1.1\aapt2-3.2.1-4818971-windows.jar\333594338724db9cac843ec5e02726f3\aapt2-3.2.1-4818971-windows\aapt2.exe link -I\
C:\Users\rajesh.yadav\AppData\Local\Android\sdk\platforms\android-27\android.jar\
--manifest\
C:\Users\rajesh.yadav\AndroidStudioProjects\microfinance\build\app\intermediates\merged_manifests\debug\processDebugManifest\merged\AndroidManifest.xml\
-o\
C:\Users\rajesh.yadav\AndroidStudioProjects\microfinance\build\app\intermediates\processed_res\debug\processDebugResources\out\resources-debug.ap_\
-R\
C:\Users\rajesh.yadav\AndroidStudioProjects\microfinance\build\app\intermediates\incremental\processDebugResources\resources-list-for-resources-debug.ap_.txt\
--auto-add-overlay\
--java\
BUILD FAILED in 2m 25s
Finished with error: Gradle task assembleDebug failed with exit code 1
You're using compile SDK version 27 (that's why android-27\android.jar is passed to AAPT2), but you or one of your dependencies is using resources from SDK version 28 (i.e. fontVariationSettings and ttcIndex). Update your compile SDK version in your build.gradle file to version 28.
I am receiving the following error when trying to launch my automation tests using selenium grid.
I have the hub running after launching this command.
When I browse http://10.1.27.27:4441/grid/register
I receive this error message:
HTTP ERROR 500
Problem accessing /grid/register. Reason:
Server Error
Caused by:
java.lang.IllegalStateException: Not a JSON Object: null
at com.google.gson.JsonElement.getAsJsonObject(JsonElement.java:90)
at org.openqa.grid.web.servlet.RegistrationServlet.process(RegistrationServlet.java:84)
at org.openqa.grid.web.servlet.RegistrationServlet.doGet(RegistrationServlet.jav
Command to start the hub
C:\seleniumserver\java -jar selenium-server-standalone-3.4.0.jar -role hub -port 4441
C:\seleniumserver\java -jar selenium-server-standalone-3.4.0.jar -role wd -hub http://localhost:4441/grid/register
Code
var capabilities = DesiredCapabilities.Chrome();
capabilities.Platform = Platform.CurrentPlatform;
IWebDriver driver = new RemoteWebDriver(new Uri("http://localhost:4441/wd/hub"), capabilities);
Error message received
at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(Uri remoteAddress, ICapabilities desiredCapabilities)
at Boden.Automation.Workflow.BodenMobileNavigation..ctor() in C:\Projects\UAT Automation\Dev\SourceCode\test.cs:line 43
at test..ctor() in C:\Projects\UAT Automation\Dev\SourceCode\test.cs:line 21
Log
Log 2
Update
Here are my actions. Open command prompt (as administrator), navigate to the selenium jar folder and execute this command
java -jar selenium-server-standalone-3.4.0.jar -role hub -port 4441
The output from this command is here:
C:\SeleniumGrid>java -jar selenium-server-standalone-3.4.0.jar -role hub -port 4441
14:40:34.811 INFO - Selenium build info: version: '3.4.0', revision: 'unknown'
14:40:34.811 INFO - Launching Selenium Grid hub
2017-08-03 14:40:35.252:INFO::main: Logging initialized #603ms to org.seleniumhq.jetty9.util.log.StdErrLog
14:40:35.262 INFO - Will listen on 4441
2017-08-03 14:40:35.299:INFO:osjs.Server:main: jetty-9.4.3.v20170317
2017-08-03 14:40:35.322:INFO:osjs.session:main: DefaultSessionIdManager workerName=node0
2017-08-03 14:40:35.322:INFO:osjs.session:main: No SessionScavenger set, using defaults
2017-08-03 14:40:35.324:INFO:osjs.session:main: Scavenging every 600000ms
2017-08-03 14:40:35.329:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler#154b04f{/,null,AVAILABLE}
2017-08-03 14:40:35.341:INFO:osjs.AbstractConnector:main: Started ServerConnector#13af739{HTTP/1.1,[http/1.1]}{0.0.0.0:4441}
2017-08-03 14:40:35.341:INFO:osjs.Server:main: Started #692ms
14:40:35.342 INFO - Nodes should register to
http://10.1.27.27:4441/grid/register/
14:40:35.342 INFO - Selenium Grid hub is up and running
Then, I open a new command prompt (as administrator) and execute the following command in the selenium folder
java -jar selenium-server-standalone-3.4.0.jar -role wd -hub http://localhost:4441/grid/register
The output from this command is here:
C:\SeleniumGrid>java -jar selenium-server-standalone-3.4.0.jar -role wd -hub http://localhost:4441/grid/register
14:41:19.175 INFO - Selenium build info: version: '3.4.0', revision: 'unknown'
14:41:19.175 INFO - Launching a Selenium Grid node
2017-08-03 14:41:19.516:INFO::main: Logging initialized #505ms to org.seleniumhq.jetty9.util.log.StdErrLog
14:41:19.563 INFO - Driver class not found: com.opera.core.systems.OperaDriver
14:41:19.563 INFO - Driver provider com.opera.core.systems.OperaDriver
registration is skipped:Unable to create new instances on this machine.
14:41:19.564 INFO - Driver class not found: com.opera.core.systems.OperaDriver
14:41:19.564 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered
14:41:19.565 INFO - Driver provider org.openqa.selenium.safari.SafariDriver registration is skipped: registration capabilities Capabilities [{browserName=safari, version=, platform=MAC}] does not match the current platform WIN8_1
2017-08-03 14:41:19.592:INFO:osjs.Server:main: jetty-9.4.3.v20170317
2017-08-03 14:41:19.613:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler#10f1111{/,null,AVAILABLE}
2017-08-03 14:41:19.625:INFO:osjs.AbstractConnector:main: Started ServerConnector#23e5ee{HTTP/1.1,[http/1.1]}{0.0.0.0:5555}
2017-08-03 14:41:19.626:INFO:osjs.Server:main: Started #615ms
14:41:19.626 INFO - Selenium Grid node is up and ready to register to the hub
14:41:19.636 INFO - Starting auto registration thread. Will try to register every 5000 ms.
14:41:19.636 INFO - Registering the node to the hub:http://localhost:4441/grid/register
14:41:19.675 INFO - The node is registered to the hub and ready to use
C# error (from running it within visual studio)
at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(Uri remoteAddress, ICapabilities desiredCapabilities)
at ....ctor() in C:\Projects\UAT Automation\Dev\SourceCode...cs:line 38
at ....ctor() in C:\Projects\UAT Automation\Dev\SourceCode...cs:line 21
This is the error I receive
I am trying to run some automated tests on Jenkins using protractor which uses selenium and chromedriver.
I have also setup xvfb so that we can run these tests in a headless manner. I have the xvfb jenkins plugin installed and it is working correctly.
Error
The problem I'm having, is when I start the tests, chrome keeps crashing. I get this error:
E/launcher - WebDriverError: unknown error: Chrome failed to start: crashed
...
E/launcher - Process exited with error code 199
Setup
Here is the information I have on the setup of the system:
Chrome
Location: /usr/bin/google-chrome
Version: Chromium 52.0.2743.0
ChromeDriver
Location: {project_home}/src/js/node_modules/webdriver-manager/selenium/chromedriver_2.24
Version: ChromeDriver 2.24.417424
Selenium
Location: {project_home}/src/js/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar
Version: 2.53.1
Protractor
Location: {project_home}/src/js/node_modules/protractor
Version: 4.0.9
WebDriver Manager
Location: {project_home}/src/js/node_modules/webdriver-manager
Version: 10.2.4
Jenkins
Version: 1.6.17
xvfb
Version: Unknown
Node
Version: 6.7
Java
Version: java-8-openjdk-amd64
Output
Here is the console output from Jenkins:
...
21:58:07.380 INFO - Launching a standalone Selenium Server
21:58:07.407 INFO - Java: Oracle Corporation 25.111-b14
21:58:07.407 INFO - OS: Linux 4.4.0-47-generic amd64
21:58:07.418 INFO - v2.53.1, with Core v2.53.1. Built from revision a36b8b1
21:58:07.473 INFO - Driver provider org.openqa.selenium.ie.InternetExplorerDriver registration is skipped:
registration capabilities Capabilities [{ensureCleanSession=true, browserName=internet explorer, version=, platform=WINDOWS}] does not match the current platform LINUX
21:58:07.474 INFO - Driver provider org.openqa.selenium.edge.EdgeDriver registration is skipped:
registration capabilities Capabilities [{browserName=MicrosoftEdge, version=, platform=WINDOWS}] does not match the current platform LINUX
21:58:07.474 INFO - Driver class not found: com.opera.core.systems.OperaDriver
21:58:07.474 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered
21:58:07.475 INFO - Driver provider org.openqa.selenium.safari.SafariDriver registration is skipped:
registration capabilities Capabilities [{browserName=safari, version=, platform=MAC}] does not match the current platform LINUX
21:58:07.475 INFO - Driver class not found: org.openqa.selenium.htmlunit.HtmlUnitDriver
21:58:07.475 INFO - Driver provider org.openqa.selenium.htmlunit.HtmlUnitDriver is not registered
21:58:07.527 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub
21:58:07.527 INFO - Selenium Server is up and running
Current webdriver status: [21:58:08] I/status - selenium standalone version available: 2.53.1 [default]
[21:58:08] I/status - chromedriver versions available: 2.22, 2.24 [default]
[21:58:08] I/status - geckodriver version available: v0.9.0 [default]
[21:58:08] I/status - android-sdk is not present
[21:58:08] I/status - appium is not present
**** STARTING GUI TESTS ****
Running ./node_modules/protractor/bin/protractor conf-server.js
[21:58:08] I/local - Starting selenium standalone server...
[21:58:08] I/launcher - Running 1 instances of WebDriver
[21:58:09] I/local - Selenium standalone server started at http://10.0.0.82:33509/wd/hub
[21:59:09] E/launcher - unknown error: Chrome failed to start: crashed
(Driver info: chromedriver=2.24.417424 (c5c5ea873213ee72e3d0929b47482681555340c3),platform=Linux 4.4.0-47-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.17 seconds
Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03'
System info: host: 'ip-10-0-0-82', ip: '10.0.0.82', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-47-generic', java.version: '1.8.0_111'
Driver info: org.openqa.selenium.chrome.ChromeDriver
[21:59:09] E/launcher - WebDriverError: unknown error: Chrome failed to start: crashed
(Driver info: chromedriver=2.24.417424 (c5c5ea873213ee72e3d0929b47482681555340c3),platform=Linux 4.4.0-47-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.17 seconds
Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03'
System info: host: 'ip-10-0-0-82', ip: '10.0.0.82', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-47-generic', java.version: '1.8.0_111'
Driver info: org.openqa.selenium.chrome.ChromeDriver
at WebDriverError ({project_home}/src/js/node_modules/selenium-webdriver/lib/error.js:27:5)
at Object.checkLegacyResponse ({project_home}/src/js/node_modules/selenium-webdriver/lib/error.js:639:15)
at parseHttpResponse ({project_home}/src/js/node_modules/selenium-webdriver/http/index.js:538:13)
at client_.send.then.response ({project_home}/src/js/node_modules/selenium-webdriver/http/index.js:472:11)
at ManagedPromise.invokeCallback_ ({project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:1379:14)
at TaskQueue.execute_ ({project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:2913:14)
at TaskQueue.executeNext_ ({project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:2896:21)
at asyncRun ({project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:2820:25)
at {project_home}/src/js/node_modules/selenium-webdriver/lib/promise.js:639:7
at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
at Function.createSession ({project_home}/src/js/node_modules/selenium-webdriver/lib/webdriver.js:329:24)
at Builder.build ({project_home}/src/js/node_modules/selenium-webdriver/builder.js:458:24)
at Local.DriverProvider.getNewDriver ({project_home}/src/js/node_modules/protractor/built/driverProviders/driverProvider.js:37:33)
at Runner.createBrowser ({project_home}/src/js/node_modules/protractor/built/runner.js:198:43)
at {project_home}/src/js/node_modules/protractor/built/runner.js:277:30
at _fulfilled ({project_home}/src/js/node_modules/q/q.js:834:54)
at self.promiseDispatch.done ({project_home}/src/js/node_modules/q/q.js:863:30)
at Promise.promise.promiseDispatch ({project_home}/src/js/node_modules/q/q.js:796:13)
at {project_home}/src/js/node_modules/q/q.js:604:44
at runSingle ({project_home}/src/js/node_modules/q/q.js:137:13)
[21:59:09] E/launcher - Process exited with error code 199
Protractor Config
exports.config = {
seleniumServerJar: './node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar',
chromeDriver: './node_modules/webdriver-manager/selenium/chromedriver_2.24',
capabilities: {
'browserName': 'chrome',
'chromeOptions': {
binary: '/usr/bin/google-chrome',
args: ['--enable-logging','--v=1'],
extensions: []
}
},
framework: 'custom',
frameworkPath: require.resolve('./node_modules/protractor-cucumber-framework'),
specs: [
'../../features/gui/active/*.feature'
],
onPrepare: function ()
{
require('babel-register')({ presets : ['es2015'] })
}
};
Jenkins xvfb plugin
Related
Chrome reference: https://sites.google.com/a/chromium.org/chromedriver/help/chrome-doesn-t-start
unknown error: Chrome failed to start: exited abnormally (Driver info: chromedriver=2.9 suggests configuring xvfb
WebDriverError: unknown error: Chrome failed to start: exited abnormally unsolved
https://github.com/seleniumhq/selenium-google-code-issue-archive/issues/8409 suggests using direct connect: "Protractor can test directly against Chrome and Firefox without using a Selenium Server. To use this, in your config file set directConnect: true."
Selenium Webdriver & Chrome driver - not able to run chrome driver suggests using java 1.6 instead
Chrome on remote webdriver (via Grid) failed to start suggests using x64 chromedriver and specifying it in a parameter
Please try updating Protractor to latest 4.0.11 and chrome driver to 2.25 as there were lot of issues reported in 2.24 version which has been fixed.
Try it once and let us know.
Can you follow below :
- In you jenkins settings add a global property
key : DISPLAY
value:0:0
- On your server start Xvfb in the background:
Xvfb :0 -ac -screen 0 1024x768x24 &
Reference link:
unknown error: Chrome failed to start: exited abnormally (Driver info: chromedriver=2.9
I had the same issue as you
I ended up to change my args as a below
args: [ "--headless", "--no-sandbox" ,"--disable-dev-shm-usage"]
I am facing below exception while launching the Oculus SDK 0.6.0.1 demo program.
**Exception Info
Exception report file: C:\Users\Exception Report (2015-06-26 12.41.23).txt
Exception minidump file: C:\Users\Exception Minidump (2015-06-26 12.41.23).mdmp
Time (GMT): 2015/06/26 12:41:23
Time (local): 2015/06/26 18:11:23
Thread name: (not available)
Thread handle: 0x000000d8
Thread sys id: 976 (0x3d0)
Exception instruction address: 0x0ff4f677 (see callstack below)
Exception description: ACCESS_VIOLATION reading address 0x00000000
Exception location: ovr_WaitTillTime (59911)**
below is my app and system Info :
App Info
Process path: C:\Users\Downloads\ovr_sdk_win_0.6.0.0\OculusSDK\Samples\OculusWorldDemo\Release\OculusWorldDemo.exe
App format: 32 bit
App version info not present
System Info
OS name: Windows 7, version: 6.1 build 7601, 32 bit, platform id: 2, service pack: Service Pack 1
Debugger present: no
Processor count: 4
Processor type: x86
Processor level: 6
Processor revision: 10759
Memory load: 87%
Total physical memory: 3240 MiB
Available physical memory: 389 MiB
Total page file memory: 6480 MiB
Available page file memory: 2323 MiB
Total virtual memory: 2047 MiB
Free virtual memory: 1974 MiB
Can someone help me to understand what to do, to fix this issue :(
You didn't include any info about your video hardware & drivers; the first thing I'd try is upgrading them. Also try upgrading to the latest Oculus 0.7.0.1 runtime.