ScarriffleandClaude Opus 5
75ae038529
Saving ran loadEvents(force: true), which skips the isCached check but leaves the existing cache in place. The manual reload button clears the cache first, and that is the one that reliably shows a newly created Home Assistant event. Rather than keep reasoning about why bypassing the cache is not enough, saving now takes the path that demonstrably works — the only difference between the two was invalidateCache(). reloadVisible had no callers left and is gone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
53 lines
1.2 KiB
Plaintext
53 lines
1.2 KiB
Plaintext
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
|
|
<plist version="1.0">
|
|
<dict>
|
|
<key>SchemeUserState</key>
|
|
<dict>
|
|
<key>Calendarr iOS.xcscheme_^#shared#^_</key>
|
|
<dict>
|
|
<key>orderHint</key>
|
|
<integer>0</integer>
|
|
</dict>
|
|
<key>CalendarrWatch Watch App.xcscheme_^#shared#^_</key>
|
|
<dict>
|
|
<key>orderHint</key>
|
|
<integer>3</integer>
|
|
</dict>
|
|
<key>CalendarrWatch.xcscheme_^#shared#^_</key>
|
|
<dict>
|
|
<key>orderHint</key>
|
|
<integer>1</integer>
|
|
</dict>
|
|
<key>CalendarrWatchComplications.xcscheme_^#shared#^_</key>
|
|
<dict>
|
|
<key>orderHint</key>
|
|
<integer>2</integer>
|
|
</dict>
|
|
<key>CalendarrWatchExtension.xcscheme_^#shared#^_</key>
|
|
<dict>
|
|
<key>orderHint</key>
|
|
<integer>4</integer>
|
|
</dict>
|
|
<key>CalendarrWidgets.xcscheme_^#shared#^_</key>
|
|
<dict>
|
|
<key>orderHint</key>
|
|
<integer>3</integer>
|
|
</dict>
|
|
</dict>
|
|
<key>SuppressBuildableAutocreation</key>
|
|
<dict>
|
|
<key>3927C7BB2FB99D0E00EAD8ED</key>
|
|
<dict>
|
|
<key>primary</key>
|
|
<true/>
|
|
</dict>
|
|
<key>C0000A01FB4E10100AB5001</key>
|
|
<dict>
|
|
<key>primary</key>
|
|
<true/>
|
|
</dict>
|
|
</dict>
|
|
</dict>
|
|
</plist>
|