Release 1.4
versionCode 5. public_html/ changed, so the service worker cache goes to bgclock-v20. Confirmed on device: a turn left running well past the delay, force-quit and reopened, now comes back with the time it had actually spent. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -12,8 +12,8 @@ android {
|
||||
applicationId = "nl.hansdezwart.bgclock"
|
||||
minSdk = 26
|
||||
targetSdk = 36
|
||||
versionCode = 4
|
||||
versionName = "1.3"
|
||||
versionCode = 5
|
||||
versionName = "1.4"
|
||||
}
|
||||
|
||||
compileOptions {
|
||||
|
||||
@@ -0,0 +1,4 @@
|
||||
Fixes a match not coming back correctly after the app is force-quit. The clock
|
||||
returned to where it stood at the last turn change, losing the time spent on
|
||||
the turn that was interrupted. The match is now written down once a second
|
||||
while a clock is running, so at most a second can be lost.
|
||||
+1
-1
@@ -1,5 +1,5 @@
|
||||
/* Cache-first: once installed the clock never touches the network again. */
|
||||
const CACHE = "bgclock-v19";
|
||||
const CACHE = "bgclock-v20";
|
||||
const FILES = [
|
||||
"./",
|
||||
"./index.html",
|
||||
|
||||
Reference in New Issue
Block a user