A postinstall data breaks backup due to `set -e` about open-android-backup

[bitstreamout]

Here a first workaround ... guess: tar would also work with this method, but due to the visible error I've choosen the adb method

Simple workaround

---
 backup.sh |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- backup.sh
+++ backup.sh   2022-12-25 14:10:06.041313595 +0000
@@ -74,7 +74,7 @@ function get_file() {
   if [ "$export_method" = 'tar' ]; then
     adb exec-out "tar -c -C $1 $2 2> /dev/null" | pv -p --timer --rate --bytes | tar -C $3 -xf -
   else # we're falling back to adb pull if the variable is empty/unset
-    adb pull $1/$2 $3
+    adb pull $1/$2 $3 || echo "Can not backup $2 ignoring it" 1>&2
   fi
 }
 
@@ -221,7 +221,7 @@ then
       # apk_path=/data/app/~~4wyPu0QoTM3AByZS==/com.whatsapp-iaTC9-W1lyR1FxO==/base.apk
       # apk_base=47856542.apk
       get_file $(dirname $apk_path) $(basename $apk_path) ./backup-tmp/Apps
-      mv ./backup-tmp/Apps/$(basename $apk_path) ./backup-tmp/Apps/$apk_base
+      mv ./backup-tmp/Apps/$(basename $apk_path) ./backup-tmp/Apps/$apk_base || echo "Not found $(basename $apk_path)" 1>&2
     )
   done
 

[mrrfv]

I'll consider adding this workaround.