I'm also still seeing this issue. This code produces the above error, `Trigger of type: calendar is not supported on Android.`:
See original GitHub issueI’m also still seeing this issue. This code produces the above error, Trigger of type: calendar is not supported on Android.
:
await Notifications.scheduleNotificationAsync({
content: { body: 'Hello' },
trigger: { channelId: 'default', hour: 10, minute: 23, repeats: true },
});
This code does nothing (note the omitted channelId
):
await Notifications.scheduleNotificationAsync({
content: { body: 'Hello' },
trigger: { hour: 10, minute: 23, repeats: true },
});
_Originally posted by @bakerkretzmar in https://github.com/expo/expo/issues/8996#issuecomment-710079999_
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
DailyNotificationTrigger in expo-notifications not working on ...
Trigger of type: calendar is not supported on Android.] This is the snippet of code that produces the error: Notifications.
Read more >Notifications - Expo Documentation
Notifications. The expo-notifications provides an API to fetch push notification tokens and to present, schedule, receive and respond to notifications.
Read more >Service | Android Developers
Clients can also use Context.bindService() to obtain a persistent connection to a service. This likewise creates the service if it is not already...
Read more >Fix connection errors - Google Chrome Help
If you get an error message when you try to visit a website, try these fixes. If your error isn't listed below, learn...
Read more >Known Issues and Limitations for Webex Meetings
Scheduling in Microsoft Outlook with an account set up from Google Calendar isn't supported. The desktop app can only read the meeting list ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Mine is 39. Dunno if there is any minor update. or if the version of expo- notifications matters. Let me check it out tomorrow
Thanks for the advice. My expo-notifications is ~0.7.2 which is the latest for now. I have checked the changelog just now and saw @sjchmiela had already merge a fix to master branch of expo https://github.com/expo/expo/pull/10454. The revised code is not yet available in sdk-39 branch though; so we may still come across this issue. Looks like it will be publish in near future. By considering that, I will close the issue and try wait for update. Thanks mates!