From eb0932bddad0daa47c36cd20599944c3dc45482a Mon Sep 17 00:00:00 2001 From: Claude Code Date: Sat, 15 Aug 2026 17:59:12 +0000 Subject: Initial commit: tungsten's memory tree --- feedback_feedreader_apk_naming.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 feedback_feedreader_apk_naming.md (limited to 'feedback_feedreader_apk_naming.md') diff --git a/feedback_feedreader_apk_naming.md b/feedback_feedreader_apk_naming.md new file mode 100644 index 0000000..9508c14 --- /dev/null +++ b/feedback_feedreader_apk_naming.md @@ -0,0 +1,14 @@ +--- +name: feedback-feedreader-apk-naming +description: "Send feedreader debug APKs under a stable, descriptive filename, not the default app-debug.apk" +metadata: + node_type: memory + type: feedback + originSessionId: 375c858e-e817-41e8-a076-7920d22eab2b +--- + +When sending Peter a debug build of the "Feeds" app, copy/rename the Gradle output (`app/build/outputs/apk/debug/app-debug.apk`) to `feeds-debug.apk` before sending, rather than sending the default filename as-is. + +**Why:** He explicitly asked for this ("name the apk feeds-debug.apk so I can keep them straight") after receiving a couple of same-named `app-debug.apk` builds in a row — he's juggling multiple app builds/devices and needs the filename itself to disambiguate which project/app a given APK is. + +**How to apply:** Applies to this project specifically; if other Android projects come up, ask or infer a similarly stable, project-specific filename rather than defaulting to the Gradle output name. -- cgit v1.2.3