fix: Add consumer proguard rules to fix release build crash

[syed-tp]

• Previously, a client faced crash issues on release builds caused by aggressive R8 optimization.
• Add consumer-rules.pro to preserve DownloadHelper and Callback, preventing the AbstractMethodError during downloads.
• Update tpstreamsAndroidPlayerVersion to 1.1.8.

[gemini-code-assist]

Summary of Changes

Hello @syed-tp, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical issue where release builds were crashing due to aggressive R8 optimization. By introducing specific ProGuard rules, it ensures that essential components for download functionality are retained, thereby stabilizing the application in production environments. Additionally, it updates a core dependency to its latest patch version.

Highlights

• R8 Optimization Fix: Introduced consumer-rules.pro to prevent aggressive R8 optimization from stripping necessary classes, which previously caused AbstractMethodError in release builds.
• Class Preservation: Explicitly preserves androidx.media3.exoplayer.offline.DownloadHelper and its Callback interface to ensure their methods are not incorrectly stripped or renamed during the build process.
• Dependency Update: Updated the tpstreamsAndroidPlayerVersion from 1.1.7 to 1.1.8 in gradle.properties.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​turbo@​1.13.4
	npm/​react-native-builder-bob@​0.40.11
	npm/​react@​19.0.0
	npm/​react-native-webview@​13.16.0
	npm/​react-native-monorepo-config@​0.1.9
	npm/​typescript@​5.4.5
	npm/​react-native@​0.79.2
	npm/​release-it@​17.11.0
	npm/​prettier@​3.5.3

View full report

[gemini-code-assist]

Code Review

This pull request addresses a crash in release builds by adding consumer Proguard rules and updating the tpstreamsAndroidPlayerVersion. The changes look correct and should resolve the issue. I have provided a couple of suggestions to improve the Proguard rule specificity and adhere to file formatting best practices.