- 07 Jul, 2019 4 commits
- 04 Jul, 2019 3 commits
- 02 May, 2019 3 commits
-
-
Artal Druk authored
-
Artal Druk authored
This reverts commit 498dd34b.
-
Artal Druk authored
This reverts commit 0c21b4bd.
-
- 18 Apr, 2019 6 commits
-
-
yogevbd authored
-
yogevbd authored
-
Artal Druk authored
-
Artal Druk authored
-
Artal Druk authored
-
Artal Druk authored
-
- 18 Mar, 2019 1 commit
-
-
aboelbisher authored
* IOS deprecated API replacement
-
- 14 Mar, 2019 1 commit
-
- 24 Feb, 2019 3 commits
-
-
Yogev Ben David authored
Fixes isRegisteredForRemoteNotifications on iOS
-
Yogev Ben David authored
-
yogevbd authored
-
- 04 Feb, 2019 5 commits
- 30 Jan, 2019 1 commit
-
-
yogevbd authored
-
- 29 Jan, 2019 3 commits
-
-
Yogev Ben David authored
-
Yogev Ben David authored
-
Yogev Ben David authored
Migrate from GCM to FCM
-
- 12 Dec, 2018 2 commits
-
-
Yogev Ben David authored
-
yogevbd authored
-
- 11 Dec, 2018 4 commits
-
-
yogevbd authored
-
Yogev Ben David authored
Foreground listener
-
yogevbd authored
-
yogevbd authored
-
- 10 Dec, 2018 2 commits
-
-
yogevbd authored
-
Yogev Ben David authored
fix background PN is received as foreground
-
- 09 Dec, 2018 1 commit
-
-
Doron Pearl authored
for the first time. refs #268 The `didReceiveRemoteNotification` checks for the current app state which will be active and hence wrongly emit the notification to JS as foreground. However at the exact time when the user opened the notification, the app was at the background hence this is a background notification by definition. In other words, conceptually determining if the notification is background or foreground should NOT be based on the time it was consumed from the queue but on the time it was received. Practically, if it was queued, then the app must have been in the background ==> background notification.
-
- 04 Nov, 2018 1 commit
-
-
Amit Davidi authored
-