-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix more build errors #2488
Fix more build errors #2488
Conversation
📝 WalkthroughWalkthroughThe changes update the Android configuration by streamlining API key management. The Changes
Sequence Diagram(s)sequenceDiagram
participant Build as Build Process
participant FP as secrets.properties File
Build->>FP: Check if file exists
alt File exists
FP-->>Build: Send key-value pairs
Build->>Build: Load and apply properties (e.g., Maps API key)
else File not found
Build->>Build: Proceed without properties
end
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
mobile-v3/android/app/build.gradle (1)
34-41
: Unused Secrets Properties BlockThe block loading
secrets.properties
intosecretsProperties
appears redundant since the secrets plugin already manages the secrets. If this code isn’t intended for future expansion, consider removing it to reduce confusion.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
mobile-v3/android/app/build.gradle
(1 hunks)mobile-v3/android/app/src/main/AndroidManifest.xml
(0 hunks)mobile-v3/android/local.defaults.properties
(1 hunks)
💤 Files with no reviewable changes (1)
- mobile-v3/android/app/src/main/AndroidManifest.xml
🔇 Additional comments (4)
mobile-v3/android/local.defaults.properties (1)
1-4
: API Key Variables Added SuccessfullyThe introduction of variables for both production and development environments (for Maps and Places APIs) is clear and aligns with the intended environment differentiation. Just ensure that sensitive values are updated securely when deploying to production.
mobile-v3/android/app/build.gradle (3)
50-53
: Robust Production API Key RetrievalFetching the production Maps API key via
appProperties
with a fallback to the secrets plugin is a solid approach. The accompanying exception provides clear, immediate feedback if the key is missing.
55-58
: Solid Development API Key CheckSimilarly, the retrieval of the development API key is handled well, with an appropriate exception thrown if it isn’t defined. This reinforces the importance of having both keys set correctly.
110-121
: Streamlined Manifest PlaceholdersThe manifest placeholders now exclusively reference the Maps API key, which aligns with the updated key management strategy and the removal of Google Places API key support. This change simplifies the configuration.
Summary of Changes (What does this PR do?)
Status of maturity (all need to be checked before merging):
How should this be manually tested?
What are the relevant tickets?
Screenshots (optional)
Summary by CodeRabbit