Here is the error I'm getting when trying to archive my app for deployment.
This error doesn't show up at any other time. The project builds and runs on emulators and devices without issue. This error has zero context or direction as to where to look to fix it. It also just randomly showed up out of nowhere, last time I built/archived (with zero functional changes) this error did not happen.
Main difference between this archival and the previous one is a newer version of VS 2017. Don't remember exactly the version from before, but am currently on 15.9.4 (stable).
Looking around on the interwebs, I've found that this error seems to have something to do with ObservableCollection's, which there are probably 10-ish in my app. Not really sure what to do here, because this has never been an issue previously, and I'm coming up on a deadline and with the structure of the app, am not in a good position to start making functional changes.
EDIT
I have also cleaned and rebuilt my solution, as well as deleting all bin/obj folders in my xamarin projects. Even tried deleting the .vs folder which can sometimes help. But still no go.
Going to try updating VS to 15.9.5 and see if maybe it was fixed in a release.
EDIT 2
Updating VS 2017 to 15.9.5 made no difference.
EDIT 3
I had my coworker try archiving the exact same project on his machine (running VS 2017: 5.9.3, and it archived fine for him. So far that's the only difference we've been able to find between our environments.
I saw the same problem using VS2017 15.9.9. Even the same code that could be archived a week ago threw the above mentioned error. It seems related to local data in the solution. A "clear" build was not sufficient. However manual deletion of the local obj and bin folders followed by archiving (build is done implicitly) solved the problem for me.
For my part closing Visual studio and deleting the .vs hidden folder did it.
It's actually a fix for many issues using Xamarin.
I had this other issue where I couldn't archive because the build process would just hang and never end. Deleting the .vs folder did it too.
https://github.com/xamarin/xamarin-android/issues/1760
Just go to project property then go to Android options-> Select Advanced then increase the Java Max heap size to 2G/3G -> it's working for me.
Leon Lu's suggestion worked. I don't particularly like it, as it took forever and repairing basically restores you to a base install (no extensions or personalizations). Took about 1.2 hours to complete, but once done I was able to again archive my android application. I guess something went wrong in vs at some point, perhaps during an update. There's no way to tell.
I tried ALL of the ideas above, but had no consistent reliable luck with any of them.
I found that Microsoft has had the problem reported to them (see link below). After a ton of time burn on this, I posted at the link below one way that I've been able to get around this archive-build issue.
Like the other fixes, it's not exactly logical, and nothing that you would think would work, but I've found the process to be repeatable, which is golden for me with tight timelines and having no time for this.
MS Visual Studio Developer Community Problem 507708
Posted on a Saturday morning, a sign of really needing to get around this urgently. I hope it helps you too.
I've recently started android programming, and I'm extremely frustrated to say the least with a lot of things that to me seem simple but are totally holding me back from making any progress. The first of which is the "my first app" hello world that I started a tutorial from http://developer.android.com/training/basics/firstapp/creating-project.html
This tutorial worked fine when I was originally looking into android a while ago. Then when I came back after learning a bunch of java this program will no longer work unless I change the target-sdk to version 10 (I found that solution after extensive searching on this site).
Then I moved on to starting tutorials by thenewboston
All of these work fine as long as I didn't use any new targetsdkversion, so I'm wondering what happened that everywhere I go looking for tutorials I can't find anything that will actually work on the current ADT(4.4W and L are what my eclipse automatically set up) and eclipse (indigo). I'll also get issues saying lint isn't working, or trouble with android SDK content loader when I'm not even doing anything.
I've also found snippets of code example on the developer website that I linked earlier that don't work when implemented either
So, am I missing something, is that just old documentation, or is something up with eclipse and ADT? I'm just so frustrated that everything wants to bug out on me when I'm just trying to follow simple introductory tutorials and I don't even know where to turn for tutorials that I can trust to work..
edit:removed code because it wasn't needed.
To not get blocked What you can do is continue to set "targetVersion as '19'" instead of setting it to 20 or so. Ensure that you've downloaded API19 through SDK Manager and create the AVDs with that targetSDK version for checking you apps.
That way you can proceed ahead with your coding and later when things get resolved by google for API20...you can always comeback to that new version. This way you can follow 'TheNewBoston' and start coding in Android.
I also recommend 'Slidenerd' tutorials over youtube as well for the beginner.
BTW, I've also selected 'Blank Activity / Empty Activity" during the project creation with API19 and been able to move ahead with my coding.
The Google Bug thread about this latest version issue can be tracked here : The google bug
As a beginning developer, I suggest you use API 19. It has been out for a while and is more stable than L or Google Wear.
I am a android beginner. I am going through the book listed in the title. I haven't even made it past the first chapter without running into problems. I have installed the latest version of Eclipse. However, the examples shown in the book are not much like my version. For instance, this main.xml file that's supposed to be in the layout folder is not there. The "New Android Project" dialog box is arranged very differently and the package explorer is called project explorer. Is there a way to get this kind of eclipse in the book? Or do I just have to interpret it best I can? Any help would be much appreciated! This question has been down voted and closed by another user. Could someone please tell me why? I am just trying to get some help.
As different Android APIs(ICS, JB, etc.) are released, they sometimes change the ADT (Android Development Tools) for Eclipse. The ADT is plugin for Eclipse. This plugin is what gives you all those neat buttons in the toolbar and the XML layout interaction.
The book you are reading was designed for Android 4.0(Ice Cream Sandwhich). As of right now, Google has released up to Android 4.2.2(JB 4.2). There has been some significant changes to the ADT going from ICS to JB, but in my opinion, they are for the good. Lots of really neat and new features. Here is a Google resource explaining the different API releases for Android: http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels
I would say continue reading the book as it will teachs you the basics of Android, but when you want to do some in depth coding, that book isn't going to be very useful and you may have to do a little research online. Reason is, Google releases at least two new versions of Android every year. Every version changes, and adds new features. In other words, the book you are reading is already out of date. Android OS development moves way to fast for authors to keep updating their books.
To answer your question, your probably going to have to interpret it the best you can since, most likely, by June/July, Key Lime Pie is going to out, and the ADT your using NOW will be outdated. You should really learn the fundamentals of Android OS and how it works in the background and how processes things. After that, everything else should be easier to learn.
An alternative to the book you are reading is this: http://developer.android.com/training/basics/firstapp/index.html. This is straight from Google and is constantly updated and tweeked. This will be the most updated and useful information on how to write Android apps.
Hope that helps!
I've recently moved from VS to eclipse and am using the intellisense functionality. I came across a tutorial a week ago telling me to add 'source' directories to the android sdk to improve the speed of intellisense.
Anyways i still find it a bit sluggish and i was curious if there was a way to change how it functions from a 'remove suggestions' from the list to a 'highlight the most accurate so far'. This I BELIEVE would solve some of the lag issues.
I just answered a similar question over here:
How do I defeat Eclipse's autocomplete feature?
"There's a bug in Eclipse 3.6.1 that affects code completion (Code Assist). There is supposed to be a patch that will be in 3.6.2 when it's out, but this post from the Android Dev Google group shows a work around that patches 3.6.1. I've tried it and it makes a world of improvement.
https://groups.google.com/d/msg/android-developers/El-6ufT3F7E/uhxmLoUqnQ8J
"
It's called content assist in Eclipse and you can change almost everything in it.
You find it under Eclipse => Preferences => Java => Editor => Content Assist
Doesn't seem like at this point in time it is possible to duplicate this functionality. I'll keep an eye on this answer set should anybody choose to prove me wrong.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have been using Eclipse for Android development and don't have a problem with it (I also use it for Web Service and C++ development under Linux) but I want to give IntelliJ IDEA a go as it appears to have favourable reviews. This is easily possibly now that IDEA 10 has been released with Android support enabled in the Community Edition.
I have looked at IDEA and it looks pretty good to me with the only downside being the lack of UI on .xml file editing (AndroidManifest.xml for example) and the user interface builder provided with ADT 9.0.
Has anyone got experience they can share on IntelliJ IDEA and Android development?
EDIT: Thanks all; I'm sticking with Eclipse as I know it pretty well and it allows me to do pretty much anything (Java-related) I like for free. I shouldn't look a gift horse in the mouth!
The only benefit for me: You code as fast as formula 1 :). Really. If you're used to Resharper in .NET programming, then you will code as fast as in .NET. Even faster.
Bad thing: lack of some Eclipse's tools (browse my questions for details) and it seems that Eclipse's compiler--which you can use from IntelliJ as well--is better. Because of the lack of some tools you are forced to use many 3rd party tools.
The bottom line is: if you don't have problems with Eclipse, then stick to it. I hated Eclipse's slowness and that's why I moved to IntelliJ.
EDIT 23 Jan 2013
IntelliJ has improved a lot. They now have UI visual editor, a great connection to Android SDK and at this moment I can't really think of any feature which Eclipse has and IDEA does not have. What's better, I will say again that IDEA has more features than Eclipse.
EDIT 11 Mar 2014
Again IntelliJ improved. With its visual UI editor for XML layouts and itself being used as the base for Google's Android Studio, its still the best IDE around.
The only flaws for Android developer are IMHO:
it still does not perfectly import dependencies (libraries) so you have to fix things manually
it does not perfectly recognizes other projects (modules) which sometimes you have to add those modules manually
a support for Google Glass does not exist
All this is referring to when importing projects made in Eclipse, which happens very often to anyone working on multiple Android projects.
I have used both, they aren't that different. A lot of it is just what you are used to. Personally, if you aren't having any problems with Eclipse, I would not suggest switching. There are no advantages that are worth the learning curve.
I switched to IDEA for my android development.
Intellisense actually works
IDEA is much faster
The refactoring is nicely done, and the "inspections" catch a lot of places where refactoring would make sense
Things I miss:
The new Layout viewer from Android 3.0. I always modify the layout xml, but it's nice to be able to switch over and get an idea of what it will look like without running the app. I do load up eclipse for this reason when I do heavy layout editing.
Hover documentation. In intelliJ, you have to press ctrl+Q to get the javaDoc of an existing method call (vs intellisense popping up as you code).
I know eclipse is free, but come on, I don’t know how people actually use it to build software. I like open source as much as the next guy, I just like “high quality open source” which may be an oxymoron.
I want to get work done and not fight the tool no matter how free it is.
After 2 years of Android Development on Eclipse I finally give up. I hate it because:
1. Eclipse is slow.
2. Search and autocomplete is poor.
3. Require big among of memory.
4. Crashing and hanging constantly.
5. Correct or incorrect way of closing Eclipse may cause workspace and settings crash.
Eclipse: reminding me every time I use why I normally don't use it. -
Romain Guy
You can check some of interesting IntelliJ IDEA features here
Google has introduced new intellij-based IDE for android development (if you dont want to pay for intellij), you can find more info here http://developer.android.com/sdk/installing/studio.html
I am interested in this question too. For me, eclipse starts to be slow as more plugins installed: CDT, aptana, pydev, ADT....
IDEA seems like a light-weighted and interesting alternative. For the lacking of layout xml editing, you may do it with http://www.droiddraw.org/, or its desktop version. Pretty amazingly easy after reading the droiddraw tutorials.
I haven't got enough experience with IDEA, so cannot help a lot. Hope more people cast light on this issue.
Thanks,
Frank
I think Eclipse has all the features that an IDE should have these days.
But from my point of view it does everything on the wrong way (I am a Visual Studio fan).
After I tried IDEA, I had to realize that it can be customized to act nearly the same as VS, so it IS a very good IDE.
And the version 12 has UI editor for Android.
I can say that try to compare their IntelliSense (or whatever you call it), the debugger (including watches) and the editor. Much more better, smarter, faster for a daily use.
IDEA ultimate is not free, but if you would like to make money with programming I think you can make it easier with professional tools.
I would never pay for Eclipse.
As a new IDEA user I found the IDE to be somewhat overwhelming at first. The IDE contains more options than I thought possible and can bring into question - "Just how many checkboxes can you fit on a screen". Once the shock passed and I was able to complete a small project, I'm in love. Sorry Eclipse, but you were kind of flakey and would have unpredictable behavior. IDEA is rock solid.
As a programmer I want rock solid tools and sometimes the phrase "you get what you pay for" is valid.
Google's Android Studio is built on top of IDEA, assuming that it will be the "Official" developer tool when it reaches 1.0, it might be worth getting up to speed by learning IDEA.
It also has a "dark" theme built in so you don't have to mess around with Eclipse plugins.
Quick comparison
between eclipse 4.3.2 and intellij 13.0.2:
I will refer to intellij idea as I as an abbreviation below (e.g. I12 means intellij idea version 12)
Both are fine .
Pro Intellij are:
Faster compiler mode:(introduced in I12) exactly as with eclipse, now Intellij compiles everything continuously in the background and shows you files that doesn't compile with red zigzag. Exactly as Eclipse but less heavier and more responsive .
Android UI editor: (introduced in I11) even better than the one in eclipse ADT plugin: it shows more properties as android:layout_span ,i.e. Advanced properties that are hidden in Eclipse UI editor forcing you to edit them from Layout XML , can be easily editted from Intellij UI editor. Also while Eclipse UI editor hangs when selecting multiple components then editting one common property , this is extremely fast and easy in Intellij UI editor. It also can show you a preview while editing XML code, which you can't do in eclipse.
Best content assist : it auto completes when you enter next limiter (space or semicolon or brackets or dot ) you don't have to press enter then press the next limiter, exactly as Visual Studio Intellisense. Also Intellij puts most relevant result on top. another feature introduced in I12 is that it searches if matches are available from the middle not from start.
Fast: intellij is much faster than Eclipse. Eclipse 3.8 is slow and Eclipse 4.2 is even slower due some bugs, that were fixed gradually in Eclipse 4.2.1 and 4.2.2 releases .
more stable than eclipse. In Eclipse, A row of Layout properties editor may stick on screen while you scroll, a very bad UI glitch. Also Eclipse x64 crashes very frequently as compared with eclipse x86 or Intellij, may be because of bugs in JDK x64.
Add framework support:( New in I13) a wizard to add framework support
As of intellij 13, it has wizard like (New->Android-> Android Activity) as that in eclipse adt plugin , maybe the only difference is the intellij wizard may force you to a higher minimum SDK version, while eclipse doesn't .
Con Intellij:
Gradle: Android project wizard: (New in I13) when you create an app you can define in a gui wizerd : min sdk , target sdk , icons and theme (all these fills in the gap between eclipse and previous Is) and support mode ( an advantage over eclipse). Although this might be considered an advantage, gradle added so many errors to managing an android project, that intellij became not usable as before in intellij 12. most errors require either changing configuration and updating a maven repo from internet , or navigating to a folder and running a command from terminal.
Doesn't support NDK (Native Development Kit for development in C/C++)
I have been using IDEA for professional Android development for almost a year, it is much better than Eclipse because:
The IDE is much faster and stable
Excellent interface designer
Other good enhancements such color picker in XML, creating resource directories and creating String resources.
IDEA is much better for Android development and you will increase your productivity for sure, Google knows this, that is why Android Studio is built on top of IDEA