Version 0.0.16-ALPHA-3 Fails to generate Proof

[ingfabby]

Tested on:
Galaxy S8 - Android 9
Steps followed:
1.- Installed the last release (0.0.16-ALPHA-3), and enable it to run in the background
2.-Took a set of pictures and videos, and waited 2 days.
3.- Selected the videos and pictures taken for the testing.
4.-Tap on the share icon
5.-Selected ProofMode
6.-Got the screen that reads " No Proof exists yet"
7.-Selected Generate proof
8.- Selected "Basic" on the next screen.
9.-Got the message " We were unable to generate proof for this file"
10.- I got the same result when I selected just 1 file

Galaxy S20 -Android 12
Steps followed:
1.- Installed the last release (0.0.16-ALPHA-3), and enable it to run in the background
2.-Took a set of pictures and videos, and waited 2 days.
3.- Selected the videos and pictures taken for the testing.
4.-Tap on the share icon
5.-Selected ProofMode
6.-Got the screen that reads " No Proof exists yet"
7.-Selected Generate proof
8.- Selected "Basic" on the next screen.
9.-Got the message " We were unable to generate proof for this file"
10.- I got the same result when I selected just 1 file

Redmi 9A - Android 10
Steps followed:
1.- Installed the last release (0.0.16-ALPHA-3), and enable it to run in the background
2.-Took a set of pictures and videos, and waited 2 days.
3.- Selected the videos and pictures taken for the testing.
4.-Tap on the share icon
5.-Selected ProofMode
6.-A bubble message appears that says " Sharing on Share Proof" for a few seconds and then nothin happens.
7.- I got the same result when I selected just 1 file

[n8fr8]

Seems like all of your tests were bulk/multiple photos and videos?

Can you try to test a single photo or single video on these devices to see if it works?

[n8fr8]

Are you sharing the photos from Google Photos or another Gallery / Photo app?

[n8fr8]

Can you check permissions for the Proofmode app on all phones? You should have Camera, Phone and Storage granted, and maybe location.

[ingfabby]

• I did all the testing with single files and bulk files, in both cases the result was the same.
• I am using the gallery to select the files I want to share.
• On the Galaxy S8 the permissions were enabled and the device still failed to generate a proof.
• On the Galaxy S20 the permissions were disabled, and the app produced proof files after I enabled the permissions.

[n8fr8]

Working on a fix for handling when permissions are disabled properly. It shouldn't fail!

[ingfabby]

06-14 17:34:29.376 3041 3041 I SurfaceFlinger: Device | 0x7e097d5780 | 0002 | RGBA_8888 | 0.0 0.0 1080.0 2220.0 | 0 0 1080 2220 | org.witness.proofmode/org.witness.proofmode.ShareProofActivity[8119]#0
06-14 17:34:29.376 3041 3041 I SurfaceFlinger: Device | 0x7e097d5f00 | 0002 | RGBA_8888 | 0.0 0.0 1080.0 2220.0 | 0 0 1080 2220 | Splash Screen org.witness.proofmode[8119]#0
06-14 17:34:29.376 3041 3041 I SurfaceFlinger: Device | 0x7e097d5000 | 0000 | RGBA_8888 | 0.0 1.0 1080.0 72.0 | 0 0 1080 71 | StatusBar[4152]#0
06-14 17:34:29.376 3041 3041 I SurfaceFlinger: Device | 0x7e0b622780 | 0000 | RGBA_8888 | 0.0 0.0 67.0 416.0 | 1013 1560 1080 1976 | com.samsung.android.app.cocktailbars[...]arservice.CocktailBarService[8650]#0
06-14 17:34:29.376 3041 3041 I SurfaceFlinger: Device | 0x7e0b622600 | 0000 | RGBA_8888 | 0.0 0.0 1080.0 144.0 | 0 2076 1080 2220 | NavigationBar[4152]#0
06-14 17:34:29.376 3041 3041 I SurfaceFlinger:
06-14 17:34:29.377 17517 17580 D OpenGLRenderer: eglDestroySurface = 0x7b335c2a00, 0x7b39322000
06-14 17:34:29.377 3041 4730 W SurfaceFlinger: Attempting to set client state on removed layer: Dim Layer for - Task=16638#0 [s.what : 10000]
06-14 17:34:29.377 3041 4730 W SurfaceFlinger: Attempting to destroy on removed layer: Dim Layer for - Task=16638#0
06-14 17:34:29.377 3041 4730 I SurfaceFlinger: id=1579 Removed Surface(name=Dim Layer for - Task=16638)/@0xe136afb - animation-leash#0 (1/57)
06-14 17:34:29.379 13392 13392 D ViewRootImpl@2b58723[GalleryActivity]: Relayout returned: old=[0,0][1080,2220] new=[0,0][1080,2220] result=0x1 surface={valid=false 0} changed=false
06-14 17:34:29.381 3564 4190 V WindowManager: Relayout Window{cc84ae7 u0 android/com.android.internal.app.ChooserActivity}: viewVisibility=8 req=1080x2220 {(0,0)(fillxfill) sim={adjust=nothing forwardNavigation} ty=BASE_APPLICATION fmt=TRANSPARENT wanim=0x10302ec
06-14 17:34:29.381 3564 4190 V WindowManager: fl=DIM_BEHIND LAYOUT_IN_SCREEN FULLSCREEN LAYOUT_INSET_DECOR SPLIT_TOUCH HARDWARE_ACCELERATED DRAWS_SYSTEM_BAR_BACKGROUNDS
06-14 17:34:29.381 3564 4190 V WindowManager: pfl=FORCE_DRAW_STATUS_BAR_BACKGROUND remains{ 0x1000000 }
06-14 17:34:29.381 3564 4190 V WindowManager: vsysui=LIGHT_NAVIGATION_BAR naviIconColor=0}
06-14 17:34:29.382 3564 4190 E WindowManager: win=Window{cc84ae7 u0 android/com.android.internal.app.ChooserActivity} destroySurfaces: appStopped=false win.mWindowRemovalAllowed=false win.mRemoveOnExit=false win.mViewVisibility=8 caller=com.android.server.wm.WindowManagerService.tryStartExitingAnimation:2803 com.android.server.wm.WindowManagerService.relayoutWindow:2501 com.android.server.wm.Session.relayoutForTranslate:302 android.view.IWindowSession$Stub.onTransact:518 com.android.server.wm.Session.onTransact:186 android.os.Binder.execTransact:739
06-14 17:34:29.382 3564 4190 I WindowManager: Destroying surface Surface(name=android/com.android.internal.app.ChooserActivity[17517])/@0xdc47694 called by com.android.server.wm.WindowStateAnimator.destroySurface:1880 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:838 com.android.server.wm.WindowState.destroySurfaceUnchecked:3823 com.android.server.wm.WindowState.destroySurface:3804 com.android.server.wm.WindowManagerService.tryStartExitingAnimation:2803 com.android.server.wm.WindowManagerService.relayoutWindow:2501 com.android.server.wm.Session.relayoutForTranslate:302 android.view.IWindowSession$Stub.onTransact:518