Skip to content

Fix #994 Remove unnecessary error for FCM #999

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

Merged
merged 1 commit into from
Jun 17, 2022

Conversation

chkuang-g
Copy link
Contributor

Remove unnecessary error for FCM

Description

Provide details of the change, and generalize the change in the PR title above.

There is no need to log and error when the API returns the existing future.


Testing

Describe how you've tested these changes. Link any manually triggered Integration tests or CPP binary SDK Packaging Github Action workflows, if applicable.

Integration test workflow


Type of Change

Place an x the applicable box:

  • Bug fix. Add the issue # below if applicable.
  • New feature. A non-breaking change which adds functionality.
  • Other, such as a build process or documentation change.

Notes

  • Bug fixes and feature changes require an update to the Release Notes section of release_build_files/readme.md.
  • Read the contribution guidelines CONTRIBUTING.md.
  • Changes to the public API require an internal API review. If you'd like to help us make Firebase APIs better, please propose your change in a feature request so that we can discuss it together.

There is no need to log and error when the API returns the existing
future.
@chkuang-g chkuang-g added the skip-release-notes Skip release notes check label Jun 17, 2022
@@ -180,7 +180,6 @@ void NotifyListenerSet(Listener* listener) {
FIREBASE_ASSERT_RETURN(RequestPermissionLastResult(), internal::IsInitialized());

if (RequestPermissionLastResult().status() == kFutureStatusPending) {
LogError("Status is pending. Return the pending future.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be a LogDebug if we still need this for some reason.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I merged before seeing this comment. Do you think I should add LogDebug back?

I did a code search and it does not seems like we are logging anything when LastResult is pending.

@chkuang-g chkuang-g merged commit 5f23f71 into main Jun 17, 2022
@github-actions github-actions bot added the tests: in-progress This PR's integration tests are in progress. label Jun 17, 2022
@github-actions
Copy link

github-actions bot commented Jun 17, 2022

✅  Integration test succeeded!

Requested by @chkuang-g on commit 5f23f71
Last updated: Fri Jun 17 11:24 PDT 2022
View integration test log & download artifacts

@chkuang-g chkuang-g deleted the patch/remove-pending-future-error branch June 17, 2022 17:39
@github-actions github-actions bot added the tests: succeeded This PR's integration tests succeeded. label Jun 17, 2022
@firebase-workflow-trigger firebase-workflow-trigger bot removed the tests: in-progress This PR's integration tests are in progress. label Jun 17, 2022
@firebase firebase locked and limited conversation to collaborators Jul 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
skip-release-notes Skip release notes check tests: succeeded This PR's integration tests succeeded.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants