In Bug 1140951, we found that bluedroid stack reported a wrong connId in |RegisterNotificationNotification|. Since connId is the only identifier info in this notification callback, we couldn't map back to the target client if this only info is wrong. Currently we use a workaround to resolve/reject the start/stopNotification request in their result handler. This bug is to track that we should remove this workaround after upstream fixed. We also need to report the wrong connId bug to upstream.
Remove [bluetooth2] from title since it's already landed on m-c.
Summary: [bluetooth2] Resolve/Reject the promise of start/stopNotifications() in |RegisterNotificationNotification| → Resolve/Reject the promise of start/stopNotifications() in |RegisterNotificationNotification|
You need to log in before you can comment on or make changes to this bug.