bug: catch exception if opening a notification fails

[abdulraqeeb33]

Description

One Line Summary

Catch and Log an exception when opening a destination activity fails thru Notification

Details

Motivation

Provide better user experience by catching and logging errors when it fails to open a destination activity.
This is in response to the PR https://github.com/OneSignal/OneSignal-Android-SDK/pull/1954/changes

Scope

Better logging.

Testing

Unit testing

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is 

[github-actions]

📊 Diff Coverage Report

Diff Coverage Report

Threshold: 80%

Changed Files Coverage

• ❌ NotificationLifecycleService.kt: 0/137 lines (0.0%)
  • ⚠️ Below threshold: 137 uncovered lines

Overall Coverage

0/137 lines covered (0.0%)

❌ Coverage Check Failed

Files below 80% threshold:

• NotificationLifecycleService.kt: 0.0% (137 uncovered lines)

📥 View workflow run

[nan-li]

not sure we should catch all exception? Still sounds fine to me

[abdulraqeeb33]

not sure we should catch all exception? Still sounds fine to me

yeah i was assuming this is our code, atleast we should catch and print the exception