GVKun编程网logo

Android Studio 3.1：找不到org.jetbrains.trove4j：trove4j：20160824（android studio找不到或无法加载主类）

10

对于AndroidStudio3.1：找不到org.jetbrains.trove4j：trove4j：20160824感兴趣的读者，本文将提供您所需要的所有信息，我们将详细讲解androidstud

对于Android Studio 3.1：找不到org.jetbrains.trove4j：trove4j：20160824感兴趣的读者，本文将提供您所需要的所有信息，我们将详细讲解android studio找不到或无法加载主类，并且为您提供关于An Overview of the Android Architecture (Android Studio)、android stdio 编译项目报Error:Failed to find target with hash string ''android-24、Android Studio 3.0 找不到 Android Device Monitor、Android Studio 3.1 EditText StackOverflowError的宝贵知识。

本文目录一览：

Android Studio 3.1：找不到org.jetbrains.trove4j：trove4j：20160824（android studio找不到或无法加载主类）

Android Studio 3.1：找不到org.jetbrains.trove4j：trove4j：20160824（android studio找不到或无法加载主类）

昨天,我将 Android Studio更新为3.1,我收到此错误： 
Could not find org.jetbrains.trove4j:trove4j:20160824.
Searched in the following locations:
    https://repo.maven.apache.org/maven2/org/jetbrains/trove4j/trove4j/20160824/trove4j-20160824.pom
    https://repo.maven.apache.org/maven2/org/jetbrains/trove4j/trove4j/20160824/trove4j-20160824.jar
    https://dl.google.com/dl/android/maven2/org/jetbrains/trove4j/trove4j/20160824/trove4j-20160824.pom
    https://dl.google.com/dl/android/maven2/org/jetbrains/trove4j/trove4j/20160824/trove4j-20160824.jar
required by:
    project :library > com.android.tools.build:gradle:3.0.1 > com.android.tools.build:gradle-core:3.0.1 > com.android.tools.lint:lint:26.0.1 > com.android.tools.lint:lint-checks:26.0.1 > com.android.tools.lint:lint-api:26.0.1 > com.android.tools.external.com-intellij:intellij-core:26.0.1

这是我项目的gradle文件：

