BUG - Sev-1 - All - Push Notifications for messages aren't working

[rbontrager]

What happened?

Push notifications for messages don't seem to be working and haven't since at least mid December (the earliest build I could get). I talked to Dylan and he believes it is a BE and not FE issue.

Specs:

• Device:
• OS:
• User Account:
• Accessibility State:

Steps to Reproduce

1. Verify that the VA app allows notifications. Login to user +226 and turn on push notifications (if needed).
2. Send a message from the clinician portal. Notice that no push notification happens.

Desired behavior

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See [Bug Tracking](https://department-of-veterans-affairs.github.io/va-mobile-app/docs/QA#issue-severity) for details on severity levels

• Impact: High Low
• Frequency: High Low

• 3 - Low
• 2 - High
• 1 - Critical

Linked to Story

Screen shot(s) and additional information

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

• [ ] Steps to reproduce are defined
• [ ] Desired behavior is added
• [ ] Labels added (front-end, back-end, global, Health, relevant feature, accessibility, etc)
• [ ] Estimate of 1 added (for front-end tickets)
• [ ] Added either to the relevant feature epic (if found during new feature implementation), or the relevant team's bug epic (Global, Health & Benefits, API, QART)

[Sparowhawk]

To add to the notes here this is our logs:

[0] DEBUG Device Token Received 807bde015626318953ad66d26d49b8cdda3d04951d1cfe8424b61d897839f9a0a953748ba794cdd51f180833f36dcd2ca6b03c7f959df58a3a633655e39b8f8a3b222e5fcce8b8dcaa7fc8bac15e882f [0] LOG id undefined [0] DEBUG setAnalyticsUserProperty vama_uses_notifications true [0] DEBUG Device Token Received 807bde015626318953ad66d26d49b8cdda3d04951d1cfe8424b61d897839f9a0a953748ba794cdd51f180833f36dcd2ca6b03c7f959df58a3a633655e39b8f8a3b222e5fcce8b8dcaa7fc8bac15e882f [0] LOG id 3071ca1783954ec19170f3c4bdfd0c95 [0] DEBUG setAnalyticsUserProperty vama_uses_notifications true [0] DEBUG saved endpointSid: null [0] DEBUG saved endpointSid: null [0] DEBUG push registration response: [object Object] [0] LOG id undefined [0] DEBUG push registration response: [object Object] [0] LOG id 3071ca1783954ec19170f3c4bdfd0c95

To follow it looks like when we login everything is getting called correctly and then saved with this [0] DEBUG saved endpointSid: CBBC6B6FAC5F92A6D51714663809598306

So from a FE perspective registering for push notification api seems to be working properly

[rbontrager]

Determined to be a VA notify issue. Closing this ticket.