Skip to content

Conversation

@jaskfla
Copy link
Contributor

@jaskfla jaskfla commented Nov 20, 2025

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jaskfla, I'm Gemini Code Assist1! 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 updates the application's target Android API level to 35. This change is crucial for maintaining compatibility with the latest Android operating system (Android 15), ensuring the application can utilize new platform features, and adhering to the most recent security and privacy standards mandated by Google Play.

Highlights

  • Android API Level Update: The target Android API level for the application has been updated from 34 to 35, aligning with Android 15.
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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request aims to update the Android target API level to 35 (Android 15). While updating targetSdkVersion is a good step, the compileSdkVersion has not been updated in tandem. It's crucial to align compileSdkVersion with targetSdkVersion to ensure the app is built and tested against the new platform's APIs and behavioral changes. I've added a comment to address this oversight.

minSdkVersion = 21
compileSdkVersion = 34
targetSdkVersion = 34
targetSdkVersion = 35
Copy link
Contributor

Choose a reason for hiding this comment

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

high

While updating targetSdkVersion to 35 is correct, the compileSdkVersion on line 7 should also be updated to 35. It is a best practice to keep compileSdkVersion and targetSdkVersion at the same value. This ensures your application is compiled against the APIs of the version it targets, allowing you to handle new platform behaviors and requirements correctly. Without this change, you might encounter unexpected runtime issues on Android 15 devices.

@jaskfla jaskfla force-pushed the rn-1770-android-api-35 branch from 61dc322 to 39bf35c Compare December 1, 2025 23:55
Applied all Android-related changes and some iOS-related changes
* Returns the name of the main component registered from JavaScript. This is used to schedule
* rendering of the component.
*/
override fun getMainComponentName(): String = "MediTrak"
Copy link

Choose a reason for hiding this comment

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

Bug: Android component name doesn't match JavaScript registration

getMainComponentName() returns "MediTrak" but the JavaScript code in main.jsx registers the app component as 'TupaiaMediTrak'. iOS (AppDelegate.swift) correctly uses "TupaiaMediTrak". This mismatch will cause the Android app to crash on startup because React Native won't find a component with the name "MediTrak".

Fix in Cursor Fix in Web

<key>UIRequiredDeviceCapabilities</key>
<array>
<string>armv7</string>
<string>armv64</string>
Copy link

Choose a reason for hiding this comment

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

Bug: Invalid iOS device capability architecture value typo

The UIRequiredDeviceCapabilities key specifies armv64 which is not a valid iOS device capability. The correct value is arm64. This typo could cause App Store submission rejection or unexpected device compatibility issues.

Fix in Cursor Fix in Web

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.

1 participant