HOW HORRIBLE bug is this?!?!?! I started experimenting what would happen if I comment out an activity, and so I did - I commented out a RANDOM activity in AndroidManifest.xml and WHAT THE ..., the build SUCCEEDED.
And I just sensed that this bug is SO RIDICULOUS that I should probably remove the comment, but simply add a few blank lines to the manifest file. And VOILA - my build succeeds. WHAT THE !...@#$!!! On Thu, Mar 26, 2009 at 1:59 AM, Stoyan Damov <stoyan.da...@gmail.com> wrote: > On Thu, Mar 26, 2009 at 1:37 AM, Mark Murphy <mmur...@commonsware.com> wrote: >> >> Stoyan Damov wrote: >>> I can't provide a way to reproduce the problem. >> >> 1. Create a fresh project. >> >> 2. Copy your entire res/ tree out of your current project into the fresh >> project. >> >> 3. Try building. > > Will try. If this helps, I will be very much in debt to you. > >> >> If the build crashes, then zip up the new project and attach it to the >> issue. > > You're kidding right? I should attach the source code of my paid application? > >> Or, try winnowing out some resources (e.g., ones you might not >> want to upload) and see if the problem persists -- if the problem goes >> away, it may be tied to the resources you removed. > > I'm saying this for the last time tonight. I haven't added ANY > resources. I've created a class, and used it in another one. That's it > - wrote some code. > >> >> If that doesn't crash, then the problem depends on other stuff (e.g., >> your original project's manifest, other build settings you may have >> enabled) and may truly be difficult to reproduce without uploading your >> original app, which I suspect you may be less than inclined to do. > > No, I haven't enabled anything and I stated that. Perhaps I should be > more clear - everything is vanilla installation - SDK 1.1 with Eclipse > 3.4.1 with no tweaks whatsoever. > The last time I built the code successfully was an hour ago for crying > out loud. Then I wrote some code and aapt crashes. Is it clear now? > >> >> But if you really want this "TERRIBLE BUG" fixed, you really should >> consider at least trying to give the developers steps to reproduce the >> crash. >> > > I very much doubt it WILL get fixed. I can see clearly that no one > wants to fix it. > >> ----------------- > > <snipped guidelines, probably read them all at different times> > > The information I provided (consistent crash address and assembly > around it) should be sufficient to any skilled Windows C++ developer > to find the bug in 10 minutes, provided that the appt tool was built > with Microsoft Visual Studio, or another toolchain, which has the > equivalent of VS's .map files. > > That is why, knowing that Android engineers are indeed skilled, I'm > left with the impression, that they do not want to fix the bug, most > probably because of the fact that I'm again the single guy reporting > the bug. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
