I'm starting to use Android Studio for the first time, and I've run into a snag. When I followed an example and made a helloworld app, no problem. However, I tried to make my own app, which was literally just a Blank Activity, and it can't use Android Tools, or the AVD. I then deleted this project from both AS and in Windows Explorer, and remade it, multiple times. It never fixed the problem. This app was called D&D 5e Character Roller.
I then made another app called DnD 5e Character Roller, which did not have the same problem - it can use AVD and Android Tools.
At this point, I believe that it may simply be due to the ampersand in the name of the first app, but this seems like a weird reason for it to fail - it at least should have told me that would be a problem when I was trying to make the app. Is this a known problem with AS? My searching turned up nothing related to it. If not, what is the problem? If you are at home, can you try to make a similarly named project(with an ampersand) and see if you can use AVD/Android Tools, which would make it a problem with my install of AS.
Thank you.
you should have opened the module setting of your project, there sdk path or gradle version should be missing.
Related
I could use the emulator properly two days ago and now it does not work.
I understand there are many people facing this problem. I have read many of them and tried the solutions stated there (set/change the environment variable of ANDROID_SDK_ROOT & ANDROID_HOME, re-install Android Studio, check avd file, etc.), but did not solve the problem.
My sdk file is in C:\Android\sdk and that is the place where Android SDK Manager in Android Studio found Android SDK as is existing. I have set ANDROID_SDK_ROOT value to C:\Android\sdk. I do not know what else to do. Is there anyone who knows how to resolve this?
I am using Android Studio 3.5.3 on Windows 10.
Thank you in advance for your reply.
I got the same problem recently and got it solved after doing some googling and trying..
It's because the emulator can't read path that containing non-ascii strings properly and in default AVD-specific files are located at C:/Users/%USERNAME%/.android/avd/, but somehow the error log doesn't give right hint and mislead us to focus on ANDROID_SDK_ROOT, so you only need to add ANDROID_AVD_HOME variable with a ascii path like ANDROID_AVD_HOME=D:\Android_avd and restart your IDE. After that your emulator will run properly.
More info https://developer.android.com/studio/command-line/variables
Update: You may need to create a subdirectory .android like C:\test\.android and add a ANDROID_SDK_HOME=C:\test variable, then add a empty .emulator_console_auth_token file which locates at the corresponding floder according to the error log, for me it's C:\Users\鍑濈传绉嬭悓\.emulator_console_auth_token.
After that you should run it without any error, I've already tested it.
https://github.com/flutter/flutter/issues/24988
https://www.reddit.com/r/AndroidQuestions/comments/6of9kp/error_when_starting_emulator_panic_broken_avd/dkgzing/
https://inneka.com/programming/android/panic-broken-avd-system-path-check-your-android_sdk_root-value/
You might not need to setup path. Try to run without path.
when I am trying to run an app in VS code, this message shows up "The named parameter 'home' isn't defined.".
It is a general problem for all flutter projects .flutter doctor says no issues.
I also tried creating a new project from scratch using android studio and Intellij and no progress .it says (theme: and home:) are not identified as named parameters.before that everything was perfectly fine ..please help! :(
As mentioned in the comments, it seems like you may have modified your Flutter SDK (there was previously a bug in the analysis server that made this easy to do accidentally by running quick-fixes).
There's an open issue about having flutter doctor detect this here:
https://github.com/flutter/flutter/issues/25220
For now, running the git clean command Günter gave in the comments from inside your Flutter SDK folder should get things back to normal.
I am developing an iPad application with Xamarin.iOS and MVVMcross. So I have a PCL with my View-Model and my Model, and an iOS project with the view. I use Visual Studio.
Before, I used Xamarin.iOS 6.3.6 beta version, and when I tried to launch the app on the device, an .app file was created and getting it with my Ipad, I could launch the application (impossible to launch directly from Visual Studio).
Yesterday, I uploaded Xamarin.iOS to 6.4.1. On simulator, everything's okay. When I try to launch the application on device, now the app is directly installed but the build stop and the following error appear in the debug output :
Failed to load AOT module '<my PCL>' while running in aot-only mode: doesn't match assembly.
And if I click on my app icon on the device,a black screen appear and disappear immediately.
Does someone know why this error appear?
This looks like something was cached somewhere or not updated correctly.
Here are a few ideas to try:
Delete the app from the device.
Clean & Rebuild your app.
Build & install from Xamarin Studio on your Mac.
Copy the Debug configuration to a new configuration (DebugTest for instance), and run that configuration instead.
I regularly get the same issue here.
The workaround that I use is to switch the platform in the Visual Studio build Configuration Manager to "iPhoneSimulator", run a quick debug session on that, then switch the platform back to "iPhone", and the problem disappears for a while.
Unfortunately I have no intelligent reason as to why this works. It seems to be doing a better job of the "Clean and Rebuild".
After reading a similar bug, I found that clearing the mtbs folder on the OS X host which is located at $HOME/Library/Caches/Xamarin/mtbs/ fixes this problem for me.
I have to do it so frequently I just have a PuTTY session open on my Windows box to clear the folder. I do hope that Xamarin fixes this issue soon.
Make sure Linker Behaviour is set to Don't Link
Clean, rebuild, remove old version from app.
Worked for me at least.
This happened to me after I upgraded to XCode 5/iOS7. I noticed a warning that I hadn't installed XCode Command Line Tools. After I did that I rebuilt the application and it now runs.
I just had this problem and got it to work again by opening the Apple project properties and changing the provisioning profile identity from "Distribution" to "Developer".
My workaround on Mac is to
Close Solution in XS
Quit XS. Command-Q
Reopen it and reopen solution.
After that it usually works again.
I'm on Visual Studio Premium 2012, Version 11.0.50727.1 RTMREL, Windows 7 Enterprise (SP1).
When I right click on the Solution, and click Properties, I get a popup window showing the the null reference exception (Object reference not set to an instance of an object).
When I try the same in 2010, it works fine, opening up the normal solution properties pages, allowing me to set the startup order etc.
Also, in 2012, View -> Property Pages, gives the same result.
Please advise how to solve this, is this a known bug?
UPDATE 1: Tried running devenv /resetsettings as well as devenv /safemode but the problem persists. Also tried it on a new solution, and the problem persists.
UPDATE 2: Seems that disabling any extension, and trying again, sorts out the issue. Re-enabling extension doesn't bring the bug back.
UPDATE 3: Go vote here if you're still having this issue: https://connect.microsoft.com/VisualStudio/feedback/details/763961/cannot-open-property-pages-for-solution
This happened to me as well. If you have ReSharper installed, try disabling it (Tools -> Options -> ReSharper -> General -> Suspend and restart VS2012. If you do not have ReSharper installed, I'm afraid I have no idea.
After seeing some comments here, and running into it myself, it appears that disabling Re-Sharper doesn't always fix the issue. However, if you disable, restart, re-enable 'other' add ons, the issue will eventually go away temporarily. The next time visual studio opens, you will likely be in the same spot.
In my case, the problem was solution-specific. NuGet was causing this error, but not the extension itself but a NuGet package that generated an error on VS load. When I opened NuGet Package Manager Console I saw a big red text with a description of the error. In my case it was T4Scaffolding.Core package, which in turn is a dependency of MVCMailer.
If this is your case, you will probably see what package generates an error in PM Console.
I was encountering this problem on one of my solutions, while it didn't happen for others. The solution causing the trouble didn't do so until I added a certain project to it; after that I could not view the solution's properties anymore or set the startup projects.
Removing the project from the solution didn't solve it, the only way to 'reset' was to create a new solution file and adding all projects one by one to it. This made it work again, until of course I re-added the offending project.
Today the issue was solved for me by updating the NuGet package manager.
This is my experience with the problem:
(Running VS2012 as administrator, hoping that some setting would be sorted out).
I have a solution with two MVC projects and other projects.
If I unload the two MVC projects without restarting VS, the problem is still there. After restarting VS, with the two projects not loading, but showing in Solution explorer, the problem disappears.
Load the two projects back, Solution properties still work, but after a restart the cycle restarts.
NOTE: There is no difference in the projects and solution files when the two MVC projects are not loaded.
I have a Lightswitch 2012 application. It's been working fine for weeks. I made some changes and F5 stopped working. When I click on Start (toolbar) it gives this error message and does nothing.
"The Debugger cannot continue running the process. Unable to start debugging"
Note: It does compile file, it just doesn't run.
If I rollback to an earlier version then it works fine - i.e. it is solution specific.
Here is a video of the current version of my solution with the problem:
http://screencast.com/t/TD4RzLASO
and here is the previous version of the solution from earlier today (and no, I don't know what I changed). As you can see, at least it does something with F5 or Start:
http://screencast.com/t/wX5fRDPz
Rebooting doesn't help... ;)
Maybe you should select start up project which can be started.
Solution Explorer -> On your startable project right mouse click -> Set as Start up Project.
I had this situation when i unloaded my main lightswitch project and other project which is dll has been selected automatically and when i reloaded my main project "The Debugger cannot continue running the process. Unable to start debugging" exception was shown, because debuger was trying to load DLL.
Sometimes you need to start up a project which is compiled as a dll, for instance when testing WCF services.
To do so:
Projects -> 'Set Startup Projects...' -> Select 'Multiple Startup Projects' and set action to 'Start' for each one.
It's a pity you didn't recorded the whole screen, so I can't confirm, but I had the same error a few times...
When this happens, my "output panel" isn't visible and even I try to go on Menu -> View -> Output the panel don't appear.
I need to restart my Visual Studio 2013.
Then my output panel is visible again and everything works fine.
I discovered the cause was an extension which I installed on my Visual Studio.
I encountered this problem after removing some projects from the solution. I wasn't able to pinpoint the exact cause, but closing the solution, deleting the solution file, then opening the project and re-adding supporting projects solved the issue for me. Kind of a sledge hammer, but only takes a minute to do if you don't have a lot of projects.
Also, there are some people that uses a "One Click" Certification in your settings that you'll want to make sure its set up right, re-install or unchecked in-which this case was my problem. I finally got it working myself, but check that too just in case. Again this would be for most Visual Studio Versions only. Im 2013 Ult.