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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

[馃悰] IOS in background; when received a notification, display notification after 3-5 minutes later, does not display immediately, does not awake immediately #7684

Closed
ademirtemur opened this issue Mar 15, 2024 · 3 comments
Closed

[馃悰] IOS in background; when received a notification, display notification after 3-5 minutes later, does not display immediately, does not awake immediately #7684

ademirtemur opened this issue Mar 15, 2024 · 3 comments
Labels
Help: Needs Triage Issue needs additional investigation/triaging. Impact: Bug New bug report Type: Stale Issue has become stale - automatically added by Stale bot

Comments

@ademirtemur
Copy link

ademirtemur commented Mar 15, 2024 •
edited

IOS in background; when received a notification, display notification after 3-5 minutes later, does not display immediately, does not awake immediately.

background refresh is open.

"@notifee/react-native": "^7.8.0",
"@react-native-firebase/analytics": "^18.5.0",
"@react-native-firebase/app": "^18.5.0",
"@react-native-firebase/auth": "^18.5.0",
"@react-native-firebase/messaging": "^18.5.0",
@ademirtemur ademirtemur added Help: Needs Triage Issue needs additional investigation/triaging. Impact: Bug New bug report labels Mar 15, 2024
@github-actions GitHub Actions
Copy link

Hello 馃憢, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@github-actions github-actions bot added the Type: Stale Issue has become stale - automatically added by Stale bot label Apr 12, 2024
@ademirtemur
Copy link
Author

not fixed,it still continue

@github-actions github-actions bot removed the Type: Stale Issue has become stale - automatically added by Stale bot label Apr 13, 2024
@github-actions GitHub Actions
Copy link

Hello 馃憢, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@github-actions github-actions bot added the Type: Stale Issue has become stale - automatically added by Stale bot label May 11, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Help: Needs Triage Issue needs additional investigation/triaging. Impact: Bug New bug report Type: Stale Issue has become stale - automatically added by Stale bot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ademirtemur