Android Studio’s APK Analyzer can sometimes open an APK produced by the current project but fail to display AndroidManifest.xml or other entries with “Can not show or open file.” Some builds before Android Studio Quail 4 contained a known regression in the IDE’s APK parsing path.
Representative error
APK Analyzer fails to display
Can not show or open file AndroidManifest.xmlThe APK may appear in Build > Analyze APK, while AndroidManifest.xml, XML resources, JavaScript files, or properties files cannot be opened and the manifest details remain unavailable.
Cause
Google Issue Tracker #534815916 identifies this as an APK Viewer defect in which Android Studio fails to parse even an APK built by the IDE itself. It does not necessarily mean that the app code, signing key, or APK is corrupt. Google has not published a detailed internal root cause, so cache corruption should not be presented as a confirmed explanation.
Affected conditions and versions
- You inspect an APK and select its manifest or another embedded file in APK Analyzer.
- Your IDE predates the fix recorded for issue #534815916, including affected Quail 4 preview builds.
Google lists the fix in Android Studio Quail 4 Canary 3. The fix is also included in the stable Quail 4 line and later releases.
Recommended fix
- Open Help > About, or Android Studio > About Android Studio on macOS, and note the exact build.
- Use Help > Check for Updates and install Android Studio Quail 4 or newer. If you use previews, choose Quail 4 Canary 3 or later.
- Rebuild the APK with the updated environment.
- Open Build > Analyze APK, select the new artifact, and open AndroidManifest.xml.
Workarounds when an IDE update is not possible
Use the Android SDK’s command-line APK Analyzer to inspect the manifest without relying on the affected IDE view.
$ANDROID_SDK_ROOT/cmdline-tools/latest/bin/apkanalyzer manifest print app-release.apkYou can also copy the APK to another workstation running a fixed Android Studio build. Invalidate Caches and re-signing the APK are not documented fixes for this regression and should only be treated as diagnostic experiments.
How to verify the fix
- The APK tree expands normally in APK Analyzer.
- AndroidManifest.xml and its manifest details are displayed.
- The same APK can also be read by apkanalyzer.
Cautions
If only one old APK still fails after upgrading, investigate the artifact itself. Compare it with a freshly built APK; if command-line apkanalyzer also rejects it, regenerate the build output rather than assuming the IDE regression is still present.
Summary
“Can not show or open file AndroidManifest.xml” is a known APK Viewer failure in affected Android Studio builds. Upgrade to Quail 4 or later; when upgrading is temporarily impossible, inspect the manifest with apkanalyzer.
Official references
