Bump version to 1.3.2 and update package name

[RajnishKMehta]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@RajnishKMehta has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 50 minutes and 6 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 50 minutes and 6 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b2fc4c3e-e1cc-49e3-a0ce-142260c1682f

📥 Commits

Reviewing files that changed from the base of the PR and between 8830d23 and 2dcffaa.

📒 Files selected for processing (1)

• app.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch Change-android-package-name

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🩺 Expo Doctor — All Checks Passed ✅

No issues found by expo-doctor.

Triggered by commit 2dcffaadcebe11a0e43e07af794282c1b1b2683e

[RajnishKMehta]

@coderabbitai review is thi compatible?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Fetch PR details
gh pr view 4 --repo RajnishKMehta/Scream2Wish --json title,body,files,baseRefName,headRefName

# Get the diff
gh pr diff 4 --repo RajnishKMehta/Scream2Wish

Length of output: 853

---

🏁 Script executed:

#!/bin/bash
# Check for Firebase config, eas.json, or other files referencing the old package name
fd -e json -e gradle . | head -30

# Check if google-services.json exists
fd "google-services.json" .

# Check eas.json
cat eas.json 2>/dev/null || echo "No eas.json found"

# Search for old package name references
rg "com.rajnishkmehta.scream2wish" --type-not binary

Length of output: 923

---

@RajnishKMehta Here is a compatibility analysis of the two changes in this PR:

---

✅ Version Bump (1.3.1 → 1.3.2)

This is a standard patch version increment and is fully compatible. This version number is required by Google Play, and should be incremented for each release. No issues here.

---

⚠️ Android Package Name Change

com.rajnishkmehta.scream2wish → io.github.rajnishkmehta.scream2wish

The package field is the unique identifier for your app on the Google Play Store — like the iOS bundle identifier, it is mandatory for publishing. Changing it has significant compatibility implications:

Concern	Impact
Existing installs	Android treats apps by package name. Users with the old app installed will not receive an update — they'll need to uninstall and reinstall.
Google Play Store	If the app is already published under com.rajnishkmehta.scream2wish, the package name on an existing Play Store listing cannot be changed. A new listing would need to be created.
EAS Keystore	Since the Android Application ID changed, the EAS CLI will prompt you to generate a new Keystore for Android.
OTA Updates	Existing installs won't receive OTA updates from the new package since they're treated as a different app entirely.
New package name format	io.github.rajnishkmehta.scream2wish is a valid Android Application ID — it contains only valid characters separated by periods, with each component starting with a lowercase letter. ✅
Other config files	No google-services.json or other files were found referencing the old package name, so no additional updates are needed. ✅

---

Summary

• If this app has not been published to the Play Store yet, this change is safe to proceed with (just be aware of the new EAS keystore requirement).
• If this app is already live on the Play Store under the old package name, the package name cannot be changed on the existing listing — it would require a brand-new app submission, and existing users would not automatically migrate.

[RajnishKMehta]

@coderabbitai help

[coderabbitai]

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

CodeRabbit commands

These commands are invoked using PR/Issue 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 evaluate custom pre-merge check --instructions <custom-checks-instructions> --name <custom-checks-title> [--mode <error|warning>] to validate the custom pre-merge checks instructions. Defaults to error when --mode is omitted.
• @coderabbitai ignore pre-merge checks to override pre-merge checks and get an approval on PR.
• @coderabbitai run pre-merge checks to run pre-merge checks on the pull request.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve merge conflict to automatically resolve merge conflicts.
• @coderabbitai autofix to automatically fix issues identified in unresolved review comments.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai generate configuration to create a PR that adds the current resolved configuration as .coderabbit.yaml (or show it if already present).
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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.
• You can also validate your configuration using the online YAML validator.
• 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

Status, support, documentation and community

• Visit our status page to check the current availability of CodeRabbit.
• Create a ticket on our support page for assistance with any issues or questions.
• Visit our documentation site for detailed information on how to use CodeRabbit.
• Join our Discord community to connect with other users and get help from the community.
• Follow us on X/Twitter for updates and announcements.