calabash | Automated Acceptance Testing for Mobile Apps | Functional Testing library

Please take a look to this GitHub Issue

https://github.com/microsoft/appcenter/issues/1992#issuecomment-724843179

It seems to be a fail with Xamarin.UITest and XCode 12

As you can read from the stack trace provided by you in the questions, the error is actually occuring on line 369 of your ‘Login.xaml.cs’ file.

If you place an "Exception catchpoint" and it should tell you exactly what line is causing that issue. Placing a try-catch around it should fix the crash, but try to to resolve the issue as well since exceptions in general are bad.

Besides that, you can also to use DispatchAsync instead

Yes, it is possible to use Calabash on an ipa. Compile-time linking is no longer strictly required. See https://github.com/calabash/run_loop/pull/750 - this is a work in progress. I am no longer working on the Calabash project, but I can provide some guidance.

See my response here: https://github.com/calabash/calabash-ios-server/issues/459

Calabash iOS Server and Test Cloud Agent are the same.

Microsoft has deprecated support for the Calabash iOS and Android cucumber ruby clients.

Xamarin.UITest has not been deprecated. DeviceAgent, iOSDeviceManager, Calabash iOS Server, and Calabash Android Test Server are all required by Xamarin.UITest, and as such they are still maintained by Microsoft.

• Trynode -v to see whether you've installed node. I think your node not works.

• nvm is the environment managment for node. If you are using nvm, you should brew install nvm, and use nvm install version-of-node-you-want-to-install to install node, and use nvm use the-version to let node works.

• Whole install chain is:

  • brew install nvm, to install nvm, which is environment/version management for node.

  • nvm install 10.3.0, to install node and npm

  • npm install -g yarn, to install yarn

  • use node -v, npm -v, nvm -v, yarn -v to check if they all works.

It's not installing "default" packages. It is installing the packages in your Gemfile and the dependencies of those packages. If you see that it's installing packages that you didn't specify in your Gemfile, it's because those packages are dependencies of one or more of the packages in your Gemfile.

From the bundle install documentation:

Install the dependencies specified in your Gemfile

...Bundler will fetch all remote sources, resolve dependencies and install all needed gems.

You can use the gem dependency command with the --reverse-dependencies flag to see why a gem was installed. In your case use, for example, gem dependency CFPropertyList --reverse-dependencies to see why the CFPropertyList gem was installed. At the very bottom of the output of the command it will tell you which package required it as a dependency.

You can also check your Gemfile.lock file after you've run bundle install to see the list of packages you have installed and their dependencies. Under the specs header you'll see a list of all the packages that was installed. Some of the packages have a list of indented packages underneath them. Those are the dependencies of the package.

For example, let's see why the to_boolean package was installed:

Can you try

You can use ternary operator assignment:

I'm doing it like so, for UILabels. I don't think it works for UIButtons, for buttons you have to dig a bit deeper in the AppResult[], but it should be doable alone, I've just never had the chance to have text in my buttons when I did UITests.