Open nathan-alden-hp opened 5 years ago
Hi @nathan-alden-hp
Can you run get-StartApps
via powershell and confirm the app name?
PS > Get-StartApps | ?{ $_.Name.Contains("XamlUwpApp") }
Name AppID
---- -----
XamlUwpApp 52a95998-8cfa-43d7-96c9-06fc6d8ad1c5_x38zh4nq6sjk4!App
FWIW, I updated the Appium.WebDriver package to 4.0.0. I got some obsolete warnings, so I updated my test code to this:
var options = new AppiumOptions();
options.AddAdditionalCapability("app", "52a95998-8cfa-43d7-96c9-06fc6d8ad1c5_0.0.0.0_x64__x38zh4nq6sjk4!app");
var windowsDriver = new WindowsDriver<WindowsElement>(new Uri("http://127.0.0.1:4723/"), options);
windowsDriver.FindElementByAccessibilityId("UIGenerateRandomEquationButton").Click();
However, the driver still reports the same error.
Also note that this app is being side-loaded by using the Add-AppDevPackage.ps1
script generated by the Store app package build in Visual Studio. The self-signed certificate used to sign the bundle was added to the Trusted Root Certification Authorities store by the script.
Hi @nathan-alden-hp
Try passing in just the following for the AppID - since it looks like there is a variation what is being reported.
52a95998-8cfa-43d7-96c9-06fc6d8ad1c5_x38zh4nq6sjk4!App
If that doesn't work, then I'd recommend using a Desktop Session.
Hello @hassanuz,
I am facing the similar issue. Not able to launch my app through App ID.
Could you please suggest me the fix?
Thanks Gaurav Agnihotri
Proof that my UWP app is installed (Visual Studio installs it when I run it in Debug configuration):
XAML:
Test class:
WinAppDriver response: