Skip to content

RG-T133 iOS Perms Fix - #283

Merged
ucswift merged 1 commit into
masterfrom
develop
Aug 27, 2026
Merged

RG-T133 iOS Perms Fix#283
ucswift merged 1 commit into
masterfrom
develop

Conversation

@ucswift

@ucswift ucswift commented Aug 27, 2026

Copy link
Copy Markdown
Member

This pull request updates the iOS app permission configuration to better match the app’s actual usage and improve App Store–facing permission disclosures.

What changed

  • Expanded iOS permission descriptions for:

    • Bluetooth
    • Location (foreground and background)
    • Photo library
    • Camera
    • Microphone
  • Added explicit permission messaging for photo library and camera access used when attaching photos to calls/chat and during video sessions.

  • Added a camera permission configuration for the WebRTC plugin to align video-related camera access messaging.

  • Updated the Secure Store configuration to explicitly disable Face ID permission text, since biometric-gated secure storage is not used.

  • Updated the Location configuration to explicitly disable motion usage permission text, since motion activity APIs are not used.

Functional impact

  • iOS users will now see clearer, more specific explanations for why the app requests access to device features.
  • The app avoids requesting or declaring unused iOS permissions related to Face ID and Motion.
  • Overall, the app’s permission prompts and iOS metadata are better aligned with the app’s features such as Push-to-Talk, AVL/background location, media attachments, and video sessions.

Summary by CodeRabbit

  • New Features

    • Added clearer iOS permission descriptions for Bluetooth, location, audio, camera, and photo access.
    • Improved camera permission messaging for video calls.
    • Added explicit photo picker configuration.
  • Bug Fixes

    • Removed unused Face ID and motion permission declarations.
    • Updated secure storage and audio permission configuration.

@Resgrid-Bot

Resgrid-Bot commented Aug 27, 2026

Copy link
Copy Markdown

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

  • Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug
Performance
Security
Business Logic

Access your configuration settings here.

Comment thread app.config.ts
locationAlwaysAndWhenInUsePermission: 'Allow Resgrid Unit to use your location for department updates.',
locationAlwaysPermission: 'Resgrid Unit needs to track your location for department AVL.',
locationWhenInUsePermission:
'Resgrid Unit uses your location while you use the app to show your unit position on the department map and to attach your coordinates when you set a status or respond to a call. For example, when you respond to a call, your location is shared with dispatch so they can see which unit is closest to the scene.',

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

kody code-review Kody Rules high

Sensitive permission copy in app.config.ts exposes operational and health-adjacent incident details by describing live location sharing with dispatch and incident-scene proximity. Minimize the permission text in app.config.ts, including at app.config.ts:167-167 and app.config.ts:169-169, and remove scenario-specific references such as incident scenes or dispatch tracking examples.

Kody rule violation: Do not log PHI; mask and drop sensitive fields

'Resgrid Unit uses your location while you use the app to show your unit position on the department map and to support dispatch coordination for active incidents.',
Prompt for LLM

File app.config.ts:

Line 165:

Sensitive permission copy in app.config.ts exposes operational and health-adjacent incident details by describing live location sharing with dispatch and incident-scene proximity. Minimize the permission text in app.config.ts, including at app.config.ts:167-167 and app.config.ts:169-169, and remove scenario-specific references such as incident scenes or dispatch tracking examples.

Suggested Code:

'Resgrid Unit uses your location while you use the app to show your unit position on the department map and to support dispatch coordination for active incidents.',

Talk to Kody by mentioning @kody

Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.

@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: be3c75a8-9f62-429d-9178-eb88343f94bd

📥 Commits

Reviewing files that changed from the base of the PR and between 0abbef1 and 39fd79b.

📒 Files selected for processing (1)
  • app.config.ts

Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.


📝 Walkthrough

Walkthrough

Updated app.config.ts with detailed iOS permission descriptions and explicit Expo plugin settings. Disabled unused Face ID and motion permission declarations.

Changes

iOS permission and plugin configuration

Layer / File(s) Summary
Permission descriptions and plugin settings
app.config.ts
Expanded Bluetooth, location, audio, camera, and photo-library descriptions. Disabled Face ID and motion permission declarations. Added expo-image-picker settings and configured expo-secure-store and WebRTC permissions.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: 🔵 Low · up to 39fd7

The PR improves iOS permission disclosures and removes unused Face ID and motion declarations. Some descriptions still include scenario-specific emergency, dispatch, and responder wording, creating a bounded App Store or privacy-review risk; the change is otherwise mergeable with owner awareness.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: fixing iOS permission configuration. It is concise and specific enough for repository history.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch develop

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

@ucswift

ucswift commented Aug 27, 2026

Copy link
Copy Markdown
Member Author

Approve

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

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 96b4cf5 into master Aug 27, 2026
20 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