-
Notifications
You must be signed in to change notification settings - Fork 267
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
Request FullAccess on iOS17+ #497
Request FullAccess on iOS17+ #497
Conversation
The pipeline might need some updates too it seems |
I have fixed the build test based on the error message. |
lgtm |
Request FullAccess on iOS17+ (builttoroam#497)
This reverts commit 623f0bf.
* fix: request FullAccess on iOS17 or later * update iOS integration description * fix: iOS build test & Android build test
* fix: request FullAccess on iOS17 or later * update iOS integration description * fix: iOS build test & Android build test
@thomassth When will this PR changes be released, or by when will the next version of device_calendar plugin will release with iOS17 updates? |
Someone cherrypick the commit and start a PR to the release branch ( I'll approve that |
* fix: request FullAccess on iOS17 or later * update iOS integration description * fix: iOS build test & Android build test
Hi @thomassth, I just started a cherry-pick PR to master as you suggested. |
* fix: request FullAccess on iOS17 or later * update iOS integration description * fix: iOS build test & Android build test
* Request FullAccess on iOS17+ (#497) * fix: request FullAccess on iOS17 or later * update iOS integration description * fix: iOS build test & Android build test * feat: update xcode-version * update changelog and pubspec * fix ci --------- Co-authored-by: MIYANARI Junki <[email protected]>
Issue #490
A distinction between write-only access and full access has been made since iOS17.
https://developer.apple.com/documentation/technotes/tn3152-migrating-to-the-latest-calendar-access-levels
This PR obtains full access, but it may be inappropriate if you intend to be able to handle write-only access separately.