StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15450592
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-03-16T14:41:58.717
FavoriteCount
0
LastActivityDate
2013-03-16T14:41:58.717
LastEditDate
LastEditorUserId
0
OwnerUserId
1320544
ParentId
15191546
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It looks to me like your database store is getting created for iCloud, but nothing is being put into it. The receipt.0.cdt file appears in the transaction log folder for each device using that app through iCloud, but only initially (on store creation, or connection to an existing store from another device). The transaction logs that actually contain the data are named more like: <pre><code>FFFE99DC-87D7-5CBE-BFD8-32E11-D3E934.1.cdt </code></pre> and are of a size that is proportional to the number of records inserted/updated/deleted etc in that transaction. These transaction logs appear in the iCloud device folder related to the device that generated those transactions. A device that has connected to iCloud for that app, but NOT performed any transactions of its own, will just have the receipt.0.cdt file in it. If you unzip the receipt.0.cdt, you end up with a text file - and all this seems to contain is a reference to the device these transaction logs were generated against (though initially is empty). <pre><code>mobile.DEVICE_ID:NUMBER_OF_TRANSACTIONS </code></pre> And this then grows to show: <pre><code>mobile.DEVICE_TWO:2:mobile.DEVICE_ONE:4 </code></pre> so receipt.0.cdt is just a housekeeping reference for the number of transactions recorded against each device connected to that store in iCloud. Concentrate on making sure you're actually putting data into your iCloud store (using the correct context, aren't getting mixed up with the local store context etc), and then actually saving it. If none of that works, try blowing away the entire iCloud container and starting again in case something has gone wrong inside your ubiquity store (the standard response to just about every Core Data iCloud conundrum!).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONSPersistentStoreDidImportUbiquitousContentChangesNotification not fired on either iOS device
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRob Glassey
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.