Apk editor studio ошибка распаковки apk

This program appears to have an unreliable means of determining the correct version of Java to run. Here is the situation on my PC:

1. I launch APK Editor Studio
2. I click Open APK and pick one.
3. Log messages appear:

Unpacking APK…
Error unpacking APK.

3a. The details for «Error unpacking APK.» are as follows:

Error: Registry key 'SoftwareJavaSoftJava Runtime Environment'CurrentVersion'
has value ‘1.8’, but ‘1.7’ is required.
Error: could not find java.dll
Error: Could not find Java SE Runtime Environment.

How strange. I inspect the program events with Process Monitor. Here’s what I’ve surmised.

1. After clicking Open APK, APK Editor Studio checks the registry path HKLMSOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Optionsjava.exe.
   1a. Is it trying to locate the most current version of java.exe? This bizarre-looking key is very unusual and does not exist on any of my PCs. Why not use the Path and/or JAVA_HOME vars?
   1b. Presumably, APK Editor Studio defaults to some fallback, since the registry key does not exist.
2. APK Editor Studio launches %windir%SysWOW64java.exe.
   2a. Is this a hardcoded default path? No matter where this magic path comes from, it is not a good choice. That particular java.exe doesn’t seem to be dependable. It is merely a copy from the actual Java install location and only exists on one of my PCs. Furthermore, the 1.8 JDK and JRE installers do not overwrite it with the latest java.exe, so it has remained at 1.7 for a long time (on my PC).
