Skip to content

Conversation

@naipaka
Copy link

@naipaka naipaka commented Dec 20, 2025

Related Issue

Fixes #2283

Changes

Changed return type from Future<CustomerSheetResult?> to Future<void> to match actual behavior and align with React Native SDK.

The method always returned null on success:

  • iOS: returns empty array []
  • Android: returns empty map

The type CustomerSheetResult? was misleading. This fixes the type definition to match reality.

If there was an intentional reason for the CustomerSheetResult? return type that I may have missed, I'd appreciate any insights. I want to ensure this change aligns with the package's design goals.

@naipaka
Copy link
Author

naipaka commented Dec 30, 2025

@jonasbark @remonh87

Hi, I submitted this PR on Dec 20 to fix issue #2283.

PR #2292 (submitted Dec 27) has an identical title and the same logic changes, and a reviewer has been assigned to it.

Could you please let me know if there's something I should improve in this PR? I'd be happy to address any feedback.

Thank you for your time.

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.

Misleading return type for initCustomerSheet

1 participant