-
Notifications
You must be signed in to change notification settings - Fork 275
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
iOS 17 PlatformException(401, The user has not allowed this application to modify their calendar(s), null, null) #561
Comments
make sure that this line of code |
It shows authorized inside the app settings, but |
That is strange, can you provide a minimum example to reproduce this issue? |
Here's my running order
You can check separately the permission status returned by these two lines of code.
|
Ran into the similar issue. Could not get permission request at all. It even didn't appear in system settings. Worked it around via requesting the permission from permission_handler, but it requires relaunching the app to retrieve the calendar list. Moreover, it reproduces only on 17.0, on 17.2 and higher works like charm (couldn't get my hands on iOS 17.1). |
It should be caused by two methods with the same name |
ios 17.0
var calendarsResult = await _deviceCalendarPlugin.retrieveCalendars() has error PlatformException(401, The user has not allowed this application to modify their calendar(s), null, null)
await _deviceCalendarPlugin.requestPermissions();
await _deviceCalendarPlugin.hasPermissions();
var calendarsResult = await _deviceCalendarPlugin.retrieveCalendars();
errorcode:599
errorMessage:Device calendar plugin ran into an issue. Platform specific exception [401], with message :"The user has not allowed this application to modify their calendar(s)", has been thrown.
When getting the fullaccess privileges for a calendar, running await _deviceCalendarPlugin.requestPermissions() gives true after the user grants the privileges, but await _deviceCalendarPlugin.hasPermissions() says is false, and only becomes true after restarting the app.
The text was updated successfully, but these errors were encountered: