You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the app contains multiple proofs, the app will be killed when taking new photos due to insufficient memory. Thus, after the the app recreated by Android, users will find out that the app does not store the new photo.
Steps to Reproduce
Use a low-end Android device.
After install the app, take photo.
When taking photos, do some "memory demanding" tasks, such as zoom in and out, or switch rear and front camera multiple times.
Repeat the steps 3. multiple times, the app should containing multiple photos and thus uses more device memory.
There should be a high chance that Android kills the mylog app and restores it after user takes a photo. The new photo will not be caught by the app (i.e. the PhotoService.create() will not work).
After the app contains multiple proofs, the app will be killed when taking new photos due to insufficient memory. Thus, after the the app recreated by Android, users will find out that the app does not store the new photo.
Steps to Reproduce
PhotoService.create()
will not work).This is the same issue as numbersprotocol/capture-lite#83. We should catch the image after the app is restored by
App.addListener('appRestoredResult', ...)
. The result is in the following format:The text was updated successfully, but these errors were encountered: