Skip to content

Conversation

@ucswift
Copy link
Member

@ucswift ucswift commented Aug 17, 2025

Summary by CodeRabbit

  • New Features

    • Enabled native system call UI integration (CallKeep) for VoIP/in-app calling on supported platforms, providing familiar call screens and controls.
  • Chores

    • Updated call-related dependencies and configuration to support the new call UI integration.
    • Replaced the call library source with a maintained repository and added the corresponding config plugin to the build setup.

@ucswift
Copy link
Member Author

ucswift commented Aug 17, 2025

@coderabbitai
Copy link

coderabbitai bot commented Aug 17, 2025

Walkthrough

Added the CallKeep Expo config plugin to app.config.ts and updated dependencies in package.json by adding @config-plugins/react-native-callkeep and pointing react-native-callkeep to a GitHub repository URL.

Changes

Cohort / File(s) Summary
Expo config plugin integration
app.config.ts
Inserted '@config-plugins/react-native-callkeep' into the plugins array between existing plugins.
Dependency updates
package.json
Added dependency '@config-plugins/react-native-callkeep' (^11.0.0). Updated 'react-native-callkeep' from ^4.3.16 to a GitHub URL (Irfanwani/react-native-callkeep).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A hop, a skip—CallKeep in tow,
I twitch my ears where config grows.
New plugin seeds in Expo’s field,
Dependencies neatly tilled and sealed.
With gentle paws, I nudge the build—
Ring, ring! The burrow’s phones are thrilled. 🐇☎️

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch develop

🪧 Tips

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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai 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.
  • 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, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (2)
app.config.ts (1)

263-263: Verify Android 14+ permission and plugin ordering

Please manually confirm the following:

  • After running expo prebuild, open android/app/src/main/AndroidManifest.xml and verify that it contains
    <uses-permission android:name="android.permission.FOREGROUND_SERVICE_PHONE_CALL"/>.
    If it’s missing, add 'android.permission.FOREGROUND_SERVICE_PHONE_CALL' to the android.permissions array in your app.config.ts.
  • In app.config.ts, ensure that
    '@config-plugins/react-native-callkeep'
    appears before your customManifest.plugin.js entry in the plugins array, so your PhoneAccount/ConnectionService tweaks aren’t overridden.

Suggested check after prebuild:

rg -nA2 'FOREGROUND_SERVICE_PHONE_CALL' android/app/src/main/AndroidManifest.xml
package.json (1)

49-49: Use tilde (~) instead of caret (^) to minimize config plugin breakage

Most Expo config plugins are sensitive to minor changes. To reduce accidental config drift during CI/CD, prefer ~11.0.0 over ^11.0.0 for @config-plugins/react-native-callkeep (consistent with how you pin @config-plugins/react-native-webrtc).

Apply:

-    "@config-plugins/react-native-callkeep": "^11.0.0",
+    "@config-plugins/react-native-callkeep": "~11.0.0",
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 84ef055 and c1f5b6a.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (2)
  • app.config.ts (1 hunks)
  • package.json (2 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursorrules)

**/*.{ts,tsx}: Write concise, type-safe TypeScript code
Use camelCase for variable and function names (e.g., isFetchingData, handleUserInput)
Use TypeScript for all components, favoring interfaces for props and state
Avoid using any; strive for precise types
Use Expo SecureStore for sensitive data
Use zustand for state management
Use react-query for data fetching and caching
Use react-i18next for internationalization
Use react-native-mmkv for local storage
Use axios for API requests

**/*.{ts,tsx}: Write concise, type-safe TypeScript code
Use camelCase for variable and function names
Use TypeScript for all components, favoring interfaces for props and state
Avoid using any; strive for precise types
Use React Navigation for handling navigation and deep linking
Handle errors gracefully and provide user feedback
Use Expo's SecureStore for sensitive data
Use zustand for state management
Use react-query for data fetching
Use react-i18next for internationalization
Use react-native-mmkv for local storage
Use axios for API requests

Files:

  • app.config.ts
**/*

📄 CodeRabbit Inference Engine (.cursorrules)

Directory and file names should be lowercase and hyphenated (e.g., user-profile, chat-screen)

Files:

  • app.config.ts
  • package.json

"react-native-base64": "~0.2.1",
"react-native-ble-manager": "^12.1.5",
"react-native-callkeep": "^4.3.16",
"react-native-callkeep": "https://github.com/Irfanwani/react-native-callkeep",
Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Pin the GitHub dependency to a commit/tag for reproducible builds

Using a moving GitHub branch URL can produce non-deterministic installs and surprise build failures. Pin to a specific commit or tag.

Example (replace with the exact commit you need):

-    "react-native-callkeep": "https://github.com/Irfanwani/react-native-callkeep",
+    "react-native-callkeep": "github:Irfanwani/react-native-callkeep#<commit-sha>",

Also, briefly document in the PR description or a comment why the fork is required and which upstream issue/PR it addresses (helps future maintainers).

To confirm what you’re installing, run:


🏁 Script executed:

#!/bin/bash
# Shows the resolved URL for the dependency after install (run locally where node_modules is present)
node -e "const p=require('./package.json'); console.log(p.dependencies['react-native-callkeep'])"

Length of output: 162


Pin GitHub dependency to a specific commit for reproducible installs

Using a floating URL for react-native-callkeep can lead to non-deterministic installs and unexpected breakages when the remote branch advances. Please update your dependency to point at a specific commit or tag, and document why you’re using this fork (e.g. which upstream issue or PR it addresses).

• File: package.json (line 148)
• Replace:

-  "react-native-callkeep": "https://github.com/Irfanwani/react-native-callkeep",
+  "react-native-callkeep": "github:Irfanwani/react-native-callkeep#<commit-sha>",

• In your PR description (or here in a comment), note:
– The reason this fork is needed
– Which upstream issue/PR it fixes

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"react-native-callkeep": "https://github.com/Irfanwani/react-native-callkeep",
"react-native-callkeep": "github:Irfanwani/react-native-callkeep#<commit-sha>",
🤖 Prompt for AI Agents
In package.json around line 148, the dependency "react-native-callkeep" is
pointing to a floating GitHub branch URL which makes installs non-deterministic;
update the value to reference a specific commit SHA or a tag (e.g.
"https://github.com/Irfanwani/react-native-callkeep.git#<commit-sha>") to pin
the dependency, run npm/yarn install to verify, and update the PR description to
explain why this fork is used and which upstream issue/PR it addresses (include
link and short rationale).

@ucswift
Copy link
Member Author

ucswift commented Aug 17, 2025

Approve

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

This PR is approved.

@ucswift ucswift merged commit 1f4fb1e into master Aug 17, 2025
7 checks passed
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.

2 participants