-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No Calendar has been set" after authorization until App is restarted #55
Comments
Hey @Prudwell, are you waiting for the |
Yes sir, the render function shouldn't even display the option to save a new event unless the authorizeEventStore has fulfilled as authorized in the componentDidMount
Even more strange is that this appears to be intermittent (oh joy). I can delete that app in simulator, reinstall it via xcode, complete the
The function that saves the event is now wrapped with I'll update if I find anything new |
Alright it seems to be caused by another part of my code that's running on an interval. When my app starts up, it attempts to sync events that it sees in its own database with the events stored in iOS calendar events. That interval attempted to read and save events with no regard for I don't know how those failures caused future actions to fail (maybe not catching those promise rejections properly) but it's been resolved by just wrapping that code in The intermittency of the issue for me I believe depended on whether I authorized the event store before that interval ran. |
I'm on iOS and in my app I authorize the calendar store, but I cannot set events until I restart the app. It still acts like the calendar system has not been authorized when I try to add events directly after authorization. Is there some way I'm supposed to reinitialize the calendar object so that it can properly see the new settings?
Cheers
The text was updated successfully, but these errors were encountered: