When installing SeattleOnAndroid, we also install Python via unzipping a tarball that contains the required binaries, libraries, etc. It happens that during install, the "Unpacking Python..." message is followed by "Unpack successful", but when that message is dismissed, the app returns to "Unpacking".
This might be a race between the the pre-installer (trying to detect the magic files it needs to decide whether Python is already installed) and the filesystem (not actually syncing); I haven't seen the loop ever terminate though.
What's unfortunate is that force-stopping the app and then restarting it seemingly makes the installation source Intent disappear. Thus, the install might go through then, but not credit the planned donor or download a custom installer.
When installing SeattleOnAndroid, we also install Python via unzipping a tarball that contains the required binaries, libraries, etc. It happens that during install, the "Unpacking Python..." message is followed by "Unpack successful", but when that message is dismissed, the app returns to "Unpacking".
This might be a race between the the pre-installer (trying to detect the magic files it needs to decide whether Python is already installed) and the filesystem (not actually
syncing); I haven't seen the loop ever terminate though.What's unfortunate is that force-stopping the app and then restarting it seemingly makes the installation source Intent disappear. Thus, the install might go through then, but not credit the planned donor or download a custom installer.