search

TeamVanced / VancedManager

Vanced Installer
GNU General Public License v3.0
8.25k stars 1.14k forks source link

[Bug]: Vanced Manager gives "unable to open file: /data/local/tmp/split_config.arm64_v8a.apk" error when attempting to install #697

Closed KirbyFan102 closed 3 years ago

KirbyFan102 commented 3 years ago

Device

Device: Samsung Galaxy M31 Operating System: Android Android Version: 10

Version

2.6.1

Bug Description

This occurs when trying to install the app. I already uninstalled all the youtube updates, so it should work, right? I'm not sure if the update to the manager might be causing it, or what.

Additional checks

Ante0 commented 3 years ago

Same problem here. I previously had YouTube vanced installed but it seems to have installed regular updates over night, and now I can't reinstall.

Edit: ok so it has nothing to do with play store updating YouTube, that was on me as I previously wiped play stores data so auto update re-enabled. However, the bug is in 2.6.1 manager. 2.6.0 installs both YT and Music fine, you just need to stop the manager update after you have installed 2.6.0 so it doesn't update.

magictomagic commented 3 years ago

Same to me in redmik30 pro with unable to open file: /data/local/tmp/split_config.arm64_v8a.apk

KirbyFan102 commented 3 years ago

Same problem here. I previously had YouTube vanced installed but it seems to have installed regular updates over night, and now I can't reinstall.

Edit: ok so it has nothing to do with play store updating YouTube, that was on me as I previously wiped play stores data so auto update re-enabled. However, the bug is in 2.6.1 manager. 2.6.0 installs both YT and Music fine, you just need to stop the manager update after you have installed 2.6.0 so it doesn't update.

Thank you, installing the previous version of Vanced Manager worked! Hope the vanced team manages to fix whatever bug is present in version 2.6.1.

X1nto commented 3 years ago

I'm investigating the issue, seems to be related to the recent commit 6ed72d3b65b497d89edc02849090473d07404cce, I'll either try to fix it or revert the commit.

X1nto commented 3 years ago

should be fixed with 2.6.2