Handle CameraX use cases separately #78
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #50
Instead of binding all use cases to lifecycle at once on Activity startup, this PR creates and binds each use case as per the user needs, and unbinds the current use case when the user switches to another use case.
While this might produce some artifacts and small waits, it prevents the crash from happening on devices where a matching resolution for image still capture and resolution for video capture can't be found, thus ending up not finding a match for both cases at once (and crashing).