Weekly GitHub Report for FGA

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is v3030

1.2 Version Information:

The version released on May 25, 2026, includes key updates such as enhanced GitHub workflows using commit SHA, an upgrade of Gradle to version 9.5.1, and expanded support features. These improvements focus on development process optimization and broader functionality support.

Click here to view the full release notes!

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. [BUG] Not working, android said i have to choose a folder but it's protected: This issue describes a problem where the user is unable to grant the app access to a required folder on their Android device because the folder is protected, preventing the app from functioning properly. The user reports that despite attempts to create a new folder and using different methods like shizuku for access, the app still cannot access internal storage folders after a recent update.

   • The comments include requests for screenshots to better understand the problem, suggestions to create a new folder named "FGA" in different directories, and confirmation from the user that the issue persists due to the app losing access to internal folders after the latest update, while older versions do not have this problem.
   • Number of comments this week: 6

2. Custom Game Area (black bars) megathread: This issue is a megathread dedicated to automatically calculating Custom Game Area values for devices that display black bars when playing Fate/Grand Order, helping users adjust offsets to ensure proper screen interaction. It provides instructions on how to identify if black bars are present, how to post screenshots for offset calculation, and notes that many devices no longer require manual offsets due to recent updates and system settings adjustments.

   • The comment section consists mainly of users posting screenshots of their devices with black bars to receive offset values, troubleshooting advice about play button placement and system settings, and confirmations of working offsets; the discussion also includes guidance on handling devices without black bars, issues caused by screen recording or overlays, and updates about changes in device behavior after game or OS updates.
   • Number of comments this week: 2

Since there were fewer than 5 open issues, all of the open issues have been listed above.

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

As of our latest update, there are no stale issues for the project this week.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 0

Summarized Issues:

As of our latest update, there are no open issues for the project this week.

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 2

Summarized Issues:

• App Crashes on Bluestacks Air for Apple Silicon Mac: The Fate-Grand-Automata app crashes immediately upon opening on Bluestacks Air for Apple Silicon Mac after the latest update, despite attempts to reinstall both the app and emulator. Users have also followed troubleshooting steps but the issue persists, indicating a critical compatibility or update-related problem.
• issues/2267

• Auto-Set ON/OFF Feature Malfunction: After the addition of the Auto-Set ON/OFF feature, the automatic selection function for EXP Embers to enhance Servants stopped working. This issue affects the app's core automation functionality, reducing user convenience and efficiency.
• issues/2268

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 2

Key Open Pull Requests

1. Add 6 new default support Craft Essences: This pull request adds six new default support Craft Essences to the project, including cropped 720p template images and proper localization mappings with names sourced from the FGO wiki, such as Beyond the Night Without the Snow Flower and Chaldea Dinnertime.

• URL: pull/2275

• Associated Commits: 3f708

2. Fix auto-enhancement for KR and CN: This pull request fixes the auto-enhancement feature specifically for the Korean (KR) and Chinese (CN) versions of the project, addressing issue #2243.

• URL: pull/2276

• Associated Commits: 169c2

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 9

Key Closed Pull Requests

1. chore: Update Project configuration: This pull request updates the project configuration by upgrading the Java version from 11 to 17, refactoring dependency and plugin management for improved consistency and centralization, enhancing Gradle build scripts for better organization and modern practices, and cleaning up redundant entries in .gitignore files across multiple modules to streamline the build process and repository management.

• URL: pull/2003

• Associated Commits: 5b39f, 3db04, 24512, 81779, f8619, 74172, 19bab, e3df9, de845, 6ffdf, 14f58, dbca7, c2f3a, 8bb01, 8765e, 1e894, db751, 98e74

2. Completed runs on play button: This pull request implements the feature to display completed runs on the play button using a BadgedBox indicator, refines the visual presentation by adjusting badge colors, and removes the storage of completed runs from preferences to enhance the user interface and experience.

• URL: pull/1820

• Associated Commits: 5d085, cc742, d9973, 4285f, 8e52f, 605fb

3. chore: add param for hilt injected parameters: This pull request adds parameters for Hilt-injected dependencies and marks more elements as parameter-only, improving dependency injection handling in the project.

• URL: pull/2081

• Associated Commits: 53e0d, 0b067, 773d6, 98402, 77883, b36c0

Other Closed Pull Requests

• Codebase cleanup and optimization: Multiple pull requests focus on improving the codebase by enhancing initialization order with a GameServers registry, replacing Gson with kotlinx.serialization, adopting type-safe navigation routes, updating UI components to Compose reorderable, fixing UI issues on the Spam screen, and optimizing Tesseract OCR training data. These changes collectively improve maintainability, UI responsiveness, and OCR performance.
• [pull/2269]

• Linting and code quality improvements: One pull request removes unnecessary linting suppressions by using MTL to fix linter problems in the Script Manager, addressing related lint errors and improving overall code quality. This cleanup helps maintain a cleaner and more reliable codebase.
• [pull/1932]

• Build performance enhancement: A pull request enables the Gradle configuration cache to improve build times in the project, contributing to faster development cycles and more efficient builds.
• [pull/2080]

• Card type pattern priority system: A pull request introduces a new card type pattern priority system with associated models and a selector component that allows defining and matching per-wave, priority-ordered B/A/Q card type patterns independently from the existing whole-hand card priority ranking. It also adds error handling for invalid patterns and comprehensive unit tests, though it does not yet integrate this selector into the main application logic.
• [pull/2271]

• Navigation framework update: One pull request migrates the project to Navigation 3, updating the navigation framework to the latest version to keep the project current with modern navigation practices.
• [pull/2272]

• OpenCV crash workaround on Bluestacks Air: A pull request adds a workaround to prevent OpenCV from crashing on Bluestacks Air running on macOS and reports the issue to KleidiCV maintainers for further evaluation. This ensures better stability on specific environments.
• [pull/2274]

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.

Access Last Week's Newsletter:

• Link