ContributionsMost RecentMost LikesSolutionsRe: Failed to initialize the TFS API library. Hi thanks! Yes, I have Visual Studio 2019 Enterprise installed with Team Explorer. This worked on my old laptop though I remember it wasn't easy to connect Source Control the first time there either. New laptop is Windows 11 when old one was Windows 10 not sure if that makes a difference. Good to know though about only support to 2019. I was going to upgrade to VS2022 to see if that would help. Failed to initialize the TFS API library. Hello, I got a new laptop recently and did a fresh install of the latest TestComplete. However, I am unable to connect to TFS via this error above every time I click on the "SourceControl" menu option in TestComplete. When I click OK to make the pop up go away, the "Server path" option is greyed out so that I can not select the TFS server. I have the TFS plug in activated. I have TFS chosen as my Source Control option under Options. I have Team Explorer installed through Visual Studio. Those were all solutions to other people having this issue but I seem dead in the water. Screen shot attached. What am I missing? Thanks. v12.6 Issues with Xamarin Forms Android Objects Hello, I was using v12.5 with our Xamarin Forms application and all was moving along. However, I've recently installed v12.6 (and re-instrumented with the new DLLs) and now TestComplete can't see my objects any more. Before, the property "XFControlName" worked like a charm but now this field is only blank on all my objects. I find some distinguishing properties buried way down in "StyleId" but these are shared across controls usually and not always unique. I've worked with the develeoper re-building multiple times now with the same result. Works fine instrumenting in v12.5 but not in v12.6. He made one mention that the injected assembly was like a 12.0.0 version but not sure if that makes a difference. At this point, all signs point to instrumenting Xamarin Forms applications in v12.6 is broken. Attaching two images of the way objects were previously recognized in 12.5 and now how everything is just a "RadEntry" in 12.6. Anyone else have issues with the latest version and Xamarin Forms applications?? ~Chris Re: Support Xamarin.Forms Telerik Controls Haha. Thanks for the feedback. :-) Will do ... Re: Remove product Hello and thanks for your replies - albeit neither one was the answer. I already had the license server targeted in configuration and you can not uninstall a trial license (the original issue). I performed a "Repair" of TestComplete and that seemed to do the trick. Must have been some setting buried down somewhere. Re: Support Xamarin.Forms Telerik Controls Yes of course. Like I said, the application is installed and I see all objects on the Login and Help pages. However, the mobile Telerik controls don't seem to be supported. Anyone else have any success with Telerik Controls in a Xamarin.Forms application? Re: Remove product Hello, Is there a real solution for this issue? Just going to the link provided is of no use. You try that and you get the message that the original user posted about there being no reason to deactivate a trial license. My problem is that I had a trial mobile license. We then purchased a floating license which is properly activated on our license manager server. However, my workstation will not recognize the mobile license on the manager server (it does start up with basic license so I know it sees the license server) and gives me an error that my local mobile license is expired. Thus, I want to remove these trial licenses and hopefully that would clear up the issue. However, nobody has given a proper response how to remove these trial licenses. Support Xamarin.Forms Telerik Controls Hello, We are very excited that TestComplete now supports Xamarin.Forms for Android. However, it appears it's limited to basic Xamarin.Forms controls out of the box. We have several Telerik controls within our Xamarin.Forms app too and I can't drill down into any of these objects. Object Spy just sees it as a huge menu object and the progress stops there so I can't continue within our app. So, as of right now, as excited as I was, we're dead in the water. See attached picture for more info. ~Chris Re: Testcomplete and the new permission system in Android Hello, We are facing the same problem. I see the workaround (thanks!) but I'd prefer to not have to go that route. It would make much more sense (and be easier on all of us!) for TestComplete to add some "Run Mode Parameters" to the Tested Application to allow permission requests or make it a default project setting. Not sure the best implementation route but I figure it would be easier for SmartBear to figure it out than for myself to code a workaround. :) Thanks for listening. ~Chris Re: A recursive call to the "OnUnexpectedWindow" event handler has been detected Was this issue ever resolved? I just ran into this for the first time. I added an event but all it does is send a picture to the log. Is it because I have options checked in the project options as well to close window on unexpected window? Does anyone know if I have to uncheck those and close the window myself if I use a script event? Thanks.