This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
Fix app info cut on screen bottom (EXPOSUREAPP-7040) #3098
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # Corona-Warn-App/src/main/java/de/rki/coronawarnapp/ui/information/InformationFragment.kt
SamuraiKek
added
bug
fynngodau
reviewed
May 6, 2021
vaubaehn
reviewed
May 6, 2021
vaubaehn
previously approved these changes
May 6, 2021
mtwalli
reviewed
May 7, 2021
mtwalli
approved these changes
May 7, 2021
|
Kudos, SonarCloud Quality Gate passed! |
axelherbstreith
approved these changes
May 7, 2021
3 tasks
This was referenced Jun 7, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 an issue where on some phones running older versions of Android, the bottom part of the "App Information" screen would be cut off and unscrollable.
Issue is descirbed in #3059 and fix was also found by @fynngodau.
Steps to reproduce are quite finicky, best bet is to follow the last comments in #3059. This is how I've managed to reproduce it.
Thanks @vaubaehn, @fynngodau and @MikeMcC399 for the thorough investigation!