Can't update calabash server version - ios

Having a problem updating the Calabash server version.
The problem is that I can run basic tests that check for elements... However, once I try to "touch" buttons calabash returns
RuntimeError: Could not parse response ''; the app has probably crashed
The origin of the problem, I believe, is that my server version is old/incompatible. Not rocket science:
WARN: The server version is not compatible with gem version. Please
update your server.
https://github.com/calabash/calabash-ios/wiki/B1-Updating-your-Calabash-iOS-version
gem version: '0.14.3'
min server version: '0.14.3'
server version: '0.9.169'
The link is outdated, but I followed all steps in https://github.com/calabash/calabash-ios/wiki/Updating-your-Calabash-iOS-version many times.
And still when I check the version it is 0.9.169
irb(main):006:0> server_version['version']
"0.9.169"
Any help would be greatly appreciated!
Thanks

Finally solved it!
It turns out that it all had to do with the calabash component in my Xamarin project.
When I first started experimenting with tests few month ago I added the calabash component (image below)
When I started adding some more tests now, I still had the same component. This component is up to date as far as I can tell. I then tried to remove it and add it again but I could no longer find it.
Turns out that now it is called "Xamarin Test Cloud Agent". I installed that component and DONE.
Hope this helps anyone.

Related

The Cytoscape v3.9.0 application does not start

I have a question regarding Cytoscape. I just downloaded the newest version (v3.9.0) for Windows, but I am not able to open the actual application. Before I used v3.6.1 which ran perfectly fine, but I want to make use of the KEGGscape app which requires Cytoscape v3.8.0 or higher.
I have deleted the previous installation of Cytoscape, as well as made sure the cache was cleared. In addition, I downloaded the correct version of Java (Java version 11) and checked the system requirements with the script available on the website, which summarised: "Succes! You are ready to run Cytoscape 3.9.0."
So I am not exactly sure what I am missing and why it is not starting and hope anyone can help.
Thank you in advance.
Kind regards,
Sorry to hear you are having problems. When you say it doesn't start, does it correctly install, and the application doesn't start when you double-click it, or does the installer never start? If it's the former -- Cytoscape installs, but doesn't start, you could try opening up a console window and run cytoscape.bat from the directory that you installed it. That should give us more information about what the problem is. There should also be a file called framework-cytoscape.log in the CytoscapeConfiguration\3\ directory in your home. That will give us more information also.
-- scooter

Old Version of Newtonsoft.JSon being Used in Docker

I have an application where I have removed my references to the Newtonsoft.Json library and used instead Swashbuckle.ASpNetCore.Newtonsoft version 6.1.4. When I run this locally everything works great. Swagger loads, I am able to query my API with no issues and the world is a nice place. I deploy this code to an Azure Server in Docker and where everything there was working great before, now I have problems. Swagger will not load and my API doesn't work at all, because the application doesn't even start. It would appear that something, somewhere is looking for Newtonsoft.Json version 12.0.0.0 because this is the error I get in the logs.
Any ideas would be greatly appreciated.
In case anyone else has this issue in the future, here is the solution in my case. The Coverlet NuGet package was causing this error. I removed the package and the problem went away.

Uno Platform - xamarin No Virtual method getTargetState()

I recently updated Visual Studio 2019 to 16.9. When it updated- there was a message indicating that the Android SDK was updated. When I go to run the IOS version of my Uno Project- it runs fine. However- when I go to run it on the Android version- I have had a few issues. At first it would not compile- but after doing some web searches I found I needed to reenable AAPT. I am now able to compile it- but I get an exception when I run the app on my android device. It says no virtual method getTargetState()- and then lists the library as the picture shows. I checked Nuget for any package updates and applied them- but still have the same error. It is showing a method missing- that presumably was there earlier. I am not sure how to resolve this- so any help would be appreciated.
I started thinking about what Leo Zhu said above and it made me think- there was no update to the package mentioned. Maybe there was a breaking change in the package that was installed? So- I downgraded it to 2.2.0.3- and it is working again. One point to make is I was using the latest alpha release- so a breaking change is not surprising. I hope this helps someone else that encounters this issue or a similar issue.

How to connect to tfs from VSCode 1.17

I have tried to connect to TFS on my VSCode 1.17.2 by installing Visual studio team services.
Please help me to solve the problem
I test the latest VS Code Version 1.22.2 and everything works as expected.
There is a thread talking about the issue here : https://github.com/Microsoft/vsts-vscode/issues/245
It seems an environment issue based on BrianFarnhill's conclusion:
So based on that I've come to the conclusion that the issue I have
here is nothing related to you guys or your extension, but something
to do with this environment for my customer and it impacting on all
extensions.
So, you can try to troubleshoot the issue based on the discussion in that thread.
If that still not work, you can download the latest VS Code Version 1.22.2, then configure it following the guide here, then check if it works for you.
You can also reference my answer in another thread to do that.

Core Data Versioning, always loading the previous version

I have done lightweight versioning in my project, right now i have two versions and the current version is set to latest one(dataModel 2.xcdatamodel for example). I have followed every steps there in the apple document. But it's crashing every time because the old version is loading(found that after debugging, the new attributes are missing in the entity) after fresh installation.
If i switch back to old version and roll back to current version again then it's running fine. I have deleted the references and added it again but the result is same.
My source code is on git and its very annoying to do that extra effort every time. Please help me to solve this problem.
thanks :)
If you are 100% sure that the new version is loaded, it means that you created the new version, started the app, applied changes to the model, started the app again. To eliminate the possibility of it, just create the 3rd version based on the 2nd version and make it current active. Also make sure you have the automated lightweight migration implemented as per apple manual here
https://developer.apple.com/Library/ios/documentation/Cocoa/Conceptual/CoreDataVersioning/Articles/vmLightweightMigration.html
I am not sure, i guess it is a git/svn problem. We had to work with different versions of Xcode from the very beginning of the project. Whenever we committed to the git, the git found a miss match of Xcode versions(for say i am working with Xcode 5.1 and my team mate working with Xcode 5.0.1, the project was initialised with Xcode 4.1) and set the current core data version to the very older one that is dataModel 1.xcdatamodel in my case. That's why the project was running fine in my side but when my team mate pulled my code from the git and tried to run in his side it crashed everytime because the version was set to older one by the git.
I got this from here. After following the instructions the problem is solved for now.
Thank you all. If you have any better solution please share.

Resources