fix: update Composables Core to 1.37.0 for Expo DevClient compatibility

[leonelgalan]

User description

Summary

Updates com.composables:core dependency from 1.20.1 to 1.37.0 to resolve compatibility issues with Expo DevClient.

Problem

Expo DevClient uses Composables Core 1.37.0 and crashes when encountering version 1.20.1. This prevents React Native applications using Expo DevClient from properly integrating with the Rownd Android SDK v4.0.0.

Solution

Updated the Composables Core dependency to 1.37.0 (android/build.gradle:100), which is compatible with Expo DevClient.

Testing

• ✅ Android SDK v4.0.0 builds successfully with Composables Core 1.37.0
• ✅ All unit tests pass (1 test, 0 failures)
• ✅ Linting completed without errors
• ✅ Verified full integration: Built React Native Expo app (226MB APK) successfully with expo-dev-client 6.0.20 and io.rownd:android:4.0.0, both using Composables Core 1.37.0 with no conflicts

Related

This update enables the React Native package (https://github.com/rownd/react-native) to safely upgrade to Android SDK v4.0.0 without Expo DevClient compatibility issues.

🤖 Generated with Claude Code

---

PR Type

Bug fix

---

Description

• Updates com.composables:core dependency from 1.20.1 to 1.37.0 in android/build.gradle

• Resolves compatibility issues with Expo DevClient that crashes when encountering the older version

• Enables React Native applications using Expo DevClient to properly integrate with Rownd Android SDK v4.0.0

• All unit tests pass and linting completed without errors

• Verified full integration with React Native Expo app using expo-dev-client 6.0.20

---

Diagram Walkthrough

flowchart LR
  A["Composables Core<br/>1.20.1"] -- "Update dependency" --> B["Composables Core<br/>1.37.0"]
  B -- "Enables compatibility" --> C["Expo DevClient<br/>Integration"]
  C -- "Supports" --> D["React Native<br/>SDK v4.0.0"]

Loading

File Walkthrough

	Relevant files

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	No custom compliance provided Follow the guide to enable custom compliance check.

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[mhamann]

Thanks for the PR! I'll take a look at this on Friday and hopefully get it released.

[leonelgalan]

Thanks for the PR! I'll take a look at this on Friday and hopefully get it released.

Thank you guys! Claude got ahead of me and push the PR with gh, but I manage to see it working in our app by pushing the update to mavenLocal and a using it through a local copy of https://github.com/rownd/react-native.

The only questions I had left before I would have push the PR is should we stay on 1.37.0? The latest is 1.49.6? How should this change affect the android package version? Is it 4.1 or 4.0.1. No other change was needed so it seems the APIs used are all compatible.

[mhamann]

Overall, I'm in favor of jumping to the latest on dependencies as long as there aren't problematic changes requiring a lot of rework. (Or conflicts with other up/downstream packages.)

[leonelgalan]

The bottom sheet drag handle appears differently positioned in Composables Core 1.49.6 compared to 1.37.0, see screenshots.

1.37.0

No Warnings

1.49.6

Deprecation Warnings during Build

'fun Button(...): Unit' is deprecated. Use UnstyledButton instead.
'fun Dialog(...): Unit' is deprecated. This will go away in 2.0.

[mhamann]

Ah, we'll have to investigate that. Let's just merge 1.37 for now and kick the rest down the road a bit.