[expo-notifications] Fix interpretation of Date and number triggers on iOS
#7942
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rs when calling `scheduleNotificationAsync` on iOS
|
Lgtm! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
Fixes #7937.
How
+(NSDate *)dateWithTimeIntervalSince1970:expects time interval to be provided in seconds. From JS we receive a.getTime()value which corresponds to milliseconds since 1970. Dividing by 1000 transforms milliseconds to seconds.Test Plan
I have added a test case that tests whether a notification scheduled with a
Datetrigger is triggered.