HarmonyOS 鸿蒙Next：Failed to open APK '/data/app/~~rUPbGbTyu0C3aOrvn_o6LQ==/cn.chicore.zgprinting-SEjkNo16lg4EcIxsbBOD1Q==/base.apk'

发布于 1周前 作者 yuanlaile 来自 鸿蒙OS

HarmonyOS 鸿蒙Next：Failed to open APK ‘/data/app/~~rUPbGbTyu0C3aOrvn_o6LQ==/cn.chicore.zgprinting-SEjkNo16lg4EcIxsbBOD1Q==/base.apk’

Failed to open APK '/data/app/~~rUPbGbTyu0C3aOrvn_o6LQ==/cn.chicore.zgprinting-SEjkNo16lg4EcIxsbBOD1Q==/base.apk': I/O error

Log查看出现上面错误，之后的程序运行不对。但UI 能启动。 DevEco studio 4.0 Release, 测试手机是 Mate60 PRO

更多关于HarmonyOS 鸿蒙Next：Failed to open APK '/data/app/~~rUPbGbTyu0C3aOrvn_o6LQ==/cn.chicore.zgprinting-SEjkNo16lg4EcIxsbBOD1Q==/base.apk'的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html

5 回复

你好，场景是啥，这个错误是怎么出现的

更多关于HarmonyOS 鸿蒙Next：Failed to open APK '/data/app/~~rUPbGbTyu0C3aOrvn_o6LQ==/cn.chicore.zgprinting-SEjkNo16lg4EcIxsbBOD1Q==/base.apk'的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


你好 我也遇到这个问题请问解决了吗？

我也遇到了，场景是我用clang编译了一套arm64-v8a的三方库，然后用标准的nativec++模板，只是在cmakelist文件中加了头文件路径和链接了三方库，编译hep过了，真机调试mate50pro,harmonyos4.0,hello.cpp里面就只引用了头文件，还没具体调用

然后就报错

04-19 08:34:59.223 24575-17812/? D 01300/Appkit: [main_thread.cpp(HandleLaunchApplication:968)]MainThread handle launch application, InitCreate End.

04-19 08:34:59.223 24575-17816/? D 01300/Appkit: [main_thread.cpp(ScheduleLaunchAbility:577)]schedule launch ability EntryAbility, type is 1.

04-19 08:34:59.223 24575-17812/? D 01300/Appkit: [main_thread.cpp(HandleLaunchApplication:981)]MainThread handle launch application, CreateResourceManager Start.

04-19 08:34:59.223 24575-17817/? D 01510/IPCWorkThread: 60: proto_=0,policy_=0, name: IPC_2_17817, ret: 0

04-19 08:34:59.231 24549-24549/? D CompatibilityChangeReporter/: Compat change id reported: 171979766; UID 10367; state: ENABLED

04-19 08:34:59.233 24575-17812/? D 01300/Appkit: [main_thread.cpp(HandleLaunchApplication:987)]MainThread handle launch application, CreateResourceManager End.

04-19 08:34:59.233 24575-17812/? D 01300/Ability: [context_deal.cpp(GetBundleManager:226)]ContextDeal::GetBundleManager

04-19 08:34:59.233 24575-17812/? D 01800/SA_CLIENT: GetSystemAbilityWrapper:Waiting for sa 401,

04-19 08:34:59.233 24549-24549/? I Typeface/: fontManager.getInitFontWeightScale:1.0

04-19 08:34:59.233 24575-17812/? D 01800/SA_CLIENT: CheckSystemAbility called, ability id is 401, isExist is 0

04-19 08:34:59.236 24549-24549/? W ActivityThread/: Application com.hufutech.duibi can be debugged on port 8100…

04-19 08:34:59.237 24549-24549/? I LoadedApk/: createSharedLibrariesLoaders::sharedLibraries is null

04-19 08:34:59.237 24549-24549/? W System/  : ClassLoader referenced unknown path: /data/app/~~NcP7TWeTorYQUsl6WRNj5A==/com.hufutech.duibi-QxKw8rcN-GRZa1t3ful46g==/base.apk

04-19 08:34:59.239 24549-24549/? W ziparchive/: Unable to open ‘/data/app/~~NcP7TWeTorYQUsl6WRNj5A==/com.hufutech.duibi-QxKw8rcN-GRZa1t3ful46g==/base.apk’: No such file or directory

04-19 08:34:59.239 24549-24549/? E .hufutech.duib: Failed to open APK ‘/data/app/~~NcP7TWeTorYQUsl6WRNj5A==/com.hufutech.duibi-QxKw8rcN-GRZa1t3ful46g==/base.apk’: I/O error

