Skip to content

Comments

fix: warn natively if notifee is not configured for keep call alive#1678

Merged
santhoshvai merged 4 commits intomainfrom
android-warn-notifee
Feb 12, 2025
Merged

fix: warn natively if notifee is not configured for keep call alive#1678
santhoshvai merged 4 commits intomainfrom
android-warn-notifee

Conversation

@santhoshvai
Copy link
Member

@santhoshvai santhoshvai commented Feb 10, 2025

fixes #1587

Now even if notifee is installed, but not configured properly, we skip call alive part from SDK..

upon inspecting native logs they can see whats not configured properly, its on warn level for easiness

Comment on lines 44 to 45
// Package not found (shouldn't happen for the current app)
e.printStackTrace()
Copy link
Member

Choose a reason for hiding this comment

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

This is a bad practice. How can we better handle this exception?

Copy link
Member Author

Choose a reason for hiding this comment

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

made it better by adding a better logger

but this is not bad practice I think. Atleast I do not know. This catch block was autogenerated by android studio. So I do not think so 😆

@santhoshvai santhoshvai merged commit f6f11ad into main Feb 12, 2025
10 checks passed
@santhoshvai santhoshvai deleted the android-warn-notifee branch February 12, 2025 09:02
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.

App gettting crashed on android on final step

2 participants