Xamarin is free now right ? but my Xamarin account is still at the 'paid' business level until it runs out - fine - whatever.
However, I work disconnected from the internet quite often, and an incredibly annoying thing has started happening - Xamarin has been refusing to build my projects because it has been unable to verify my account. It does it several times a day, and I have to try and find some way of getting an internet connection in order to build my apps.
I could log out of my Xamarin account, and Xamarin Studio reverts to the 'community' edition, but then I cant use components etc.
Does anyone know why this is suddenly happening, and why Xamarin would refuse to build software even though the tools are free - whether you have a business account or not.
I downloaded Xamarin studio from their website and installed it. After installation I got a Xamarin Studio (old) and a new one. The new one did not had this problem.
Related
It seems that there are issues with running and debugging Tizen .NET (Xamarin Forms) apps on Tizen emulators.
My environment is a Windows 10 machine, with the latest 2004 version. For development I tried both Visual Studio Professional 2019 (v16.6.2) and VS Professional 2017 (v15.9.24) with the VS Tools for Tizen extension.
I am able to deploy the application on the emulator however cannot debug, VS fails with the message Unable to start debugging. The system cannot find the specified file and in the console output I can see an the message [StdErr] error: cannot remove forward listener.
Does anyone have any idea? Is there some magical software combination that I can use to make this work or am I missing something?
I've experienced no end of troubles with Visual Studio Tools for Tizen. I nearly gave up today completely, I've spent weeks just getting it to partially work, and only a day or two of actual development, but finally figured out a few things that might be unique to my system or most likely are just missing in the documentation (which is not rare for Samsung at all).
First up, the emulator issue. I'm assuming you've been through the certificate manager and generated a Samsung certificate (make sure to have installed the extensions in the package manager, Samsung wearable extensions and Samsung certificate extensions then run through and create your Samsung certificate in certificate manager).
So now in the emulator manager try "right" clicking the specific emulator and select allow to install applications. It might now indicate it has installed a certificate. This is a good sign. Also i assume you know not to use HyperV (you can look up how to create a bootloader that can enable you to dual boot windows where HyperV can be disabled in one and enabled in your default).
Assuming that worked and you still can't debug i found that you may need to build the application (clean the build for good measure first - remember this - it can save you often if things don't work when you change something), then click Start without Debugging from visual studio. This should install the application to the device and launch it, fingers crossed. Now if that worked, and your application is now running in emulator or on device, you may find that future attempts now to debug it will work.
The final thing which has nearly made me give up is the update to my watch. It recently updated and i noted the new tizen version reported by the watch is 5.5. So naturally i went ahead and changed the api level to 5.5 and hey presto it all just seemed to work and i could continue as before, debugging and changing things happily. Then i uninstalled the application for a dry run and since then I spent a week trying to figure out why it will not reinstall the application on the emulator or the watch ( (it was a week ago i upgraded to api 5.5 and there were no issues, so that was way down the list of anything that could go wrong). I reinstalled etc, did the whole gamut of things all to no avail. At some point i got it working on the emulator but not the watch, finally today i have it working on both and don't wish to develop anything, i'm spent.
So that final issue was resoled by moving the projects back to api 4.0 and they would now reinstall on my watch and my emulator (use the Start without Debugging trick as well to install it first). Also (my fault - why it worked on emulator but not watch at some point) beware if you have one that is api 4 and one is api 5.5 - which i did while i was testing the above (one is a service the other the ui - they were at different api levels - that will not work on a device - but was happy on the emulator).
If none of that works for you, i'd advise give up, life is too short.
Cheers
I going to login xamarin account in VS 2017
what is this an error?
At this time it is generally no longer necessary to use the old Xamarin account login, so it is recommended to move away from that old login mechanism as soon as you can.
If you are attempting to log in to use the Xamarin Component Store, note that it is recommended to migrate to corresponding NuGet packages at this time: https://blog.xamarin.com/hello-nuget-new-home-xamarin-components/.
If you are logging in to use Xamarin features, note that starting with the Xamarin versions released in March 2016, you no longer need to log in to a Xamarin account to use Xamarin features. Visual Studio will automatically provide Xamarin features based on your Visual Studio subscription level.
If you have a special case where those 2 pieces of information don't resolve the issue, you can reach out via a support incident for further assistance.
I am using Xamarin with Visual Studio 2015.
A few days ago I upgraded my Xamarin-account from the standard/free license to a trial-business license, however since then I decided that I don't need the business license. So now I want to return my account to the normal/free version/license (because the apps built with the trial-business-license only work for 24 hours).
However it is not clear to me at all how to reset the license of my Xamarin-account.
I guess a solution would be to make a new Xamarin-account, however this seems a unsatisfactory solution to me.
Just log out of your Xamarin Account and you should automatically be using the community edition.
If you need your Xamarin account to get components from the component store and this trial stuff is giving you problems. I advise you to contact Xamarin and have them help you clear out your issues.
Make sure that your Visual Studio is up to date.
A little over a year ago, I shelved several projects and went on to do other work. Now I'm finding that I cannot login to my installation of Titanium Studio. I clicked the 'troubleshooting login' link and it pointed me to the Appcelerator page for "Errors Logging In to Studio". There it suggested that I try the following command:
curl -F "username=XXXX" -F "password=YYYY" https://dashboard.appcelerator.com/api/v1/auth/login
When I did so, with my email address (which contains a '-'), it returned:
"Username must be a valid email address." Of course it is a valid email address, and Titanium confirmed it years ago. It is also the same email address I used to access the Appcelerator website.
I changed my email address to one that doesn't include the '-'. Same result.
Has Appcelerator completely locked us out of Titanium Studio?
Any suggestions regarding how to get past this hurdle would be greatly appreciated!! (When I last used Appcelerator Studio, it didn't feel comfortable, so I went back to Titanium. I'm really hoping that I don't have to start over on my apps.)
Thank you in advance!
Rob
Appcelerator discontinued Titanium studio and replaced with Appcelerator Studio with the integrated enterprise features - Arrow, performance and test services, etc for easy development of mobile applications.
You can't use titanium studio login credentials with Appcelerator Studio. However, you can get a free trial access http://www.appcelerator.com/signup/ and get started with Appcelerator Studio.
You can import all your old projects to Appcelerator studio and I don't think you need to put extra effort to start working on this.
Titanium studio was discontinued a while ago, easily over a year now. You do need to use appcelerator studio or your favorite editor if you don't like studio. You can compile and run from the command line.
Also verify your account on their website. It seems they have recently changed some things. Eg. my "forever trial" (which should have been a perpetual Indie, but that's another discussion) seems to be expired recently. So maybe you have to take some additional administrative steps in order to be able to continue working with your apps.
I recently, upgraded to Windows 10 and got Visual Studio 2015 Community hoping to build UWP apps and ASP.Net 5 apps. At first, I installed everything, but ended up skipping / canceling the Windows 8.1 / 10 mobile emulators (my PC can't even run them). After everything was installed, I went to create a new UWP app (C#), and got this error:
Next, I try the same thing, but with JavaScript. It works perfectly! on the same UAP 10.0.0.0 that is supposedly missing. The link it provides is completely useless (it sends me to http:/microsoft.com/en-us) -_-. Oddly, this only happens when I try to use C# or VB.Net, JavaScript UWP apps seem to work fine. What is going on here? Where can I find the real link to the SDK I need?
UPDATE
JavaScript UWP apps will be create just fine, but when I attempt to build, I get:
Error "10.0.0.0" is not a supported value forTargetPlatformVersion.
Please change it on the Project Property page. Test
C:\Program Files (x86) \MSBuild\Microsoft\VisualStudio\v14.\JavaScript\Microsoft.VisualStudio.JavaScript.UAP.targets
This is the download link for the standalone SDK, maybe reinstalling the sdk will fix the problem.
https://dev.windows.com/en-us/downloads/windows-10-sdk
Normally you don't always have to reinstall visual studio when something goes wrong because it takes a lot of time to reinstall again. From your question you skipped/cancel that feature, the first thing to do is go to the control panel and double click on visual studio under programs to Modify the software and enable those features.
In the case, visual studio was working properly before but due to some updates it stopped, go to control panel right click the visual studio version you have under programs to repair.
If the above doesn't work try to reinstall it again. I hope this helps.