Android-Studio upgraded from 0.1.9 to 0.2.0 causing gradle build errors now

前端 未结 7 540
粉色の甜心
粉色の甜心 2020-12-02 18:57

My current project had been building with Gradle just fine, since I created it (about a month ago), after acquiring Android-Studio. [I installed some earlier updates to Andr

7条回答
  •  生来不讨喜
    2020-12-02 19:10

    Ok, I finally resolved this, by completely de-installing Android-Studio, and then installing the latest (0.2.0) from scratch.

    EDIT: I also had to use the Android SDK-Manager, and install the component in the 'Extras' section called the Android Support Repository (as mentioned elsewhere).

    Note: This does NOT fix my old existing project...that one still will not build, as indicated above.

    But, it DOES solve the issue of now being able to at least create NEW projects going forward, that build ok using 'Gradle'. (So, basically, I re-created my proj from scratch under a new name, and copied all my code and project xml-files, etc, from the old project, into the newly-created one.)

    [As an aside: I've got an idea, Google! Why don't you refer to versions of Android-Studio using numbers like 0.1.9 and 0.2.0, but then when users click on 'About' menu item, or search elsewhere for what version they are running, you could baffle them with crap like 'the July 11th build' or aka, some build number with 6 or 8 digits of numbering, and make them wonder what version they actually have! That will keep the developers guessing...really will sort the wheat from the chaff, etc.]

    For example, I originally installed a kit named: android-studio-bundle-130.687321-windows.exe

    Today, I got the "0.2.0" kit???, and it has a name like: android-studio-bundle-130.737825-windows.exe

    Yep, this version #ing system is about as clear as mud.
    Why bother with the illusion of version#s, when you don't use them!!!???

提交回复
热议问题