fix(android): support react native 0.77

[believer]

Thanks for this great library!

Due to this change in React Native core getString now returns String?. Since the when condition checks that the current value is a string, I think it's fine to type cast the result as a String. I tested it locally and it resolves the error.

Alternatively, we could go the route of only adding the value if it exists using:

	ReadableType.String -> sizes.getString(i)?.let { result.add(it) }

[vercel]

@believer is attempting to deploy a commit to the Jovanni's projects Team on Vercel.

A member of the Team first needs to authorize it.

[codeclimate]

Code Climate has analyzed commit c990fd6 and detected 0 issues on this pull request.

View more on Code Climate.

[believer]

@lodev09 Hi! What do you think about these changes to support React Native 0.77?

[lodev09]

Hey @believer, thanks for the PR. I would prefer null check instead of casting. I'm not sure if this will cause compile issue on older RN version tho.

Thanks!

[believer]

Changed it to a null check instead, I agree that it's cleaner. I doesn't seem to cause a compile error, but it displays a warning:

Unnecessary safe call on a non-null receiver of type 'kotlin. String'.

We could suppress the warning if we feel like it:

// React Native < 0.77 used String for getString, but 0.77
// changed it to String?. Suppress the error for older APIs.
@Suppress("UNNECESSARY_SAFE_CALL")

[lodev09]

Yep, suppress annotation should be fine! Thanks @believer

[lodev09]

Goods 👍
Just add the suppress annotation when you can. Thanks!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-true-sheet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 27, 2025 3:55pm

[believer]

Awesome, will fix it first thing on Monday!

[lodev09]

LGTM. Thank you!

[lodev09]

🚀 This pull request is included in v1.1.0. See Release 1.1.0 for release notes.