04-19 08:34:59.240 24549-24570/? I ActivityThread/: Init compatible state: true

04-19 08:34:59.240 24549-24549/? W ResourcesManager/: failed to preload asset path ‘/data/app/~~NcP7TWeTorYQUsl6WRNj5A==/com.hufutech.duibi-QxKw8rcN-GRZa1t3ful46g==/base.apk’

04-19 08:34:59.240 24549-24549/? W ResourcesManager/: java.io.IOException: Failed to load asset path /data/app/~~NcP7TWeTorYQUsl6WRNj5A==/com.hufutech.duibi-QxKw8rcN-GRZa1t3ful46g==/base.apk

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.content.res.ApkAssets.nativeLoad(Native Method)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.content.res.ApkAssets.<init>(ApkAssets.java:305)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.content.res.ApkAssets.loadFromPath(ApkAssets.java:153)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ResourcesManager.loadApkAssets(ResourcesManager.java:507)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ResourcesManager.access$000(ResourcesManager.java:87)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ResourcesManager$ApkAssetsSupplier.load(ResourcesManager.java:203)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ResourcesManager.createApkAssetsSupplierNotLocked(ResourcesManager.java:1061)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ResourcesManager.getResources(ResourcesManager.java:1182)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.LoadedApk.getResources(LoadedApk.java:1488)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ContextImpl.createAppContext(ContextImpl.java:3238)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ContextImpl.createAppContext(ContextImpl.java:3221)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ActivityThread.handleBindApplication(ActivityThread.java:8450)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ActivityThread.access$2800(ActivityThread.java:311)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2889)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.os.Handler.dispatchMessage(Handler.java:117)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.os.Looper.loopOnce(Looper.java:205)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.os.Looper.loop(Looper.java:293)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ActivityThread.loopProcess(ActivityThread.java:9934)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at android.app.ActivityThread.main(ActivityThread.java:9923)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at java.lang.reflect.Method.invoke(Native Method)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:586)

04-19 08:34:59.240 24549-24549/? W ResourcesManager/:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1240)

04-19 08:34:59.240 24549-24549/? W ziparchive/: Unable to open ‘/data/app/~~NcP7TWeTorYQUsl6WRNj5A==/com.hufutech.duibi-QxKw8rcN-GRZa1t3ful46g==/base.apk’: No such file or directory

04-19 08:34:59.240 24549-24549/? E .hufutech.duib: Failed to open APK ‘/data/app/~~NcP7TWeTorYQUsl6WRNj5A==/com.hufutech.duibi-QxKw8rcN-GRZa1t3ful46g==/base.apk’: I/O error

04-19 08:34:59.239 24575-17812/? I 01300/Appkit: [main_thread.cpp(HandleLaunchApplication:1001)]GetBundleInfo, bundleName = com.hufutech.duibi

04-19 08:34:59.242 24549-24570/? D HwFrameworkSecurityPartsFactory/: HwFrameworkSecurityPartsFactory in.

04-19 08:34:59.242 24549-24570/? I HwFrameworkSecurityPartsFactory/: add HwFrameworkSecurityPartsFactory to memory.

在HarmonyOS鸿蒙Next系统中，出现“Failed to open APK ‘/data/app/~~rUPbGbTyu0C3aOrvn_o6LQ==/cn.chicore.zgprinting-SEjkNo16lg4EcIxsbBOD1Q==/base.apk’”错误，通常表示系统无法加载或打开指定的APK文件。可能的原因包括：

  1. APK文件损坏：APK文件在安装或存储过程中可能已损坏，导致系统无法正确解析。
  2. 权限问题：系统可能没有足够的权限访问该APK文件，尤其是在/data/app/目录下。
  3. 路径错误：文件路径可能不正确或已被移动、删除。
  4. 系统兼容性问题：APK可能与当前版本的HarmonyOS不兼容。
  5. 存储问题：设备存储空间不足或存在文件系统错误，导致无法读取APK。

解决此问题需要检查上述可能的原因，并采取相应的修复措施。

在HarmonyOS鸿蒙Next系统中，出现“Failed to open APK”错误通常与APK文件损坏、路径错误或权限问题有关。建议您首先检查APK文件是否完整，确保路径正确。其次，确认应用安装权限是否开启，必要时重新安装应用。如果问题依旧，尝试清理缓存或重启设备。若仍无法解决，建议联系开发者或查阅官方文档获取进一步支持。

回到顶部
AI 助手
你好，我是IT营的 AI 助手
您可以尝试点击下方的快捷入口开启体验！