Added namespace to build.gradle and updated flutter_foreground_task

[ILYA-2606]

Android Gradle Plugin requirements
https://d.android.com/r/tools/upgrade-assistant/set-namespace

Summary by CodeRabbit

• Chores
  • Enhanced Android configuration with refined settings to support both modern and legacy devices, ensuring a smoother experience for all users.
  • Upgraded background task management to a more stable version, resulting in improved performance and reliability during screen recording sessions.
  • Overall improvements focus on delivering a more robust and seamless usage experience without altering visible functionalities.

[coderabbitai]

Walkthrough

This pull request makes two primary changes in the flutter_screen_recording plugin. In the Android build configuration (build.gradle), a conditional block is added to set the namespace if the property exists, improving compatibility with earlier AGP versions. Additionally, the dependency version for flutter_foreground_task in the pubspec.yaml file is updated from ^6.0.0+1 to ^8.0.0.

Changes

File(s)	Change Summary
flutter_screen_recording/android/build.gradle	Added a conditional block in the Android configuration to assign a namespace if the "namespace" property exists.
flutter_screen_recording/pubspec.yaml	Updated dependency version for flutter_foreground_task from ^6.0.0+1 to ^8.0.0.

Sequence Diagram(s)

sequenceDiagram
    participant Gradle as Gradle Build Process
    participant Config as build.gradle
    Gradle->>Config: Evaluate Android configuration
    alt Namespace property exists
       Config->>Gradle: Set namespace to "com.isvisoft.flutter_screen_recording"
    else Namespace property not found
       Gradle->>Config: Proceed with default configuration
    end

Loading

Poem

I'm a rabbit coding through the night,
Hopping on changes, everything feels just right.
Conditional checks and versions anew,
My code garden now has a fresher view.
With every update, I rejoice with glee 🐰
Bound by lines of code and endless harmony!

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

flutter_screen_recording/android/build.gradle (1)

31-34: Conditional Namespace Assignment for AGP Compatibility

The conditional block that assigns the namespace only if the property exists (i.e., if (project.android.hasProperty("namespace"))) is a good way to maintain compatibility with older versions of the Android Gradle Plugin. However, consider adding an inline comment that further explains:

• Why this conditional check is necessary.
• Which AGP versions require this handling.

This will help future maintainers understand the context behind this logic.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7843347 and 6fb493c.

📒 Files selected for processing (2)

• flutter_screen_recording/android/build.gradle (1 hunks)
• flutter_screen_recording/pubspec.yaml (1 hunks)

🔇 Additional comments (1)

flutter_screen_recording/pubspec.yaml (1)

13-13: Dependency Version Update – Verify Compatibility

The dependency for flutter_foreground_task has been upgraded to ^8.0.0. Please ensure that any breaking changes or new requirements introduced in version 8.0.0 are compatible with the rest of the plugin, and update documentation or tests as necessary.

[Zujaj]

@salime45 kindly merge this solution, I am also facing the same issue on my end!

[azaan-aftab]

The same issue happened with me as well. Kindly resolve it as early as possible.