Update bundled CRL to latest Google status

[shoey63]

Updates the hardcoded offline fallback status.json to the latest payload from Google and bumps the UI badge string to reflect the March 17th date.

[VisionR1]

What about this ?
#11 (comment)

[VisionR1]

Updates the hardcoded offline fallback status.json to the latest payload from Google and bumps the UI badge string to reflect the March 17th date.

In my Key Attestation, still say 16 March.

[shoey63]

What about this ? #11 (comment)

Fix added to PR

[shoey63]

Updates the hardcoded offline fallback status.json to the latest payload from Google and bumps the UI badge string to reflect the March 17th date.

In my Key Attestation, still say 16 March.

16th or 17th seems to depend on timezone

Also this is the hard coded CRL ie: no internet and no cache eg: installed offline or cleared data offline or internet dropped immediately after downloading and installing.
OR Corrupt/invalid CRL like @zgfgNew had

[shoey63]

No description provided.

[shoey63]

One more fix coming to resolve zgfg's issues

[shoey63]

​@VisionR1 This is ready to go!

It bundles the latest March CRL data along with two major fixes:

​The Locale UI Fix:
As you requested over in #11, I implemented the AppCompatDelegate context wrapper in HomeAdapter.kt. The CRL status strings will now properly respect the user's chosen in-app language rather than forcing the system default.

​Critical Legacy Cache Hotfix:
I also caught and patched a schema migration bug reported by @zgfgNew. Users upgrading from pre-Build 52 to the latest master are currently crashing on the old revocation_cache.json format when the server returns a 304, permanently trapping them in an offline fallback loop. I added a try/catch block in RevocationList.java that intercepts the legacy cache crash, wipes the incompatible file, and forces a fresh 200 OK download so the app seamlessly self-heals for all upgrading users.

[VisionR1]

Thanks.

So, ready for release 2.0.1 ?

[VisionR1]

@shoey63

Now it says March 23rd, update yesterday?

I think, we must change without date in the string, so no need every time change the specific date

From:
❌ Offline - using hardcoded 17th March CRL

To:
❌ Offline - using hardcoded from last CRL

Or something similar.

I know, this go this the status.json.

[shoey63]

Wow. One week and already a new CRL! Mine says 24 March.
The dynamic CRL Fetch is working beautifully! The reality is though, that message is only seen in extreme edge cases. People have internet 99+% of the time. Maybe something like ❌ offline. CRL out of date.
What do you think?

Also I think leave app/src/main/res/raw/status.json as is. Just update strings and 2.0.1 will be good to go👍

[VisionR1]

Yeah.

Too fast.

Just like the: ✅ CRL Up-to-date

❌ Offline - CRL Out-of-date

?

[shoey63]

Yeah, app/src/main/res/values/strings.xml line 63
❌ Offline - CRL Out-of-date
(Plus translation strings)

Maybe every few months update app/src/main/res/raw/status.json but always leave it behind 😉