Tag Archives: IDE

[Solved] org.gradle.api.internal.plugins.PluginApplicationException: Failed to apply plugin

This problem sometimes occurs when opening Android files written by others:

Caused by: org.gradle.api.internal.plugins.PluginApplicationException: Failed to apply plugin [id 'com.android.internal.application']

The solution is as follows:

1. In Project view mode, select gradle.properties file.

2. On the last line (or any line in the file), enter the following code.

android.overridePathCheck=true

This line of code means “overlay path checking”.

3. Then click ‘Sync Now’ in the upper right corner and wait a few seconds to solve the problem.

[Solved] Android-android studio apk Install Error: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED

I simply wrote a program today and found that it could not run all the time, prompting that the installation failed on the physical device

INSTALL_PARSE_FAILED_MANIFEST_MALFORMED
Installation failed due to: ‘null’

After checking on the Internet, most of the brothers said that it was a problem with the test mark, so just add it

android:testOnly="false"

But there are still problems after trying

Another brother said that this problem is related to the manifest file. It may be that there is a problem with the configuration of the manifest file. Therefore, I checked it from here. However, I was also very curious about how a hello world program has a configuration problem. I didn’t see any exceptions in the xml. I went to the apk generation directory to directly try to install it:

adb install -r -d a.apk

here I saw the error messages:

adb: failed to install app-debug.apk: Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED: Failed parse during installPackageLI: /data/app/vmdl631790294.tmp/base.apk (at Binary XML file line #20): com.leonard.goot.MainActivity: Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present]

Find the problem, because the activity does not have the export property caused by the modification can be installed after debugging, Done!

[Solved] Error launching IDEA: Failed to create JVM. JVM Path…

Error launching IDEA

This error is actually a modification of the /idea64.exe.vmoptions file, but you add something he can not recognize

Solution:

The solution is very simple to \idea64.exe.vmoptions in your added delete on it!

But note that in case you really do not know what you have added, you can add a pause to the end of the idea.bat file, you can know is not recognized that sentence

Then run it, find it and go to \idea64.exe.vmoptions file to delete it.

As for how to find this file, I learned is in the idea installation path of the bin, and then after a series of operations, even with other people’s configuration directly replace the file did not work, and finally Kung Fu does not bear any responsibility, in my efforts to learn that there is an identical file in the C disk, we need to modify the C disk files

[Solved] Message from debugger: debug-server is x86_64 binary running in translation, attached failed.

Leave a reply

After transferring an Xcode project from an Intel Mac to an Apple M1 chip, code compiles successfully on the M1 chip, but displays the following error at runtime：

Message from debugger: debug-server is x86_64 binary running in translation, attached failed.

insert image description here

Solution：

I have checked Xcode’s “Open with Rosettea” option, but it still doesn’t work successfully on the M1 chip. So this program doesn’t work for me. . .
insert image description here
Valid solutions：
Find Edit Scheme -> Run -> Debug excitable, Cancel this option to run successfully.
insert image description here
Note: If this method fails to Solve your problem, Please refer to the link below：
debugserver is x86_64 binary running in translation, attached failed. Could not attach to pid

[2022 New Solution] SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder

Leave a reply

SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder

Problem introduction：

insert image description here

Problem Analysis：

According to the error message， we can know that the cause of the error is “failed to load the class file org.slf4j.impl.StaticLoggerBinder”, and the error mainly lies in the jar package of slf4j.

Official website explanation：

This error is reported when the org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. This happens when no appropriate SLF4J binding could be found on the class path. Placing one (and only one) of slf4j-nop .jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path should solve the problem.

 

Solution：

Add a dependency configuration of one of the above package files to the pom file of the Maven project, as follows：

<dependency span>>
  <groupId>org.slf4j</groupId>
  <artifactId>slf4j-nop</artifactId>
  <version>1.7.2</version>
</dependency>

Over!!!

[Solved] Android Compile and Package Error: Invalid keystore format

Leave a reply

Problem description

Running an old open source project, compiles the following error.

java.io.IOException: Invalid keystore format
Execution failed for task ':app:transformDexWithInstantRunDependenciesApkForDebug'.
> com.android.build.api.transform.TransformException: com.android.ide.common.signing.KeytoolException: Failed to read key AndroidDebugKey from store "C:\Users\a do\.android\debug.keystore": Invalide keystore format

Solution

According to the error message, there is a problem with the debug signature format.

We only need to open the c drive, in the current user’s directory, there is a .android directory, delete the debug.keystore inside.

If it prompts that the process is occupied, exit Android Studio first. Then delete it again.

Finally re-running the project, will automatically generate debug.keystore.

[Solved] Android Studio 3.0 Error: Error: INSTALL_FAILED_TEST_ONLY

Reason: After Android Studio 3.0, when generating debug apk, the android:testOnly=”true” attribute is automatically added in the application tag of the apk’s manifest file. android:testOnly=” true” This tag was originally used for testing, so packages with this tag cannot be installed in general, and need to be installed in a special way (by adding the -t flag).

Solution:

Method 1: Set: android.injected.testOnly=false in the global configuration gradle.properties file in the project

Method 2: Add -t property: adb install -t app-debug.apk

 

[Solved] VsCode + gfortran Compiler Error: error: ld returned 1 exit status

After a file is executed in the VsCode control panel, if a new f90 file is created (multiple programs share the same panel port), an error message as shown in the figure will often appear

Solution:
The tasks.json file should add the presentation property `

{
    "version": "2.0.0",
    "tasks": [
      {
        "label": "compile",
        "type": "shell",
        "command": "gfortran",
        "args": [
          "-g",
          "${file}",
          "-o",
          "${workspaceRoot}\\${fileBasenameNoExtension}.exe"
        ],
        "problemMatcher": [],
        "group": {
          "kind": "build",
          "isDefault": true
        },
        "presentation": {
          "echo": true,
          "reveal": "always",
          "focus": false,
          "panel": "new", //Here shared means shared, after changing to new each process creates a new port
          "showReuseMessage": true,
          "clear": false
        }
      }
    ]
  }

“Shared” indicates sharing. After changing to new, each process creates a new port.

[Solved] Android Studio Generate APK Error: error_prone_annotations.jar (com.google.errorprone:error)

Android Studio failed to generate apk error:

Could not download error_prone_annotations.jar (com.google.errorprone:error)

 

Solution:

Modify the buildscript and allprojects in build.gradle file of your project:

google()jcenter()

to

maven { url ‘https://maven.aliyun.com/repository/google’ }maven { url ‘https://maven.aliyun.com/repository/jcenter’ }maven { url ‘http://maven.aliyun.com/nexus/content/groups/public’ }

Done!

[Solved] Idea Failed to recognize Maven and Project Error

All the data packages of the open project are red, and the startup reports an error. Don’t panic when you encounter such a situation.

(this is only useful for the downloaded jar package project. If the project is newly opened, you need to download the Maven file)

click File in idea > Invalideate Caches…/restart clear cache and restart

Clear and restart the project