Konloch / Konloch/bytecode-viewer
error log
- Dominant language
- Java
- Stars
- 15.6k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Please send this error log to https://github.com/Konloch/bytecode-viewer/issues or Konloch at https://the.bytecode.club or konloch@gmail.com
If you hold appropriate legal rights to the relevant class/jar/apk file please include that as well.
Bytecode Viewer Version: 2.13.2 [Fat Jar], OS: Windows 10, Java: 1.8.0_491
java.nio.file.NoSuchFileException: C:\Users\WDAGUtilityAccount\.Bytecode-Viewer\bcv_temp\mrGIwNulEQEGHTTRDoIPldiflKnswDiL.apk
at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(Unknown Source)
at java.nio.file.Files.newByteChannel(Unknown Source)
at java.nio.file.Files.newByteChannel(Unknown Source)
at java.nio.file.Files.readAllBytes(Unknown Source)
at com.googlecode.d2j.dex.Dex2jar.from(Dex2jar.java:404)
at the.bytecode.club.bytecodeviewer.util.apk2Jar.Dex2Jar.dex2File(Dex2Jar.java:73)
at the.bytecode.club.bytecodeviewer.util.apk2Jar.Dex2Jar.resourceContainerFromApkImpl(Dex2Jar.java:47)
at the.bytecode.club.bytecodeviewer.util.apk2Jar.Apk2Jar.resourceContainerFromApk(Apk2Jar.java:23)
at the.bytecode.club.bytecodeviewer.resources.importing.impl.APKResourceImporter.open(APKResourceImporter.java:59)
at the.bytecode.club.bytecodeviewer.resources.importing.ImportResource.importKnownFile(ImportResource.java:91)
at the.bytecode.club.bytecodeviewer.resources.importing.ImportResource.run(ImportResource.java:63)
at java.lang.Thread.run(Unknown Source)
Contributor guide
Research direction
Start at the APK import path in APKResourceImporter.java:59, then follow Apk2Jar.java:23 and Dex2Jar.java:47 and :73 where the missing temporary APK is read. Reproduce with the affected APK if it can be obtained and determine why the temporary file is unavailable; done means the reported failure has a clear, verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev, reverse-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100