I built chromium-ozone-wayland successfully but im getting error on runtime.
Error Output :
ERROR : XDG_RUNTIME_DIR not set in the environment
ERROR:wayland_connection.cc(218) Failed to connect to wayland display: no such file or directory(2)
ERROR:ozone_platform_wayland.cc(220) Failed to initialize wayland platform
ERROR:env.cc(255) The platform failed to initialize. exiting.
I used this repo : https://github.com/OSSystems/meta-browser/tree/master/meta-chromium
What could it be caused by?
Related
I am trying to convert my jar file using graalvm native image. However, it gives an error like,
native-image -jar NativeTest2.jar
Error: Platform specified as windows-amd64 isn't supported.
Error: Image build request failed with exit status 1
I am using the following desiredCapabilities in my codeceptconf.js file.
Appium: { // IOS local Simulator iPhone 13
app: "./ipa/arvApp.app",
platform: "iOS",
desiredCapabilities: {
deviceName: "iPhone 13",
//os_version: "15.5",
"automationName": "XCUITest",
autoAcceptAlerts: 'true' ,
autoDissmissAlerts: 'true',
},
}
Facing the below error -
App Launch And Login options. --
Navigate to just browse in app and Login with Gmail
2022-10-04T17:44:00.627Z ERROR webdriver: Request failed with status 500 due to
unknown error: An unknown server-side error occurred while processing the command.
Original error: Simulator architecture is unsupported by the
'/Users/jule/Desktop/arive/automation/ipa/ariveApp.app' application. Make sure the
correct deployment target has been selected for its compilation in Xcode.
2022-10-04T17:44:00.628Z ERROR webdriver: unknown error: An unknown server-side
error occurred while processing the command. Original error: Simulator architecture is unsupported by the '/Users/jule/Desktop/arive/automation/ipa/ariveApp.app' application. Make sure the correct deployment target has been selected for its compilation in Xcode.
at getErrorFromResponseBody (/Users/jule/Desktop/arive/automation/node_modules/webdriver/build/utils.js:197:12)
at NodeJSRequest._request (/Users/jule/Desktop/arive/automation/node_modules/webdriver/build/request/index.js:166:60)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async startWebDriverSession (/Users/jule/Desktop/arive/automation/node_modules/webdriver/build/utils.js:67:20)
at async Function.newSession (/Users/jule/Desktop/arive/automation/node_modules/webdriver/build/index.js:46:45)
at async Object.remote (/Users/jule/Desktop/arive/automation/node_modules/webdriverio/build/index.js:77:22)
at async Appium._startBrowser (/Users/jule/Desktop/arive/automation/node_modules/codeceptjs/lib/helper/Appium.js:232:24)
Error: Can't connect to WebDriver.
Error: Failed to create session.
An unknown server-side error occurred while processing the command. Original error: Simulator architecture is unsupported by the '/Users/jule/Desktop/arive/automation/ipa/ariveApp.app' application. Make sure the correct deployment target has been selected for its compilation in Xcode.
Please make sure Selenium Server is running and accessible
I wait for element 30
✖ FAILED in 13ms
Please help to resolve this error.
Thanks
My Android react-native app is crashing with an ExecutionException.
"Could not connect to development server."
The method that is crashing is ReactInstanceManagerImpl.createReactContext().
But this is not the normal error as this screenshot shows:
Logcat shows me this stacktrace:
Exception in native call from JS
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException:
Could not connect to development server.
at com.facebook.react.ReactInstanceManagerImpl.createReactContext(ReactInstanceManagerImpl.java:860)
at com.facebook.react.ReactInstanceManagerImpl.access$700(ReactInstanceManagerImpl.java:98)
at com.facebook.react.ReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(ReactInstanceManagerImpl.java:194)
...
Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException:
at com.facebook.react.common.futures.SimpleSettableFuture.get(SimpleSettableFuture.java:68)
at com.facebook.react.ReactInstanceManagerImpl.createReactContext(ReactInstanceManagerImpl.java:831)
... 9 more
Caused by: java.lang.RuntimeException:
at com.facebook.react.bridge.ReactBridge.loadScriptFromFile(Native Method)
at com.facebook.react.bridge.JSBundleLoader$2.loadScript(JSBundleLoader.java:58)
at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:148)
at com.facebook.react.ReactInstanceManagerImpl$4.call(ReactInstanceManagerImpl.java:851)
...
This suggests that the server has sent the javascript code back to the device and the ReactBridge.loadScriptFromFile() somehow can't handle the bundle.
Points to clarify:
this happens on emulator & device (connected via USB)
this happens on Linux (Mint) & Windows (8.1)
I did run adb reverse tcp:8081 tcp:8081 as per the normal advice
I have run react-native start and the packager/server is running
the device DOES connect to the development server, as this is logged in the packager window
the URL that the device hits does return data, as can be seen if copied into the browser address bar
How is this different from the normal "Could not connect..." message?
Here is a screenshot of what happens when the server is legitimately not running:
The differences include:
no ExecutionException or RuntimeException before the error message
further clarity providing the URL that was called on the server
error comes from DevServerHelper.onFailure()
Logcat shows the stacktrace to be quite different in this normal expected case:
Unable to download JS bundle
com.facebook.react.devsupport.DebugServerException:
Could not connect to development server.
at com.facebook.react.devsupport.DevServerHelper$1.onFailure(DevServerHelper.java:196)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:140)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
This seems to have been caused by not having Windows Build Tools correctly installed. This broke the node-gyp commands required by my project.
Following the steps on the node-gyp page got my machine set up correctly.
After a new build I got this error once, and then it disappeared with the project building and running correctly.
I have the following Gradle task:
task execute(type:JavaExec, dependsOn:['build']) {
main = 'com.something.Main'
classpath = sourceSets.main.runtimeClasspath
}
When I debug the task in IntelliJ I get the following error:
ERROR: transport error 202: connect failed: Connection refused
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]
:execute FAILED
It seems later versions of IntelliJ Idea cannot connect debuggers to forked test runners when using the Gradle Test runner.
In your sources root, add a gradle.properties file with the next two lines:
maxTestForks = 1
testForkEvery = 0
That should do the job.
I had a very similar problem. When I was invoking Gradle in IntelliJ, the Java environment by default contained
JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,address=127.0.0.1:59842,suspend=y,server=n
I removed the JAVA_OPTS from the environment all together and voila, no more JDWP error because no more JDWP.
I am running 'mvn clean install -Dmaven.test.skip=true' command for a web application. but it gives following error. I set the catalina home as an environment variable. i am using maven 3.1.1 version. Please help me
FATAL ERROR in native method: JDWP No transports i
nitialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[WARNING] [talledLocalContainer] ERROR: transport error 202: bind failed: Addres
s already in use
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.4:star
t (start-container) on project RCMigrationWebApp: Execution start-container of g
oal org.codehaus.cargo:cargo-maven2-plugin:1.2.4:start failed: Failed to start t
he Tomcat 7.x container. Deployable [http://localhost:8080/cargocpc/index.html]
failed to finish deploying within the timeout period [120000]. The Deployable st
ate is thus unknown. -> [Help 1]
Probably you have to kill any process running at 8080, looks like the port is already in use..
ERROR: transport error 202: bind failed: Address already in use
Port in use. Run netstat -bv if you are using Windows. You will get to know which process is holding up the port. With your stackTrace, it looks very obvious.
Let me know if it helps.