cache-request-isolation

Diagnose blank AniTrend UI from CacheRequest enum collisions in cache_log.

51|6|Updated Mar 10, 2019
One-click install
npx skills add https://github.com/AniTrend/anitrend-v2 --skill cache-request-isolation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cache-request-isolation
Source: https://github.com/AniTrend/anitrend-v2/tree/main/.agents/skills/cache-request-isolation
Command: npx skills add https://github.com/AniTrend/anitrend-v2 --skill cache-request-isolation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill diagnoses and fixes cases where AniTrend renders a blank UI without crashes because offline-first cache identity values collide in the cache_log table. It helps you confirm why Room tables remain empty and ensures the app will actually fetch and persist the missing data for each source variant.

Core Features & Use Cases

  • Detect cache_log collisions that cause subsequent source variants to skip network calls with no exceptions.
  • Forensic Room and WAL verification by pulling the app databases from a device and checkpointing WAL pages.
  • Validate network behavior with Chucker to determine whether the failure happens before requests or during persistence.
  • Apply the fix safely by introducing distinct CacheRequest enum values and updating Koin wiring so sidecar sources use the correct cache request.

Quick Start

Use the cache-request-isolation skill to debug a blank AniTrend screen by pulling the Room databases, checking cache_log for request collisions, and then updating CacheRequest and Koin wiring for the affected source variants.

Frequently Asked Questions about cache-request-isolation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Android app show a blank screen when Room tables are empty but there are no crashes?

A blank screen with empty Room tables and no crashes often indicates a cache collision in the cache_log table, causing the app to skip network calls. This happens when offline-first cache identity values overlap across source variants.

How do I verify cache_log collisions in an offline-first Android app?

To verify cache_log collisions, pull the device Room databases, checkpoint WAL pages, and check the request and cache_item_id coverage to see if overlapping identity values are preventing data persistence.

Does Chucker help diagnose missing network requests in Room offline caching?

Yes, Chucker validates network behavior by confirming whether the failure happens before requests are sent or during the Room persistence phase, helping isolate the root cause of the empty cache.

What is the best way to fix silent blank screens caused by cache identity collisions?

The best way to fix cache identity collisions is introducing distinct CacheRequest enum values for each source variant and updating the Koin factory wiring to pass the correct cache request per sidecar source.

When should I checkpoint WAL pages when debugging an Android Room database?

You should checkpoint WAL pages when pulling device databases to perform forensic Room verification, ensuring all committed transactions in the Write-Ahead Log are merged into the main database before inspecting cache_log entries.