Check out from Version Control is no longer available in Android Studio - version-control

Suddenly on my Windows 7 Ultimate 64-bit PC Android Studio version 0.5.1 no longer has an "active" Check out from Version Control link on its main page. Any suggestions about how I might get that link to become active again, or what I might have done to cause it to become inactive? I can still see the link, it's just grayed-out now (and it was active a few days ago).
Note: I actually want to check out from a Mercurial repository, not Git.

Sorry about that, I discovered that somehow all of my VCS-related plugins were unchecked - I'm not sure how I did that, but after I checked them again the "Check out from Version Control" link became active again.

Related

Problems with sdk and ndk in unity?

Can't build the project and use unity remote. What to do? Downloaded the latest 2020 LTS with a development package for android
External Tools
Unity hub
When installing a version from the Unity Hub, make sure you have selected the various android packages as you see in the image.
You have shown a link where you show that you did. If the procedure is the one I showed you above, you are not wrong.
Perhaps the problem may be related to Unity 2020.3.15 which in fact I do not find among the available downloads and which was released a few days ago. Maybe they caught some bugs (like maybe what you are showing), and took it out of the releases. Try downloading the 2020.3.14 version from the site (the one I use too), and see if the problem persists.
https://unity3d.com/get-unity/download/archive

Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found

I've read every StackOverflow that I could find on this issue, but I still can't work it out.
I'm trying to deploy an app to actual device (NOT emulator). But I receive the following error when i try to build:
Severity Code Description Project File Line
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
SEHException - External component has thrown an exception. App1
and
Severity Code Description Project File Line
Error Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found. App1
It's worth mentioning that I went from Windows 7 to Windows 10. It's also worth mentioning that my computer was missing the IpOverUsbSvc.exe (not just the registry post, but the actual service was missing). Couldn't find any way to get this back so, so my colleague sent over the .exe and the DLLs and I placed it in it's location. And the service is now running and no longer gives any errors. My device is recognized by the PC, it's running Windows 10 Mobile (but I've also tried with a device running Windows 8.1).
Specs on PC:
Windows 10 Pro (Build 10240)
Using Visual Studio 2015
UWP Tools
Any suggestions to fix my nightmare? Thanks!
Steps that helped me. I have windows 10 mobile build 10581 (and now 10586) installed on phone
Turn off Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Error.
Turn on Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Working.
If you change another device or re-connect you must close VS2015, re-launch and do again!
Finally managed to find a solution to this illusive bug.
It seems that if I didn't have the Windows Phone 8.1 Tools installed I couldn't build to an ARM device (not even Windows 10 Mobile).
So my step to solve this was:
Go to Control Panel -> Programs and Features -> Microsoft Visual Studio ... 2015 -> Modify. And then select the Windows Phone 8.1 Tools.
Pretty pissed that one can't get a reasonable error message when things like this is missing.
I had this issue after updating my device to win10 ver:10.0.10581.0. I tried many things but finally after installing latest sdk and emulators i got it working. You may try installing from this page sdk and emulator:
https://dev.windows.com/en-us/downloads/windows-10-developer-preview
Somehow the new emulators were not visible in vs, they got visible after few restarts and then on device debugging started to work.
But one problem still remain from me that vs crashes after ending debug session with device.
desktop-->my computer--> right click--> management--> service--> start the service Windows Phone IP over USB Transport (IpOverUsbSvc) although maybe the starttype is set as automatic
Seems like there are many issues causing the same error message.
This one worked for me Windows Phone deploy Issue
Essentially you need to remove/uninstall the device from Windows. Then after unplugging and plugging back in, the device and drivers are reinstalled.
I tried many of the suggested solutions to no avail.
After changing the USB-C cable from a USB 3.1 port to a USB 2.0 port on my computer, the error goes away. YMMV
I see it is quite an old post...but I still get this problem. In my case, this happened after I deployed to a second phone I had for testing. After that, VS 2017 now only wants to deploy to that phone and not to the other phone no more. If I start another project, the other phone is recognized and deployable to (listed as device under debug).
Restarting system fixes this...
Also, if I add another project as reference (like a background task) to my project, I will loose the ability to select the devices and emulators under debug. VS 2017 simply then seems to deploy to the last device selected...(really no clue what this is). I have not been able to get the selection of emulators and devices back yet on this one. I only will have the "Start" and "Download new emulators" options. I think this has to do with the fact that VS maybe doesn't know the type (like arm/86/64) of the reference project because it is not set (not needed as this defies the purpose of referencing a project for dynamic references and not the compiled device specific file...)
Hope it helps someone ....
I uninstalled the existing version of the app in device and re-ran it and it worked for me
I got that error for a really simple reason...just opened a new solution I downloaded from GitHub, pressed F5, and got it!
I had left my build configuration in the default "Debug - ARM" setting, when I changed to "Debug - x64" it worked fine!
(Just adding another reason for completeness, not likely to affect your case!)
In case it's helpful for others... I got: DEP6701 bootstrapping failed ... access denied.
Thanks to comments here, I only dev-locked then dev-unlocked my phone (was originally dev-unlocked). Totally works now (took some time installing missing frameworks at first). All good.
Thanks
One more thing could be tried.
Uninstall the existing app if any and then deploy from Visual Studio.
Try on another usb port. It worked

