Yes sharedbucked_access is set on true. And I completely agree and understand the tombstone process.
With “correctly purged” I mean that the sqlite file size does not decrease. In fact I can find the docId (that I expired server side) inside the sqlite database. I cannot fetch it using a n1ql query from the mobile sdk, tho.
So the idea I have is that the purge doesnt work as intended (SQLiteStudio is able to free 30mb out of 140, while the purge using the SDK does almost nothing). Or at least, is not as efficient as any other sqlite software I tried.