Update sdk version

[cp-pratik-k]

Summary by CodeRabbit

• New Features
  • Updated the target SDK version for the Android application to ensure compatibility with the latest features.

[coderabbitai]

Walkthrough

The changes involve an update to the build.gradle file of an Android application, specifically modifying the targetSdkVersion in the defaultConfig block from a dynamic reference to a hardcoded value of 34. This adjustment aligns the target SDK level with the compile SDK version, while other configurations remain unchanged.

Changes

File Path	Change Summary
app/android/app/build.gradle	Updated targetSdkVersion from flutter.targetSdkVersion to 34 in defaultConfig.

Poem

In the code where rabbits hop,
A version change, we won't stop.
From flutter's call to number thirty-four,
Our app now leaps, it can explore!
With every build, we dance and play,
Hopping to a brighter day! 🐇✨

---

📜 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 f127910 and 130535c.

📒 Files selected for processing (1)

• app/android/app/build.gradle (1 hunks)

🔇 Additional comments (2)

app/android/app/build.gradle (2)

51-51: Verify Android 14 (API 34) compatibility

The change from flutter.targetSdkVersion to hardcoded 34 aligns with compileSdkVersion, which is good. However, targeting Android 14 introduces behavioral changes that need verification:

• Runtime permissions for exact alarms
• Foreground service types must be declared
• Changes to media access permissions

Let's verify the AndroidManifest.xml for required Android 14 declarations:

✅ Verification successful

Android 14 compatibility requirements are properly addressed

The manifest already includes all necessary Android 14 media-related permissions:

• READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_AUDIO for granular media access
• READ_MEDIA_VISUAL_USER_SELECTED for photo picker support
• POST_NOTIFICATIONS for notification runtime permission

The app doesn't use any foreground services or exact alarms, so no additional declarations are needed. The targetSdkVersion 34 upgrade is safe to proceed.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check AndroidManifest.xml for potential Android 14 requirements
echo "Checking for foreground service declarations..."
rg -l "android:foregroundServiceType" "app/android/app/src/main"

echo "Checking for exact alarm permission..."
rg -l "USE_EXACT_ALARM|SCHEDULE_EXACT_ALARM" "app/android/app/src/main"

echo "Checking for media permissions..."
rg -l "READ_MEDIA_" "app/android/app/src/main"

Length of output: 493

---

Script:

#!/bin/bash
# Let's check the actual content of AndroidManifest.xml to see what media permissions are declared
echo "Content of AndroidManifest.xml:"
cat app/android/app/src/main/AndroidManifest.xml

Length of output: 3268

---

51-51: Consider documenting the removal of dynamic SDK version

The change removes the flexibility to control targetSdkVersion through Flutter properties. If this is intentional, consider:

1. Adding a comment explaining why a fixed version is preferred
2. Updating related documentation about SDK version management

Let's check if this was a coordinated change:

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Experiment)
• @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.