Fail fast in image capture is save location is invalid [167697553]

Fixed

Bug

Status Update

No update yet.

Description

hu...@google.com

created issue #1

Sep 3, 2020 06:55PM

When the user specifies a destination to store the result of an image capture (with the use of outputFileOptions), the ImageCapture use case should verify whether this destination is valid before triggering the image capture request to the camera. If the destination is not valid, the operation should fail fast and the user should be notified about it.

Comments

ap...@google.com <ap...@google.com> #2Sep 10, 2020 05:41PM

Is there any updates? This is a big problem!

hu...@google.com <hu...@google.com> Sep 10, 2020 05:42PM

Marked as fixed.

ap...@google.com <ap...@google.com> #3Sep 11, 2020 04:17PM

Hi there - could you provide more context on the issue & a sample project to reproduce? Database locked exceptions are quite difficult to pinpoint without a repro project. Thanks!

ap...@google.com <ap...@google.com> #4Sep 18, 2020 09:00PM

Hi. It is reproduceable on some users by using this code:

suspend fun <R> MyDatabase.workaroundWithTransaction(block: suspend TransactionScope<R>.() -> R) {
    useWriterConnection {
        it.immediateTransaction(block)
    }

    // TODO: Temporally fix https://issuetracker.google.com/issues/340606803#comment2
    // Manually triggers invalidation
    invalidationTracker.refreshAsync()
}

ap...@google.com <ap...@google.com> #5Sep 18, 2020 09:07PM

Maybe it is about this? https://android-review.googlesource.com/c/platform/frameworks/support/+/3114928

I am not sure.

ap...@google.com <ap...@google.com> #6Sep 18, 2020 09:08PM

Hi. Please merge the pull request. This is big problem!

an...@google.com <an...@google.com> #7Sep 18, 2020 10:03PM

Hi. Is there any updates on this problem?

ap...@google.com <ap...@google.com> #8Sep 18, 2020 10:04PM

Hi, I updated my version to alpha12 but still have these crashes. Please release a fix asap.