NativeScript / NativeScript/plugins
[imagepicker] Exception if built in --release mode: `Error: java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/documentfile/provider/DocumentFile;`
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- TypeScript
- Estrellas
- 206
- Forks
- 123
- Merge medio
- 2 d 1 h
- PR fusionados (30 d)
- 1
Descripción
Hello,
Issue
I have updated Imagepicker on its latest version (3.0.0 / 3.0.1). It worked well in dev mode, but when built with the --release flag, it cease to work.
I patched webpack to re-enable logs in release mode (drop_console: false), and get this one.
- Code:
const context = Imagepicker.create({
mode: 'multiple',
});
context
.authorize()
.then(() => {
return context.present();
})
.then((selection) => { … })
.catch(function (e: Error) {
console.error('on select image', e.toString(), e.stack, e.cause);
});
- Log:
JS: CONSOLE ERROR: on select image Error: java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/documentfile/provider/DocumentFile; getOrSetHelper(file:///data/data/appid/files/app/vendor.js:2:118868)
JS: at getFile(file:///data/data/appid/files/app/vendor.js:2:128579)
JS: at fromPath(file:///data/data/appid/files/app/vendor.js:2:139398)
JS: at handle(file:///data/data/appid/files/app/vendor.js:2:840987)
JS: at onResult(file:///data/data/appid/files/app/vendor.js:2:842335)
JS: at invokeTask(file:///data/data/appid/files/app/vendor.js:2:1240087)
JS: at onInvokeTask(file:///data/data/appid/files/app/vendor.js:2:1553242)
JS: at invokeTask(file:///data/data/appid/files/app/vendor.js:2:1240008)
JS: at runTask(file:///data/data/appid/files/app/vendor.js:2:1235405)
JS: at invokeTask(file:///data/data/appid/files/app/vendor.js:2:1241184)
JS: at ZoneTask.i.useG.invoke(file:///data/data/appid/files/app/vendor.js:...
Investigation
So I have extracted and compared the 2 produced APK. Here are some differences that looks suspicious to me in the META-INF directory.
- Files that does not appear in
--release
androidx.cardview_cardview.version
androidx.coordinatorlayout_coordinatorlayout.version
androidx.documentfile_documentfile.version # <-- at least this one seems missing for bad reasons
androidx.dynamicanimation_dynamicanimation.version
androidx.legacy_legacy-support-core-utils.version
androidx.localbroadcastmanager_localbroadcastmanager.version
androidx.print_print.version
com.google.android.material_material.version
(These files does not have corresponding entries in MANIFEST.MF.)
- For files that exists in both side, versions does not match
androidx.customview_customview.version has content 1.1.0 in "dev" and 1.0.0 in "release".
androidx.drawerlayout_drawerlayout.version has content 1.1.1 in "dev" and 1.0.0 in "release".
Other informations
Here are some other informations about my config:
package.json extracts
"@nativescript/core": "~8.6.1",
"@nativescript/android": "~8.6.2",
"@nativescript/types": "~8.6.1",
"@nativescript/webpack": "~5.0.18",
app.gradle
android {
compileSdkVersion 33
defaultConfig {
minSdkVersion 21
targetSdkVersion 33
generatedDensities = []
}
aaptOptions {
additionalParameters "--no-version-vectors"
}
}
AndroidManifest.xml extracts
<uses-permission android:name="android.permission.ACCESS_MEDIA_LOCATION"/>
<uses-permission android:name="android.permission.READ_MEDIA_IMAGES" />
<uses-permission android:name="android.permission.READ_MEDIA_VIDEO" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" android:maxSdkVersion="32" tools:replace="android:maxSdkVersion" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="29" tools:replace="android:maxSdkVersion" />
<application
android:name="com.tns.NativeScriptApplication"
android:allowBackup="true"
…
android:requestLegacyExternalStorage="true">
(I first thought it was a permission problem, that's why I have here the old *_EXTERNAL_STORAGE and requestLegacyExternalStorage but I don't think it changed anything. I should probably just revert this!)
Question
I don't really know how these files are generated and what I should try to go forward at this point. Any help appreciated! :-)
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza con el flujo authorize/present de Imagepicker y compara el contenido de META-INF de los APK de dev y release, especialmente androidx.documentfile_documentfile.version. Revisa las versiones de package.json, la configuración de Android en app.gradle y AndroidManifest.xml; se considera terminado cuando se haya identificado y corregido el empaquetado de dependencias exclusivo de release para que DocumentFile se resuelva.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- android, typescript, webpack
- Área
- build-system, mobile
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 30/100