Windows Phone SDK 7.1 Emulator Complete Re-boot Error

I thank you all for reading this lengthy question. It's really important and I will appreciate it if you can assist me :)
The problem -------
I am have been using the Windows 7.1 SDK for about two months now. The emulator has worked without any problem so far. However, today, it began displaying this error (The saved state (Name of File).dess is corrupt. Please delete the corrupted saved state file and then retry). I had not made any significant changes to my project code, or moved any files. I had just added some Visual State animations for a button.
As it suggested, I went ahead to delete the file. I then started debugging again. However, the emulator now opened and displayed the message (Windows Phone Emulator is doing a complete OS reboot). This message was displayed for a very long time. I closed the emulator and project. Since then, I have been unable to use the emulator. I am able to code normally in Visual Studio, but I cannot test my application.
What I have tried ------
I read up on this issue and found many others who faced the same emulator issue. Following their suggestions, I have run one repair of the Windows Phone SDK 7.1. I have also tried uninstalling and then re-installing the SDK 7.1 once.
System Specifications -----
I am using Visual Studio Express 2010 for Windows Phone (Windows 7 64 bit)
I have downloaded the Windows Phone SDK 7.1 from this link: http://go.microsoft.com/fwlink/?LinkId=258412
I have read that this issue might be because of some hardware incompatibility. However, I think my machine is compatible with the emulator. Here is some information.
DirectX Version: DirectX 11
8GB RAM
Driver Model: WDM 1.1
Additional Information:
I have read that installing the 'January Update' might fix this issue. I tried downloading the update from this link: http://www.microsoft.com/enus/download/details.aspx?id=23854
However, the installer said that the update is not compatible with the product/version of the product I am using.
Usually the Repair function of the WP7.1 SDK is enough to fix all the issues. It runs the generation of the saved state of the emulator again.
Please try to delete files in %ProgramData%\Microsoft\XDE folder first (make sure you backup them somewhere else.), then run the emulator. If the emulator runs with a message "Windows Phone Emulator is doing a complete OS boot," let it boot. It takes some time though. This way you will know that the emulator actually can run on your computer. This won't generate a new saved state image, but the emulator should at least load.
Next, try installing WP7.1.1 SDK update from http://www.microsoft.com/en-us/download/details.aspx?id=29233. This update also installs additional 256MB emulator image besides the original 512MB image. It also generates emulator's saved states in the process, potentially fixing the issue.
If everything fails, then try these instructions to fix the saved state of the emulator:
Uninstall WP7.1 SDK
Manually delete these folders:
%ProgramData%\Microsoft\XDE
%LocalAppData%\Microsoft\XDE
Install WP7.1 SDK again.
Install WP7.1.1 SDK update: http://www.microsoft.com/en-us/download/details.aspx?id=29233.
Edit:
Btw, have you tried to reboot your computer? Once this fixed the issue for me.
Alright, I managed to solve this problem.
I reinstalled Windows and downloaded the SDK 7.1 again. The emulator works fine now!
#Paulos, thanks for helping!
I had the same problem for a long time. Try this:
Start up Visual Studio 2010, but before you start debugging, click on the tabs of all the open pages so that all the xaml pages and code behind pages can load.
I noticed it when I opened Visual Studio, but the first open page was a code behind page and not an xaml page, so when I first clicked on the tab of a xaml page, of course, it took some time to load the xaml page into the editor. However, when that and one or more open xaml pages were also loaded, the emulator started without the error message.