buildscript {
    repositories {
        jcenter()
        maven {
            url 'https://maven.google.com/'
            name 'Google'
        }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.1'
//        classpath 'com.google.gms:google-services:1.5.0-beta2'
        classpath 'com.google.gms:google-services:3.1.1'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        jcenter()
        maven { url 'https://maven.fabric.io/public' }

        maven {
            url 'https://maven.google.com/'

        }
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

这是我的gradle-wrapper-properties的distdistributionUrl：

distdistributionUrl=https://services.gradle.org/distributions/gradle-4.4-all.zip

解决方法

尝试在gradle构建中用jcenter()替换所有出现的mavenCentral()

An Overview of the Android Architecture (Android Studio)

An Overview of the Android Architecture (Android Studio)


http://www.techotopia.com/index.php/An_Overview_of_the_Android_Architecture_(Android_Studio)


So far in this book, steps have been taken to set up an environment suitable for the development of Android applications using Android Studio. An initial step has also been taken into the process of application development through the creation of a simple Android Studio application project.

Before delving further into the practical matters of Android application development, however, it is important to gain an understanding of some of the more abstract concepts of both the Android SDK and Android development in general. Gaining a clear understanding of these concepts now will provide a sound foundation on which to build further knowledge.Starting with an overview of the Android architecture in this chapter, and continuing in the next few chapters of this book, the goal is to provide a detailed overview of the fundamentals of Android development.

The Android Software Stack

Android is structured in the form of a software stack comprising applications, an operating system, run-time environment, middleware, services and libraries. This architecture can, perhaps, best be represented visually as outlined in Figure 8-1. Each layer of the stack, and the corresponding elements within each layer, are tightly integrated and carefully tuned to provide the optimal application development and execution environment for mobile devices.


Figure 8-1


The remainder of this chapter will work through the different layers of the Android stack, starting at the bottom with the Linux Kernel.

The Linux Kernel

Positioned at the bottom of the Android software stack, the Linux Kernel provides a level of abstraction between the device hardware and the upper layers of the Android software stack. Based on Linux version 2.6, the kernel provides preemptive multitasking, low-level core system services such as memory, process and power management in addition to providing a network stack and device drivers for hardware such as the device display, Wi-Fi and audio.

The original Linux kernel was developed in 1991 by Linus Torvalds and was combined with a set of tools, utilities and compilers developed by Richard Stallman at the Free Software Foundation to create a full operating system referred to as GNU/Linux. Various Linux distributions have been derived from these basic underpinnings such as Ubuntu and Red Hat Enterprise Linux.

It is important to note, however, that Android only uses the Linux kernel. That said, it is worth noting that the Linux kernel was originally developed for use in traditional computers in the form of desktops and servers. In fact, Linux is now most widely deployed in mission critical enterprise server environments. It is a testament to both the power of today’s mobile devices and the efficiency and performance of the Linux kernel that we find this software at the heart of the Android software stack.

Android Runtime - ART

When an Android app is built within Android Studio it is compiled into an intermediate bytecode format (referred to as DEX format). When the application is subsequently loaded onto the device, the Android Runtime (ART) uses a process referred to as Ahead-of-Time (AOT) compilation to translate the bytecode down to the native instructions required by the device processor. This format is known as Executable and Linkable Format (ELF).

Each time the application is subsequently launched, the ELF executable version is run, resulting in faster application performance and improved battery life.

This contrasts with the Just-in-Time (JIT) compilation approach used in older Android implementations whereby the bytecode was translated within a virtual machine (VM) each time the application was launched.

Android Libraries

In addition to a set of standard Java development libraries (providing support for such general purpose tasks as string handling, networking and file manipulation), the Android development environment also includes the Android Libraries. These are a set of Java-based libraries that are specific to Android development. Examples of libraries in this category include the application framework libraries in addition to those that facilitate user interface building, graphics drawing and database access.

A summary of some key core Android libraries available to the Android developer is as follows:
  • android.app – Provides access to the application model and is the cornerstone of all Android applications.
  • android.content – Facilitates content access, publishing and messaging between applications and application components.
  • android.database – Used to access data published by content providers and includes SQLite database management classes.
  • android.graphics – A low-level 2D graphics drawing API including colors, points, filters, rectangles and canvases.
  • android.hardware – Presents an API providing access to hardware such as the accelerometer and light sensor.
  • android.opengl – A Java interface to the OpenGL ES 3D graphics rendering API.
  • android.os – Provides applications with access to standard operating system services including messages, system services and inter-process communication.
  • android.media – Provides classes to enable playback of audio and video.
  • android.net – A set of APIs providing access to the network stack. Includes android.net.wifi, which provides access to the device’s wireless stack.
  • android.print – Includes a set of classes that enables content to be sent to configured printers from within Android applications.
  • android.provider – A set of convenience classes that provide access to standard Android content provider databases such as those maintained by the calendar and contact applications.
  • android.text – Used to render and manipulate text on a device display.
  • android.util – A set of utility classes for performing tasks such as string and number conversion, XML handling and date and time manipulation.
  • android.view – The fundamental building blocks of application user interfaces.
  • android.widget - A rich collection of pre-built user interface components such as buttons, labels, list views, layout managers, radio buttons etc.
  • android.webkit – A set of classes intended to allow web-browsing capabilities to be built into applications.

Having covered the Java-based libraries in the Android runtime, it is now time to turn our attention to the C/C++ based libraries contained in this layer of the Android software stack.

C/C++ Libraries

The Android runtime core libraries outlined in the preceding section are Java-based and provide the primary APIs for developers writing Android applications. It is important to note, however, that the core libraries do not actually perform much of the actual work and are, in fact, essentially Java “wrappers” around a set of C/C++ based libraries. When making calls, for example, to the android.opengl library to draw 3D graphics on the device display, the library actually ultimately makes calls to the OpenGL ES C++ library which, in turn, works with the underlying Linux kernel to perform the drawing tasks.C/C++ libraries are included to fulfill a wide and diverse range of functions including 2D and 3D graphics drawing, Secure Sockets Layer (SSL) communication, SQLite database management, audio and video playback, bitmap and vector font rendering, display subsystem and graphic layer management and an implementation of the standard C system library (libc).

In practice, the typical Android application developer will access these libraries solely through the Java based Android core library APIs. In the event that direct access to these libraries is needed, this can be achieved using the Android Native Development Kit (NDK), the purpose of which is to call the native methods of non-Java programming languages (such as C and C++) from within Java code using the Java Native Interface (JNI).

Application Framework

The Application Framework is a set of services that collectively form the environment in which Android applications run and are managed. This framework implements the concept that Android applications are constructed from reusable, interchangeable and replaceable components. This concept is taken a step further in that an application is also able to publish its capabilities along with any corresponding data so that they can be found and reused by other applications.

The Android framework includes the following key services:

  • Activity Manager – Controls all aspects of the application lifecycle and activity stack.
  • Content Providers – Allows applications to publish and share data with other applications.
  • Resource Manager – Provides access to non-code embedded resources such as strings, color settings and user interface layouts.
  • Notifications Manager – Allows applications to display alerts and notifications to the user.
  • View System – An extensible set of views used to create application user interfaces.
  • Package Manager – The system by which applications are able to find out information about other applications currently installed on the device.
  • Telephony Manager – Provides information to the application about the telelphony services available on the device such as status and subscriber information.
  • Location Manager – Provides access to the location services allowing an application to receive updates about location changes.

Applications

Located at the top of the Android software stack are the applications. These comprise both the native applications provided with the particular Android implementation (for example web browser and email applications) and the third party applications installed by the user after purchasing the device.

Summary

A good Android development knowledge foundation requires an understanding of the overall architecture of Android. Android is implemented in the form of a software stack architecture consisting of a Linux kernel, a runtime environment and corresponding libraries, an application framework and a set of applications. Applications are predominantly written in Java and compiled down to bytecode format within the Android Studio build environment. When the application is subsequently installed on a device, this bytecode is compiled down by the Android Runtime (ART) to the native format used by the CPU. The key goals of the Android architecture are performance and efficiency, both in application execution and in the implementation of reuse in application design.



android stdio 编译项目报Error:Failed to find target with hash string ''android-24

android stdio 编译项目报Error:Failed to find target with hash string ''android-24

android stdio 编译项目报Error:Failed to find target with hash string ''android-24

 

  • 查看已有的SDK

 

 

 

  • 设置项目的sdk为 25

 

android {

compileSdkVersion 25

buildToolsVersion "25.0.0"

defaultConfig {

applicationId "com.accessibility"

minSdkVersion 14

targetSdkVersion 25

versionCode 1

versionName "1.0"

}

buildTypes {

release {

minifyEnabled false

proguardFiles getDefaultProguardFile(''proguard-android.txt''), ''proguard-rules.pro''

}

}

}

 

编译之后一切OK

 

Android Studio 3.0 找不到 Android Device Monitor

Android Studio 3.0 找不到 Android Device Monitor

因为自 Android Studio 3.0 开始弃用 Android Device Monitor，Android Developers 官网上的原话是：

Android Device Monitor is a standalone tool that provides a UI for several Android app debugging and analysis tools.
However, most components of the Android Device Monitor are deprecated in favor of updated tools available in Android Studio 3.0 and higher. The table below helps you decide which developer tools you should use.

译文：

Android 设备监视器是一个独立的工具，为几个 Android 应用调试和分析工具提供了一个 UI。
但是，大多数 Android 设备监视器组件已弃用，以支持 Android Studio 3.0 和更高版本中提供的更新工具。下表帮助您决定应该使用哪些开发人员工具。

 

这里写图片描述
图 1.Android Developers 关于 Android Device Monitor 的说明页

 

虽然说被 “弃用”，但是不代表不支持，我们还是可以通过其他方式来使用 Android Device Monitor，具体使用方式如下：

在 android-sdk/tools/ 目录的命令行中输入以下内容：

如果你不知道你的 Android SDK 安装在哪个目录，预科可以在 Android Studio 的设置 1 中查看：

 

这里写图片描述
图 2.Android Studio 设置界面
进入 CMD 窗口 2，cd 到目标文件夹 tools 下，然后输入命令 montior：
这里写图片描述
图 3.cmd 界面
接下来，我们就可以看到期待已久的 Android Device Monitor 界面了 3：
这里写图片描述
图 4.Android Device Monitor 界面

Android Studio 3.1 EditText StackOverflowError

Android Studio 3.1 EditText StackOverflowError

更新到Android Studio 3.1后,当EditText处于焦点时我面临异常

E/AndroidRuntime: FATAL EXCEPTION: main
Process: <package>, PID: 18938
java.lang.StackOverflowError: stack size 8MB
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)
    at android.view.inputmethod.InputConnectionWrapper.getTextBeforeCursor(InputConnectionWrapper.java:46)

知道如何解决这个问题吗？

更新：

经过一些研究后,我发现StackOverflowError出现了不同的堆栈跟踪和简单的EditText：

<EditText
android:id="@+id/editText"
android:layout_width="match_parent"
android:layout_height="wrap_content"
app:layout_constraintTop_toTopOf="parent"/>

当我尝试输入任何符号时,我得到：

E/AndroidRuntime: FATAL EXCEPTION: main
Process: <package>, PID: 21122
java.lang.StackOverflowError: stack size 8MB
    at android.view.inputmethod.InputConnectionWrapper.beginBatchEdit(InputConnectionWrapper.java:106)

当我按下时：

E/AndroidRuntime: FATAL EXCEPTION: main
Process: <package>, PID: 21280
java.lang.StackOverflowError: stack size 8MB
    at android.view.inputmethod.InputConnectionWrapper.finishComposingText(InputConnectionWrapper.java:78)

甚至在WebView中输入文本也会导致此错误

在AS 3.0 EditText中工作正常

解决方法:

正如@evi所指出的,有a bug in advanced profiling.

暂时禁用它(编辑配置设置 – >性能分析 – >启用高级性能分析)可防止EditText崩溃

更新：

修复于Android Studio 3.1.1发布

高级分析再次可用！

我们今天的关于Android Studio 3.1：找不到org.jetbrains.trove4j：trove4j：20160824和android studio找不到或无法加载主类的分享就到这里，谢谢您的阅读，如果想了解更多关于An Overview of the Android Architecture (Android Studio)、android stdio 编译项目报Error:Failed to find target with hash string ''android-24、Android Studio 3.0 找不到 Android Device Monitor、Android Studio 3.1 EditText StackOverflowError的相关信息，可以在本站进行搜索。

本文标签：

上一篇在Android中使用setError的RadioGroup空字段检查（android string 空格）

下一篇Android Studio是否支持用于Android UI设计的AngularJS？（android studio支持哪些语言）

相关文章