I adjusted some settings in my last install and messed something up which I could not reverse (not experienced in the inner workings of Android Studio) I started programming in 1985 and have learned to "keep my grubby fingers out from under the hood" - sometimes I forget!!! What can I say?
*SO* I cleaned everything off the PC - SDK, Android, Gradle (all the hidden folders and files) - everything!!! Then I downloaded and installed all the Java SDK's After that I downloaded the latest stable Android Studio (1.2.1.1) and installed that too. Almost a day after starting I am able to create my first project on my shining new Android Studio installation So I do that small thing. *And then I get this:* ExceptionDetails java.lang.NoClassDefFoundError:Could notinitializeclass android.support.v7.internal.widget.ActionBarOverlayLayout at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at android.view.LayoutInflater.inflate (LayoutInflater.java:482) at android.view.LayoutInflater.inflate (LayoutInflater.java:414) at com.android.layoutlib.bridge.bars.BridgeActionBar.<init>(BridgeActionBar. java:56) This is the sort of nonsense that you would expect from a second rate malware infested BS application - NOT software from a Google supported project!!! Microsoft was into this sort of BS back in the day when they were king of the heap - now they are very rapidly losing market share. Somewhere I read that it is because of a Gradle issue... *This should have been picked up BEFORE RELEASE !!!* Someone else said that it is because the "standard" project templates has calls to ActionBarActivity which is depreciated. *WTF??? * *Why does the LATEST RELEASE still have default templates that rely on depreciated stuff???* Doesn't anyone install the "latest release" on a clean VM to test it? How long will that take????? Maybe an hour if your connection is fast??? Or is it a case of rushing to market and *"oh well, we will put out the fires when the users complain"* type of attitude? (refer Microsoft) I have been told by many that Android Studio is the best thing since sliced bread. *My experience: Not So Sure because I have NEVER had it working properly straight out of the box.* I truly believe that the team are doing their best - really do and thanks. But maybe they need an "idiot" to do the final "pre release" test. Testing by someone who knows how to fine tune the *STANDARD INSTALLATION* is no good. Why? Because people like me ALWAYS screw up the "fine tuning" - maybe its genetic - don't know.. Final Pre Release Testing should be done by someone who would just like to use the app "AS IS". And on a "fresh" PC (VM or whatever) *So on to the "built in templates":* I realise that backward compatibility could be an issue BUT MAYBE the templates that have calls to deprecated stuff like ActionBarActivity" should have a comment below them explaining what to use in place of the depreciated call A simple couple of comment lines outlining what is going on *and a link* to a "NOT TECHNICAL" page that explains in English (not technospeak or geekspeak) the options and the issues faced when using each of the options. Come on Dev Team - we the (not so technical) people want to use your product - help us... -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
