For this to work, the Android device needs to be running adbd as root - something that isn't allowed in production builds, which most devices are running.
There's a pretty simple workaround for this (assuming the Android device is rooted). I tried to implement it myself and create a PR, but I couldn't quite get it right.
The workaround would look something like this:
If adb returns an "access denied" error when pulling the save file, try adb root
If that returns "adb cannot run as root in production builds", run adb shell su -c "cp /data/data/jp.co.ponos.battlecatsen/files/SAVE_FILE /sdcard/SAVE_FILE && chmod o+rw /sdcard/SAVE_FILE", then just pull /sdcard/SAVE_FILE to get the save
To upload the save, just push the file to /sdcard/SAVE_FILE and run adb shell su -c "cp /sdcard/SAVE_FILE /data/data/jp.co.ponos.battlecatsen/files/SAVE_FILE"
You may also have to chown /data/data/jp.co.ponos.battlecatsen/files/SAVE_FILE after this - I'm not sure if ADB keeps ownership and permissions when a file is overwritten.
For this to work, the Android device needs to be running adbd as root - something that isn't allowed in production builds, which most devices are running.
There's a pretty simple workaround for this (assuming the Android device is rooted). I tried to implement it myself and create a PR, but I couldn't quite get it right.
The workaround would look something like this:
adb root
adb shell su -c "cp /data/data/jp.co.ponos.battlecatsen/files/SAVE_FILE /sdcard/SAVE_FILE && chmod o+rw /sdcard/SAVE_FILE"
, then just pull /sdcard/SAVE_FILE to get the save/sdcard/SAVE_FILE
and runadb shell su -c "cp /sdcard/SAVE_FILE /data/data/jp.co.ponos.battlecatsen/files/SAVE_FILE"
You may also have to chown /data/data/jp.co.ponos.battlecatsen/files/SAVE_FILE after this - I'm not sure if ADB keeps ownership and permissions when a file is overwritten.