Wound up with two iCloud Drive “Bike” folders

[jessegrosjean]

Ugh, glad nothing was lost.

I suspect this was due, at least in part, to a configuration mess-up between 18.1 (18 Mar 2024) and 18.2 (30 Apr 2024). I think those are the only release where iCould configuration has changed.

@gruber

I first noticed something was wrong when I started getting alert sheets in Bike for my open documents, telling me they were missing or something, and that I had the option of either keeping them or closing them, and that if I closed them I’d lose them. I wish to hell I’d taken a screenshot of this but I didn’t.

Do you know if this started happened due to a Bike update? Maybe one of the computers was on Bike 1.18 and was recently updated?

Generally what I know is:

• In Bike 1.18 and before there was no special iCloud Document integration. Bike worked fine with iCloud, but had no declared NSUbiquitousContainers.

• In Bike 1.18.1 (18 Mar 2024) I tried to get that special Bike specific iCloud folder by adding special iCloud entitlement and by creating a dedicated NSUbiquitousContainer for Bike I think that info is encoded in 1.18.1 as:

<key>NSUbiquitousContainers</key>
<dict>
	<key>iCloud.hogbaysoftware.Bike</key>
	<dict>
		<key>NSUbiquitousContainerIsDocumentScopePublic</key>
		<true/>
		<key>NSUbiquitousContainerName</key>
		<string>BikeOutliner</string>
		<key>NSUbiquitousContainerSupportedFolderLevels</key>
		<string>ANY</string>
	</dict>
</dict>

Alas something wasn’t quite right, and made this comment for 18.2 preview release, unfortunately I don’t remember what I meant when I said “half way for one iCloud location ID, and half up for another ID”. I think maybe it was somehow setup so that the iCloud server container was using one id, while the local Xcode config was using a different one… but looking at Xcode UI I’m not sure how that would have been possible.

Generally I was worried about touching iCloud and I think tried to have Xcode make all the choices for me, but somehow I messed something up in 18.1 and the fix for 18.2 was to change configuration to:

<key>NSUbiquitousContainers</key>
<dict>
	<key>iCloud.com.hogbaysoftware.Bike</key>
	<dict>
		<key>NSUbiquitousContainerIsDocumentScopePublic</key>
		<true/>
		<key>NSUbiquitousContainerName</key>
		<string>Bike</string>
		<key>NSUbiquitousContainerSupportedFolderLevels</key>
		<string>ANY</string>
	</dict>
</dict>

That was released in 30 Apr 2024 and I don’t think I’ve touched any iCloud related setting since. Bike does currently have two NSUbiquitousContainers on the server, iCloud.com.hogbaysoftware.Bike and the older iCloud.hogbaysoftware.Bike. I figured safest to just leave the old one active.

@gruber

There’s a missing ~com in the one that contained my missing files and which disappeared out from under me.

I can understand how the two different folders appeared due to configuration issues between 1.18.1 and 1.18.2, but I don’t understand why documents would started getting deleted from one. Looking on my computer I still see the old iCloud~hogbaysoftware~Bike/Documents folder. It’s no longer accessible through Bikes UI, but if I explicitly save files to it they seem to work, and they are not deleted on restart. I’m on 15.1. I guess I’ll update now and see if that changes the behavior.

Jesse