Release identity
Version: 1.1.0
VersionCode: 37
Package: com.saravanabhava.murugan
Expo SDK: 56
Website · Android App · Offline · Cache · Local Data
Diagnose common website and Android app problems, recover missing routes, refresh cached content and prepare a reproducible support report without sending unnecessary personal data.
Saravana Bhava – Murugan Bhakti
Version: 1.1.0
VersionCode: 37
Package: com.saravanabhava.murugan
Expo SDK: 56
Restart the phone, confirm the installed version, and record the exact crash or blank-screen behaviour. Do not reinstall until bookmarks or notes have been considered.
Update the Android text-to-speech engine, install a Tamil voice where available, restart the app and try a short devotional passage first.
Record the content title, action and restart result. Local data can be reset through the app or Android Settings, but deletion is irreversible.
Include the temple name, field, current value, proposed correction and an official or authoritative source. Do not overwrite needs-review data from memory.
Provide the Tamil, English or transliterated query, expected content title and actual result. Guided Search uses bundled local records and does not invent missing content.
Include all of the following:
Privacy-preserving website diagnostics
Checking this browser locally…
Safe website quick fixes
Reload once. When an old service-worker cache persists, clear only runtime/data caches before removing the full site storage.
Reload the current route after cache clearing. A hard refresh may be required when a proxy or CDN retains an earlier asset.
The 404 page checks an exact alias registry, then suggests related governed routes without fuzzy automatic redirects.
Open directoryOpen the site once online so core routes and assets can enter the PWA cache. Optional routes may still require a network connection.
Open offline guideBrowser-local data is tied to the browser profile and site storage. Restore a prior export where available.
Personal data toolsDo not overwrite a source-controlled text from memory. Prepare a correction with page, edition and evidence.
Prepare correctionInclude the page or app screen, approximate time, browser or device, online/offline state, visible error, expected result, steps to reproduce and whether a restart or cache refresh changed the behaviour. Never include passwords, private notes or unnecessary personal data.