Every day I visit the forums I have to sign in again despite having ticked the "remember me" check box on the login form.
Having to sign in again to make the simplest action of upvoting an answer makes me not want to bother.
Safari Version 13.1.1 (15609.2.9.1.2)
macOS Catalina 10.15.5 (19F101)
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
At 21:40 in the video the following code is shown:
(sorry for the screenshot but this talk doesn't have code copy enabled)
Luca points out this results in new view and storage every time dayTime changes. Say you wanted to fix it so it doesn't create a new view and storage every time, how would you do that?
Like this maybe?
var body: some View {
let cr = CatRecorder()
if dayTime {
return cr.nightTimeStyle()
}
else {
return cr
}
}
But this code doesn't look very declarative. I've seen many struggle with applying modifiers conditionally (especially .hidden()) so thought I'd ask.
Hi Nick, I've implemented by own sync that works the same as Notes but it requires using the private CKReferenceActionValidate. Could you help make that public? Cheers
See
https://developer.apple.com/forums/thread/652267
and
FB6114162 - 4 Jun 2019
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
Cloud and Local Storage
UI Frameworks
wwdc21-10015
I enjoyed the video thanks. At 6mins when David said "You don't need to do anything else and your data will be indexed in Spotlight.". What immediately came to mind was what about cleaning up the persistent history?
I had a brief look at the docs and noticed that indexDidUpdateNotification includes NSPersistentHistoryTokenKey should we listen for that and then purge the history?
And what if we have multiple components requiring use of the persistent history? Is there a recommended strategy for deleting only the history not required by the Spotlight indexer and other components?
Please explain how and when the state should be transferred from split VC to tab controller when traits change from regular to compact. Please also consider then the middle “supplementary” column is in use.
Please confirm we should no longer use adaptivity API given any showing alert or popover would likely be lost or should those also be in the state?
Sample code of the relevant parts of the Shortcuts app would be very useful as this is a very difficult design pattern and it seems it is essential for cross platform apps targeting iPhone/iPad/Catalyst.