ADT Plugin Directory Location for SDK - (MotoDev)

Right now I am setting up Motodev.
Its a Android Development Suite built on Eclipse, created by Motorola.
What is needed is the Android SDK. Check, got that, newest version, everything is set with that.
Now it says I need the ADT Eclipse plugin. Version 20.0.1, currently mine is v18.
I know where to get it, I can easily get it, but I am curious, where should it be installed? Currently I dont have eclipse I am just using MotoDev. But since Motodev asks where the SDK location is, and says my ADT plugin is out of date, I am assuming I have to install the ADT in the SDK directory. But is there somewhere more specific to put it? In a specific folder? or just in the top level of the SDK directory?
Thanks for your time.
Unfortunately, you can't use ADT20 with MOTODEV Studio 4.0. The plugins had some API changes between 18 and 20 that made them incompatible with each other. You will need to roll your SDK back to 19 until we can release a newer version. I wrote about this about a week ago on the MOTODEV Studio blog.
We're done with the engineering work on the new version. It's just a matter of getting the push to the web server scheduled. I expect it to be ready by late next week or early the following week.
Until then, if you need to use ADT20 for Jellybean development, use Eclipse for Mobile Developers plus the MOTODEV Core Plugins (using Help>Eclipse Marketplace). Most of the functionality of the installed product is there, but without the dependency on ADT. See the blog for details on how to set that up.

Google Web Toolkit Developer Plugin supported Firefox versions

How can I find which version of Firefox does the Google Web Toolkit Developer Plugin support ? I can't find it anywhere.
As Firefox now has it small development cycle, it could be nice if Google point us to a page where we could find the supported browsers versions.
For information :
I'm using Firefox version 5.0 with no problem.
I saw on Google Groups people saying that the version 8.0 works too.
Actual version of Firefox is 11.
EDIT 1 :
Last supported version can be found here http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugins/xpcom/prebuilt/update.rdf as suggested by Thomas.
<em:minVersion>3.0</em:minVersion>
<em:maxVersion>16.0.*</em:maxVersion>
EDIT 2 :
The file pointed in EDIT 1 do not seems to exist anymore, so the best shot it looking at the commits logs, here : https://code.google.com/p/google-web-toolkit/source/list
ex:
r11637 update for Firefox 23 / Mac
r11636 update for Firefox 23 on Windows
The DevMode plugin supports all versions of Firefox from 3.0 to 11.0: http://code.google.com/p/google-web-toolkit/source/browse/trunk/plugins/xpcom/prebuilt/update.rdf
There's always some lag after a Firefox version is released, but a preliminary version of the DevMode plugin is generally available "unofficially" from the GWT Google Groups a few days (or even hours) after the Firefox release, pending code review before it graduates to the SVN repository. The problem is that the plugin has to be recompiled against the updated Gecko SDK, which is released a few hours or days after Firefox.
…and then the http://gwt.google.com/missing-plugin/ also lags a few days/hours behind (it hasn't yet been updated for Firefox 11 at the time I write), but the plugin for Firefox 11 can be downloaded from the SVN repository.
Mozilla is hiding their ftp server with "old" releases pretty good.
Here is the URL: ftp://ftp.mozilla.org/pub/firefox/releases/11.0/
In case you are looking more infomation about how to install/remove/features of the google plugin,
you can look at google plugin tutorial