Notifee Notifications

test

123

Upon attempting to submit a feature request on the platform at ' https://invertase.canny.io/notifee ', I encountered a functionality issue. After filling out the title and description fields and clicking on the submit button, a pop-up prompt for logging in with social accounts appeared. I opted to log in using Google credentials. However, following successful login, there was no immediate reflection of my logged-in profile status. The platform still displayed the "Login" option in the top header instead of showing my logged-in status. Only after refreshing the page did the changes reflect accurately, indicating my logged-in status. Steps to Reproduce: Navigate to ' https://invertase.canny.io/notifee '. Attempt to submit a feature request by providing a title and description. Click on the submit button. Encounter the pop-up prompt for logging in with social accounts. Choose the Google option and proceed with login. Observe that despite successful login, the platform still displays "Login" in the top header instead of reflecting the logged-in status. Refresh the page. Notice that upon refreshing, the platform accurately reflects the logged-in status. Expected Behavior: Upon successful login via Google or any other social account, the platform should immediately reflect the logged-in status without requiring a manual page refresh. The top header should display the user's profile information or indicate the logged-in status instead of showing the "Login" option. Impact: This issue affects user experience and may lead to confusion among users regarding their logged-in status on the platform. It introduces an unnecessary step of manual page refresh to accurately reflect the logged-in status, which can be inconvenient for users attempting to interact with the platform seamlessly. Additional Information: Please ensure that the platform's authentication and session management mechanisms are properly integrated to immediately reflect the logged-in status upon successful authentication via social accounts. Testing across different browsers and devices may help in identifying any potential inconsistencies in the behavior. Additionally, considering asynchronous techniques or real-time updates could enhance the responsiveness of the platform in reflecting user authentication status changes.

Can you add links for documentations of older versions please?

Scheduling/Triggering Notifications based on Time/Date, a delay, or geofence

In AndroidQ, because of restrictions on starting activities from the background https://developer.android.com/guide/components/activities/background-starts So when the app's screen turn off( lock screen mode ) we can only show our activity via notification that have setFullScreenIntent action. But setFullScreenIntent is not supported yet so no way we can display app when receiving notification in lock screen

Get an array of all notifications that were not open exemple: firebase .notifications() .getAllNotifications => []

I want to turn off the notification from my application command but we don't have ant feature like this. Even firebase.messaging().requestPermission() is not revoking again if user already has permission. Do whatever is possible.

In Android, we can create a custom view from scratch and set it for notification view. is that possible using react-native-firebase? if yes, how can I achieve it, if no, is there any milestone to support it in near future? I'm not familiar with IOS development too much, is that possible such feature for IOS too?