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

Stop force disabling wakelock #772

Merged
merged 1 commit into from
Sep 8, 2023

Conversation

jan-milovanovic
Copy link
Contributor

@jan-milovanovic jan-milovanovic commented Sep 4, 2023

This commit addresses the issue where Chewie will force disable Wakelock without taking into account that other packages / app parts might depend on the same package.

In my case, the screen will be able to sleep again after exiting fullscreen, even though we don't want it to while the player is running.

Edit: If needed, for context as to why I removed the comment above the code. It was relevant over 3 years ago, when "sleep" was replaced with Wakelock and a comment was written to explain why the if statement was removed. Yes, we don't have to check if wakelock is enabled anymore, but we should still check if we were the ones that enabled it and not override any custom implementations an app may have.

This commit addresses the issue where chewie will force disable wakelock without taking into account that other packages / app parts might depend on the same package
@diegotori
Copy link
Collaborator

LGTM. Once automated checks pass, then you're good to go.

@diegotori diegotori merged commit dbd5e8b into fluttercommunity:master Sep 8, 2023
2 checks passed
diegotori added a commit that referenced this pull request Sep 9, 2023
lg8294 added a commit to lg8294/chewie that referenced this pull request Nov 3, 2023
* master:
  Chewie, version 1.7.0. Adds pull request fluttercommunity#772.
  Upgraded iOS example project's files.
  fix: stop force disable wakelock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants