fix: resolve EXC_BAD_ACCESS crash caused by Int32 type mismatch in native bridge

[subhankarmaiti]

Fixes EXC_BAD_ACCESS (code=1, address=0x20) crash on iOS introduced in #1414 when upgrading to React Native 0.83.0.

Changes Made

iOS Native Bridge (ios/A0Auth0.mm)

• Changed all numeric parameters from NSInteger to double to match JavaScript's number type
• Added explicit (NSInteger) casts when passing values to Swift methods
• Updated parameters: minTTL in getCredentials, hasValidCredentials, getApiCredentials
• Updated webAuth method to use doubleValue instead of integerValue for maxAge, leeway, and safariViewControllerPresentationStyle

Android

• ✅ No changes required - Android implementation was already using Double type correctly

🧪 Testing

• iOS example app builds and runs without crashes
• Android example app builds and runs (no regression)
• All numeric parameters pass correctly through the native bridge
• Unit tests pass
• TypeScript type checking passes

🔗 Related

• Fixes issue introduced in chore: upgrade React Native to 0.83.0 and update dev dependencies #1414 (React Native 0.83.0 upgrade)

[NandanPrabhu]

@subhankarmaiti were you able to replicate the crash?

[subhankarmaiti]

Yes @NandanPrabhu , and after this change it got fixed

[Copilot]

Pull request overview

This PR fixes an EXC_BAD_ACCESS crash on iOS that occurred after upgrading to React Native 0.83.0, caused by a type mismatch in the native bridge between JavaScript's number type and Objective-C's NSInteger type.

• Changed iOS native bridge parameter types from NSInteger to double to match JavaScript's number type
• Added explicit (NSInteger) casts when passing values to Swift methods that expect Int
• Aligned iOS implementation with Android, which already uses Double for these parameters

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.