jensstein

@vi just verifying: are you running 0.3.2-arm, not 0.3.3-arm64? 0.3.3 is the latest release and your device needs the arm64 or the universal version. but looking at the fdroid page...

there is an issue on fdroid's gitlab repo where i mention this problem: https://gitlab.com/fdroid/fdroiddata/issues/1366

the packagers at fdroid are reporting that the universal apk flavour doesn't work. it works for me but i can only test on armv7 devices so could i get some...

okay, could you try this apk and send me the logs (both logcat and oandbackup.log): https://gitlab.com/jensstein/oandbackup/builds/artifacts/oabutils-issue-212/raw/apks/arm64/oandbackup-debug.apk?job=build (we expect it to give the same result - just with some more logging)...

super, please try this: https://gitlab.com/jensstein/oandbackup/-/jobs/76944268/artifacts/file/apks/arm64/oandbackup-debug.apk i expect it to work now. your error on running the command manually seems to be because you didn't run it with an absolute path...

great :)

are you all on arm64 devices? if so then it could be the bug mentioned at the end of this issue: https://gitlab.com/fdroid/fdroiddata/issues/1366 it's an error in the build configuration which...

according to https://developer.android.com/training/permissions/requesting.html this is only supposed to happen "If the device is running Android 6.0 or higher, **and** your app's target SDK is 23 or higher" or if the...

are you running the latest release or have you tried the apk linked here:https://github.com/jensstein/oandbackup/issues/108? could i get you to first verify that the directory listed as dataDir and the apk...

@fajabird is this the released version or the apk from the link in issue 108? @sniperle did you try both backing up and restoring and are both working for you...