This differential fixes broken thiock thread in-app notifications on Android and iOS. They were broken since our code considered them to be old schema notifications and converted them by adding authoritativeKeyserverID prefix.
Details
- Reviewers
kamil tomek - Commits
- rCOMMde1c4bb6fb5e: Fix broken in-app notification on native
- Create thick thread using Kamil UI button.
- Send notifications to iOS and Android devices. Ensure that in-app notifications are correctly handled: not displayed when thread is active and displayed in other cases
Diff Detail
- Repository
- rCOMM Comm
- Branch
- marcin/eng-9141
- Lint
No Lint Coverage - Unit
No Test Coverage
We definitely should return something from this lambda since otherwise it is useless to assign it to variable.
If we find that we don't have permissions then just calling await this.requestAndroidNotificationsPermission(); would result in a prompt asking for notifications permissions. However if the user grants those permissions then hasPermissions is still falsy (since promise returned nothing), so deviceToken will be set to null. Nevertheless permissions are actually granted byt the OS, so the state on the device and keyserver would heal itself on next render.
This differential fixes this case so that if user grants permissions correct state is achieved immediately without need for additional re-render to heal the state.