3. The launched java.exe (again, version 1.7) checks the registry key HKLMSOFTWAREWow6432NodeJavaSoftJava Runtime EnvironmentCurrentVersion. It reads 1.8, determines it is outdated, and terminates.
4. This is likely the point where APK Editor Studio reports the errors.
   4a. The registry path provided by the APK Editor Studio’s error message ('SoftwareJavaSoftJava Runtime Environment'CurrentVersion') is highly questionable. There is no hive specified. On my PC, the closest match is HKLMSoftwareJavaSoftJava Runtime EnvironmentCurrentVersion, and that key was never even read, as detected by Process Monitor.

This program appears to have an unreliable means of determining the correct version of Java to run. Here is the situation on my PC:

1. I launch APK Editor Studio
2. I click Open APK and pick one.
3. Log messages appear:

Unpacking APK…
Error unpacking APK.

3a. The details for «Error unpacking APK.» are as follows:

Error: Registry key 'SoftwareJavaSoftJava Runtime Environment'CurrentVersion'
has value ‘1.8’, but ‘1.7’ is required.
Error: could not find java.dll
Error: Could not find Java SE Runtime Environment.

How strange. I inspect the program events with Process Monitor. Here’s what I’ve surmised.

1. After clicking Open APK, APK Editor Studio checks the registry path HKLMSOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Optionsjava.exe.
   1a. Is it trying to locate the most current version of java.exe? This bizarre-looking key is very unusual and does not exist on any of my PCs. Why not use the Path and/or JAVA_HOME vars?
   1b. Presumably, APK Editor Studio defaults to some fallback, since the registry key does not exist.
2. APK Editor Studio launches %windir%SysWOW64java.exe.
   2a. Is this a hardcoded default path? No matter where this magic path comes from, it is not a good choice. That particular java.exe doesn’t seem to be dependable. It is merely a copy from the actual Java install location and only exists on one of my PCs. Furthermore, the 1.8 JDK and JRE installers do not overwrite it with the latest java.exe, so it has remained at 1.7 for a long time (on my PC).
3. The launched java.exe (again, version 1.7) checks the registry key HKLMSOFTWAREWow6432NodeJavaSoftJava Runtime EnvironmentCurrentVersion. It reads 1.8, determines it is outdated, and terminates.
4. This is likely the point where APK Editor Studio reports the errors.
   4a. The registry path provided by the APK Editor Studio’s error message ('SoftwareJavaSoftJava Runtime Environment'CurrentVersion') is highly questionable. There is no hive specified. On my PC, the closest match is HKLMSoftwareJavaSoftJava Runtime EnvironmentCurrentVersion, and that key was never even read, as detected by Process Monitor.

Hi,
can’t really figure out how to continue.
Downloaded the APK, edited only the MIN SDK Version number and tried to save.

This is the error log:

I: Using Apktool 2.4.1
I: Copying C:UsersStefanAppDataLocalTempapk-editor-studioapk{b2863aec-bedc-41de-84bd-2cea16aa32a1} classes.dex file…
I: Building resources…W: C:UsersStefanAppDataLocalTempapk-editor-studioapk{b2863aec-bedc-41de-84bd-2cea16aa32a1}resvaluesstyles.xml:13: error: Resource entry AppTheme already has bag item android:statusBarColor.
W: C:UsersStefanAppDataLocalTempapk-editor-studioapk{b2863aec-bedc-41de-84bd-2cea16aa32a1}resvaluesstyles.xml:12: Originally defined here.
W:
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:UsersStefanAppDataLocalTempbrut_util_Jar_48184101202116821.tmp, p, —forced-package-id, 127, —min-sdk-version, 21, —target-sdk-version, 28, —version-code, 20201014, —version-name, 3.1.5, —no-version-vectors, -F, C:UsersStefanAppDataLocalTempAPKTOOL6716385221402879324.tmp, -e, C:UsersStefanAppDataLocalTempAPKTOOL4901568594843723801.tmp, -0, arsc, -I, C:UsersStefanAppDataLocalapk-editor-studioframeworks1.apk, -S, C:UsersStefanAppDataLocalTempapk-editor-studioapk{b2863aec-bedc-41de-84bd-2cea16aa32a1}res, -M, C:UsersStefanAppDataLocalTempapk-editor-studioapk{b2863aec-bedc-41de-84bd-2cea16aa32a1}AndroidManifest.xml]

Any ideas?

Edit

The APK is a signed one which have the problem, while installing directly from android studio causes no issues. (Only using the APK).

After finishing developing the app I tried to generate an APK and give to a friend for a test; He said it’s not working (not installable). So I grapped the phone Motorolla with Android 6.0.1 and tried to debug the problem from the Android Monitor in Android studio and this was the error there :

unable to parse package file android

Then i tried the same APK on the same phone i was using to test (Samsung J3 with 5.1.1 Android version) and got the following error in the logs of Android monitor:

Class not found when unmarshalling:
com.android.packageinstaller.InstallFlowAnalytics

I never had this or something like it before, googled a bit and tried to find an answer on SOF found a couple of answers which none of them worked.

• disabled proGuard
• added android:extractNativeLibs=»true» to manifest
• Increased/Decreased the SDK version

as I said none of these worked, any idea ?

This is my manifest and my Gradle files :

Manifest file

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="my.package.myapp">

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

    <application
        android:icon="@drawable/ice_launder"
        android:label="@string/app_name"
        android:roundIcon="@drawable/ic_launcher_round"
        android:supportsRtl="true"
        android:theme="@style/AppTheme">
        <activity android:name="my.package.MainActivity">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
        <activity android:name="my.package.MoreLikeThisActivity" />
        <activity android:name="my.package.SearchResultActivity" />
        <activity android:name="my.package.LastResultsActivity" />
        <activity android:name="my.package.CompanyDetailsActivity" />
        <activity android:name="my.package.OnboardingActivity"/>
    </application>

</manifest>

Gradle

apply plugin: 'com.android.application'

android {
    compileSdkVersion 26
    buildToolsVersion "26.0.1"
    defaultConfig {
        applicationId "my.package.myapp"
        minSdkVersion 21
        targetSdkVersion 26
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}
repositories {
    mavenCentral() // jcenter() works as well because it pulls from Maven Central
}
dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
        exclude group: 'com.android.support', module: 'support-annotations'
    })
    compile 'com.android.support:appcompat-v7:26.+'
    compile 'com.android.support.constraint:constraint-layout:1.0.2'
    compile 'com.google.code.gson:gson:2.8.1'
    compile 'com.android.volley:volley:1.0.0'
    compile 'com.github.bumptech.glide:glide:4.0.0'
    compile 'com.github.navasmdc:MaterialDesign:1.5@aar'
    compile 'com.ogaclejapan.smarttablayout:library:1.2.1@aar'
    testCompile 'junit:junit:4.12'
    annotationProcessor 'com.github.bumptech.glide:compiler:4.0.0'
}