I am running Appium scripts on IntelliJ, I am using Xcode simulator. Though I am giving correct UDID in properties file, I am always getting this issue.
org.openqa.selenium.SessionNotCreatedException: Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Unknown device or simulator UDID: '1685524E-A876-4CEB-9C75-C0C1FA0EB018'
Related
I am facing several issues while trying to launch my application from appium inspector on apple mac m2 machine . I tried for both simulator(using .app) and real device(using .ipa) . Hence wanted to check if there is any support for appium on mac m2 machine as the last release appears to be around the same time MacBook Air with M2 chip was launched.
I have installed all the pre-requisites. I have also checked the installations through appium doctor and there are no issues. Created a build. Started the appium server and entered the Desired capabilities through appium inspector and try to give Start session . But facing the below error :
Failed to create session. An unknown server-side error occurred while processing the command. Original error: Simulator architecture is unsupported by the '/Users/e5662282/fcb_mb.app' application. Make sure the correct deployment target has been selected for its compilation in Xcode.
Appium should support Mac M2.
The error that you see is because the app is not built for the simulator.
You will need to build the .app file from Xcode or from the command line and select the target as simulator. You can follow the steps from here:
https://help.perfecto.io/perfecto-help/content/perfecto/automation-testing/create_an_ios_simulator_build.htm
You can also refer this defect on Appium GitHub that has similar issue: https://github.com/appium/appium/issues/17649
It is happening when I attempt to deploy the application to the iOS app store. Before everything was ok. I tried to change App version and App code. I also updated VS Mac and XCode.
I archived my app and tried to publish via Apple Transporter. Then I got a normal error message.
After all I relogin in my Apple Developer Account + downloaded all profiles.
I have installed Desktop App Converter from the Windows store.
When I try to run the app (literally just launch it), I get the message:
[Window Title]
C:\Program Files\WindowsApps\Microsoft.DesktopAppConverter_2.0.2.0_x64__8wekyb3d8bbwe\DACTileLauncher.exe
[Content]
C:\Program Files\WindowsApps\Microsoft.DesktopAppConverter_2.0.2.0_x64__8wekyb3d8bbwe\DACTileLauncher.exe
The data area passed to a system call is too small.
I have tried running the Troubleshooter for Windows Apps, it tells me that "Windows Store cache and licenses may be corrupt" and tries to fix them, but running the troubleshooter a second time gives the same issue.
Each time I try to run the Desktop App Converter, I get 2 errors in Event Viewer:
%1: Cannot create the Desktop AppX container for package %2 because an error was encountered configuring the runtime.
%4: Cannot create the process for package %1 because an error was encountered while configuring runtime. %5
... both from AppModel-runtime
Any ideas how I can troubleshoot from here?
If you have problems with the Microsoft DAC you try this new converter, it is much easier to use, it has a GUI (no command line), built-in support for digital signing and allows you to customize the list of files that get inside your AppX.
Also, you can generate AppX packages for applications which do not (cannot) install silently.
It runs on Windows 7 too, not just Windows 10 (recommended).
I'm no longer able to debug my Cordova app on the iOS simulator. I get the dreaded "We're unable to find the app ... you're trying to debug." error. I've tried all the troubleshooting steps, but nothing has worked so far.
I should note that this was working just fine. I was able to debug my app multiple times, with no issues, and then suddenly this error started, and nothing I've tried has fixed it.
Interestingly, the actual build logs in Visual Studio make it look like everything went fine:
Requesting debug on remote iOS device for buildNumber 6805 on server https://<redacted>:3000/cordova...
Debugging - Successfully Debugging on the device
{webDebugPort=9221}
Anyone have any ideas?
UPDATE 1
Tried this on my local OS X device, too, and got a similar result. Here are the actual build logs:
Unable to attach to debug. Check that http://Matts-Mac-mini:9221 is accessible.
We were unable to find the app you’re trying to debug. Check that the device is connected, awake, and unlocked. Also, make sure it has Web Inspector enabled.
------ Cordova tools 6.1.1 already installed.
Requesting emulate on iOS Simulator for buildNumber 522 on server http://Matts-Mac-mini:3000/cordova...
Emulated - Successfully sent to ios Simulator
------ Cordova tools 6.1.1 already installed.
Requesting debug on remote iOS device for buildNumber 522 on server http://Matts-Mac-mini:3000/cordova...
Debugging - Successfully Debugging on the device
{webDebugPort=9221}
It looks like things fail, but then the later messages (which appear right away) make it look like things worked. And the app is indeed running in the simulator on my Mac.
After the discussion in the comments, I believe that the issue here is using a shared machine for debugging. If there are multiple iOS simulators running on a machine at the same time (Typically because there are multiple users connected to the machine each running their own simulator) then remotebuild cannot guarantee that you connect to the correct simulator. This is because we use ios-webkit-debug-proxy which assumes that only a single iOS simulator exists, and doesn't expose a way to restrict which one it connects to.
If you are trying to debug an app in the simulator and there is another user with a different simulator, you may connect to the wrong simulator where your app will not be running, and that can cause the error that you see.
I'm using Xcode 6.1, iPhone 6 simulator for my Appium automation tests.
I'm having a trouble of reset iOS simulator. The first time after reboot using simulator is always fine. But if I quit the simulator, and tried to use it again (both manually and load using Appium tool), I'll keep getting blackscreen for simulator. I got the following info from my automation log 'Could not reset simulator. Leaving as is. Error: Command failed: // stderr'
I've tried the 'Reset Content and Settings' from simulator, it would not help. I still getting the black screen. and I've also tried to kill the simulator from command line using 'killall SimulatorBridge', still not work.
The only way that I could get this working is - reboot my laptop... this gives me a big pain. I'm thinking if reboot could help, there must be some process that I could kill to reset it? Anyone could kindly give me some help here? Many thanks!