Skip to content

Conversation

@lollipopkit
Copy link
Owner

@lollipopkit lollipopkit commented Sep 3, 2025

Fixes #892

Summary by Sourcery

Improve CI performance with shallow checkout and caching, update macOS entitlements to resolve App Store rejection, and add supporting wiki documentation.

Bug Fixes:

  • Update macOS debug and release entitlements to comply with App Store requirements

CI:

  • Shallow clone repository and cache Flutter SDK in CI
  • Add caching for pub dependencies to speed up workflow
  • Remove commented-out Dart formatting check

Documentation:

  • Add flutter_server_box wiki file

@sourcery-ai
Copy link

sourcery-ai bot commented Sep 3, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR resolves macOS App Store rejection by refining the CI pipeline for faster, repeatable Flutter analysis and updating macOS entitlements for App Store compliance, plus adding a supportive wiki.

File-Level Changes

Change Details Files
Optimize GitHub Actions analysis workflow with shallow clones and caching
  • Enable fetch-depth=1 for checkout
  • Activate Flutter SDK caching with a dynamic cache key
  • Introduce a separate cache step for pub dependencies
  • Remove obsolete Dart format verification step
.github/workflows/analysis.yml
Adjust macOS entitlements to meet App Store requirements
  • Update DebugProfile.entitlements with required capabilities
  • Update Release.entitlements to include App Store–mandated keys
macos/Runner/DebugProfile.entitlements
macos/Runner/Release.entitlements
Add documentation for flutter_server_box setup
  • Create new wiki file outlining server box usage
  • Populate flutter_server_box.wiki with setup and usage instructions
flutter_server_box.wiki

Assessment against linked issues

Issue Objective Addressed Explanation
#892 Modify the project configuration or code to resolve the macOS App Store rejection.

Possibly linked issues


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!

Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments

### Comment 1
<location> `.github/workflows/analysis.yml:32` </location>
<code_context>
+      - name: Cache pub dependencies
+        uses: actions/cache@v4
+        with:
+          path: |
+            ${{ env.PUB_CACHE }}
+            ~/.pub-cache
+            ${{ runner.tool_cache }}/flutter
+          key: ${{ runner.os }}-pub-${{ hashFiles('**/pubspec.lock') }}
+          restore-keys: |
</code_context>

<issue_to_address>
Including runner.tool_cache/flutter in pub cache may be unnecessary.

Caching this directory may unnecessarily increase cache size and restore times. Please verify if it's essential for dependency caching or should be handled separately.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
          path: |
            ${{ env.PUB_CACHE }}
            ~/.pub-cache
            ${{ runner.tool_cache }}/flutter
=======
          path: |
            ${{ env.PUB_CACHE }}
            ~/.pub-cache
>>>>>>> REPLACE

</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment on lines +32 to +35
path: |
${{ env.PUB_CACHE }}
~/.pub-cache
${{ runner.tool_cache }}/flutter
Copy link

Choose a reason for hiding this comment

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

suggestion (performance): Including runner.tool_cache/flutter in pub cache may be unnecessary.

Caching this directory may unnecessarily increase cache size and restore times. Please verify if it's essential for dependency caching or should be handled separately.

Suggested change
path: |
${{ env.PUB_CACHE }}
~/.pub-cache
${{ runner.tool_cache }}/flutter
path: |
${{ env.PUB_CACHE }}
~/.pub-cache

@lollipopkit lollipopkit merged commit a94be6c into main Sep 3, 2025
3 checks passed
@lollipopkit lollipopkit deleted the lollipopkit/issue892 branch September 3, 2025 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: macOS appstore rejection

2 participants