Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parts of the app can't be accessed in some devices as they touch operating system interfaces #1038

Closed
SriramPatibanda opened this issue Dec 13, 2021 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@SriramPatibanda
Copy link
Contributor

Describe the bug

The buttons and content at the boundaries of the app in select language screen can't be accessed as they touch operating system interfaces.

To Reproduce
Steps to reproduce the behavior:

Opening the app in devices without a notch display reproduces this behavior.

Expected behavior
The whole interface of the app must be within the phone boundaries(SafeArea) so that every button is accessible.

Actual behavior
The app's content at the boundaries of the device can't be accessed.

Screenshots
Screenshot_20211213-130225

Additional details
N.A.

@github-actions github-actions bot added bug Something isn't working unapproved Unapproved, needs to be triaged labels Dec 13, 2021
@SriramPatibanda
Copy link
Contributor Author

SriramPatibanda commented Dec 13, 2021

Though Padding was given using SizeConfig, it's not getting initialized sometimes and this problem is faced in the Select Language page especially. I think wrapping the Scaffold with SafeArea must be a more preferable and recommended solution for this problem. @rutvik11062000 @sumitra19jha

@palisadoes palisadoes removed the unapproved Unapproved, needs to be triaged label Dec 14, 2021
@CyberWake
Copy link
Contributor

@SriramPatibanda can you tell in which scenarios do the sizeConfig is not initialized. Because that is strange this will make the whole application's UI crumble up.

@SriramPatibanda
Copy link
Contributor Author

@SriramPatibanda can you tell in which scenarios do the sizeConfig is not initialized. Because that is strange this will make the whole application's UI crumble up.

I'm not able to reproduce this bug again, but suddenly sometimes size config didn't get initialised and that's when I had faced this issue. And after navigating to the next page or hot reloading it, it was getting initialised.

@CyberWake
Copy link
Contributor

Share a demo of the happening since this isn't possible AFAIK. And wrapping widgets in safe area for no sake doesn't make sense. Would be better if you could exactly tell the scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants