Skip to content

[Feat/#303] 디버그앱 분리를 진행합니다.#304

Merged
SYAAINN merged 6 commits intodevelopfrom
feat/#303-test-app
Jul 16, 2025
Merged

[Feat/#303] 디버그앱 분리를 진행합니다.#304
SYAAINN merged 6 commits intodevelopfrom
feat/#303-test-app

Conversation

@SYAAINN
Copy link
Contributor

@SYAAINN SYAAINN commented Jul 16, 2025

📌 ISSUE

closed #303

📄 Work Description

  • applicationIdSuffix 로 앱 패키지 분리
  • appIcon, appLabel 분리
  • google-services.json 파일 세팅. (파이어베이스 콘솔에 앱 추가)
  • 디버그 앱에서는 Amplitude를 추적하지 않도록 수정

✨ PR Point

image

클로디가 술식 반전을 통해 돈키로 흑화했습니다. 앞으로 디버깅을 할 때는 돈키 앱으로 진행하게 되겠습니다.
그런데 딱 분리만 해놓은터라 자세한 기능 분리를 추가적으로 진행해야할 것 같은데 해야할 일 함께 의논해주시면 감사하겠습니다.
당장 생각나는 것으로는 ..

  • Firebase App Distribution 분리하기
  • Firebase Cloud Messaging 앱 ID별 토픽 또는 Token 분리 (선택)
  • 앱 진입 시 버전 업데이트 검사 건너뛰기
    가 있습니다..

📸 ScreenShot/Video

image

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Introduced environment-specific app icons and labels for debug and release builds, making it easier to distinguish between development and production versions.
    • Added a unique launcher icon and app name for the debug build, including Korean localization for the debug app name.
  • Chores

    • Updated CI workflow to automatically handle Firebase debug configuration files during builds.
  • Bug Fixes

    • Disabled analytics initialization and inspection checks in debug builds to streamline development and testing.

SYAAINN added 2 commits July 16, 2025 15:29
- applicationIdSuffix로 패키지 분리
- appLabel, appIcon 다르게 설정
- 테스트 앱 google-services.json 파일 추가
@SYAAINN SYAAINN requested a review from MoonsuKang July 16, 2025 06:37
@SYAAINN SYAAINN self-assigned this Jul 16, 2025
@coderabbitai
Copy link

coderabbitai bot commented Jul 16, 2025

Walkthrough

This update introduces environment-specific configurations for debug and release builds of the Android app. It adds new resources and manifest placeholders to distinguish the debug app (with unique icon and label) from the release version. The build script and CI workflow are updated to support these changes, including handling debug-specific Firebase configuration. Additionally, analytics initialization and inspection checks are disabled in debug builds.

Changes

File(s) Change Summary
app/build.gradle.kts Added applicationIdSuffix and manifest placeholders for debug/release; environment-specific UI.
app/src/main/AndroidManifest.xml Replaced hardcoded icon/label with placeholders; enabled override via tools:replace; removed label from MainActivity.
app/src/debug/res/values/strings.xml
app/src/debug/res/values-ko/strings.xml
Added debug-specific app name strings (English/Korean).
app/src/main/res/drawable/ic_launcher_dev_background.xml Added vector drawable for debug app launcher background.
app/src/main/res/mipmap-anydpi-v26/ic_launcher_dev.xml
ic_launcher_dev_round.xml
Added adaptive launcher icons for debug build.
.github/workflows/android_ci.yml Added CI step to decode and place debug google-services.json.
app/src/main/java/com/sopt/clody/ClodyApplication.kt Modified Amplitude initialization to skip in debug builds.
app/src/main/java/com/sopt/clody/presentation/ui/splash/SplashViewModel.kt Modified splash initialization to skip inspection check in debug builds.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant BuildSystem
    participant CI
    participant AndroidApp

    Developer->>BuildSystem: Trigger build (debug/release)
    BuildSystem->>AndroidApp: Apply manifest placeholders (icon/label)
    BuildSystem->>AndroidApp: Use debug/release resources
    CI->>BuildSystem: Run workflow
    CI->>BuildSystem: Decode google-services.json (debug/release)
    BuildSystem->>AndroidApp: Assemble APK with environment-specific config
    AndroidApp->>Amplitude: Initialize only if release build
    AndroidApp->>SplashViewModel: Skip inspection check if debug build
Loading

Assessment against linked issues

Objective (Issue #) Addressed Explanation
Separate release and debug apps (#303)
Environment-specific app name, icon, and resources (#303)
CI/CD pipeline supports debug/release separation (#303)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes detected.

Possibly related PRs

Suggested labels

🌊 문수

Suggested reviewers

  • MoonsuKang

Poem

A rabbit hopped through build and byte,
Debug and release now clear in sight.
With icons green and labels new,
The donkey’s name in every hue.
CI hops in, secrets unpack,
Splitting the app—no going back!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23259d5 and 84e1ad0.

📒 Files selected for processing (1)
  • app/src/main/java/com/sopt/clody/presentation/ui/splash/SplashViewModel.kt (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build
🔇 Additional comments (1)
app/src/main/java/com/sopt/clody/presentation/ui/splash/SplashViewModel.kt (1)

60-60: LGTM! Clean implementation of debug/release separation.

The conditional check correctly bypasses inspection handling in debug builds while preserving the functionality for release builds. This allows developers to test the app without being blocked by inspection dialogs, which aligns perfectly with the PR objectives of separating debug and release app behavior.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@SYAAINN SYAAINN added ✨ FEAT 기능 개발 🔥 민재 민재 labels Jul 16, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

♻️ Duplicate comments (2)
app/src/main/res/values-ko/strings.xml (1)

4-4: Duplicate of EN comment – keep dev label out of production resources

Same rationale as EN strings: relocate app_name_dev to the debug resource set and mark translatable="false" to avoid shipping/maintaining an unneeded string in release builds.

app/src/main/res/mipmap-anydpi-v26/ic_launcher_dev_round.xml (1)

3-4: Same foreground drawable check applies

Ensure @mipmap/ic_launcher_dev_foreground is present; otherwise round-icon generation will fail.

🧹 Nitpick comments (3)
app/src/main/res/values/strings.xml (1)

4-4: Scope dev-only label to the debug resource set and mark as non-translatable

app_name_dev is meant exclusively for the debug variant. Placing it in the common values/ folder exposes it to production builds and translation workflows.
Consider moving the key to src/debug/res/values/strings.xml (or values-dev/) and adding translatable="false" to avoid unnecessary localisation & APK bloat.

<!-- src/debug/res/values/strings.xml -->
<string name="app_name_dev" translatable="false">Donkey</string>
app/src/main/res/drawable/ic_launcher_dev_background.xml (1)

8-74: Icon vector is overly verbose; consolidate paths to shrink APK size

The background contains ~60 identical stroke paths for the grid. At runtime this is fine, but the inflated XML increases the APK and compile time.
You can merge parallel lines into a single <path> using space-separated move/line commands, or generate the grid programmatically in an SVG editor and optimise via svgo before converting.

Result: ~80 % size drop with no visual change.

app/build.gradle.kts (1)

76-78: Keep release & debug placeholder keys in sync

Release assigns appLabel and appIcon but leaves roundIcon hard-coded in the manifest; the same discrepancy noted for the debug build applies here.
Define appRoundIcon for release as well to keep variant handling symmetrical and avoid merge conflicts later.

 manifestPlaceholders["appLabel"] = "@string/app_name"
 manifestPlaceholders["appIcon"] = "@mipmap/ic_launcher"
+manifestPlaceholders["appRoundIcon"] = "@mipmap/ic_launcher_round"
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e665301 and ece9653.

⛔ Files ignored due to path filters (1)
  • app/src/main/ic_launcher_dev-playstore.png is excluded by !**/*.png
📒 Files selected for processing (7)
  • app/build.gradle.kts (2 hunks)
  • app/src/main/AndroidManifest.xml (1 hunks)
  • app/src/main/res/drawable/ic_launcher_dev_background.xml (1 hunks)
  • app/src/main/res/mipmap-anydpi-v26/ic_launcher_dev.xml (1 hunks)
  • app/src/main/res/mipmap-anydpi-v26/ic_launcher_dev_round.xml (1 hunks)
  • app/src/main/res/values-ko/strings.xml (1 hunks)
  • app/src/main/res/values/strings.xml (1 hunks)
🔇 Additional comments (2)
app/src/main/res/mipmap-anydpi-v26/ic_launcher_dev.xml (1)

3-4: Verify that ic_launcher_dev_foreground exists in all density buckets

The file references @mipmap/ic_launcher_dev_foreground, but that drawable isn’t part of this PR.
Please confirm it already exists (including round variants) or add it; missing foregrounds will cause build-time “resource not found” errors.

app/build.gradle.kts (1)

57-64: Verify presence of debug google-services.json for the “.dev” variant

I ran:

fd -H google-services.json app/src
find . -type f -name google-services.json

and found no matching files.

  • You must include a google-services.json under app/src/debug/ (or a multi-client JSON in app/) containing a client entry with
    "package_name": "com.sopt.clody.dev".
  • Without this, the debug APK will throw
    IllegalStateException: Default FirebaseApp is not initialized at runtime.

@SYAAINN SYAAINN changed the title [Feat/#303] 테스트앱 분리를 진행합니다. [Feat/#303] 디버그앱 분리를 진행합니다. Jul 16, 2025
- 우선순위는 빌드 타입 -> 로케일 순입니다.
Copy link
Contributor

@MoonsuKang MoonsuKang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

수고 하셨습니다. google.json은 노션에 올려주시고...
















image

미안하다 이거 보여주려고 어그로끌었다.. 나루토 사스케 싸움수준 ㄹㅇ실화냐? 진짜 세계관최강자들의 싸움이다.. 그찐따같던 나루토가 맞나? 진짜 나루토는 전설이다..진짜옛날에 맨날나루토봘는데 왕같은존재인 호카게 되서 세계최강 전설적인 영웅이된나루토보면 진짜내가다 감격스럽고 나루토 노래부터 명장면까지 가슴울리는장면들이 뇌리에 스치면서 가슴이 웅장해진다..

@SYAAINN SYAAINN merged commit e301099 into develop Jul 16, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

✨ FEAT 기능 개발 🔥 민재 민재

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEAT] 디버그 앱 분리를 진행합니다.

2 participants