Fix versioned expiration timer capability bug.

This commit is contained in:
Cody Henthorne 2024-08-30 16:18:23 -04:00
parent 84ae8db549
commit 216073f4c2
3 changed files with 8 additions and 3 deletions

View file

@ -12,7 +12,7 @@ object AppCapabilities {
return AccountAttributes.Capabilities(
storage = storageCapable,
deleteSync = true,
expireTimerVersion = true
versionedExpirationTimer = true
)
}
}

View file

@ -153,9 +153,10 @@ public class ApplicationMigrations {
static final int REBUILD_MESSAGE_FTS_INDEX_5 = 108;
static final int EXPIRE_TIMER_CAPABILITY = 109;
static final int REBUILD_MESSAGE_FTS_INDEX_6 = 110;
static final int EXPIRE_TIMER_CAPABILITY_2 = 111;
}
public static final int CURRENT_VERSION = 110;
public static final int CURRENT_VERSION = 111;
/**
* This *must* be called after the {@link JobManager} has been instantiated, but *before* the call
@ -698,6 +699,10 @@ public class ApplicationMigrations {
jobs.put(Version.REBUILD_MESSAGE_FTS_INDEX_6, new RebuildMessageSearchIndexMigrationJob());
}
if (lastSeenVersion < Version.EXPIRE_TIMER_CAPABILITY_2) {
jobs.put(Version.EXPIRE_TIMER_CAPABILITY_2, new AttributesMigrationJob());
}
return jobs;
}

View file

@ -56,6 +56,6 @@ class AccountAttributes @JsonCreator constructor(
data class Capabilities @JsonCreator constructor(
@JsonProperty val storage: Boolean,
@JsonProperty val deleteSync: Boolean,
@JsonProperty val expireTimerVersion: Boolean
@JsonProperty val versionedExpirationTimer: Boolean
)
}