Skip to content

chore(apple): fix build issues discovered internally #1178

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 5 commits into from
Feb 2, 2025

Conversation

Saadnajmi
Copy link
Contributor

@Saadnajmi Saadnajmi commented Jan 31, 2025

Summary

At my side of Microsoft, we have recently "vendored" a couple of libraries. Which means, we started building them from source using our own generated Xcode project (not the one cocoapods generates), which has much stricter build flags / treats warnings as errors. In doing so, I caught a couple of issues in React Native async-storage I'd like to push back up!

Namely:

  • Fix warnings where we need to add a bunch of either __nullable or __nonnull specifiers.
  • Fix a "declaration of variable shadows another local variable" where we had two NSError *error = nil declarations in a row
  • Fix another "declaration of variable shadows another local variable" with two NSError variables by renaming one of them
  • Add an __unused clang tag to a parameter
  • Add __autoreleaseing clang tags to two more parameters.
    • The error internally without these was Method parameter of type 'NSMutableArray<NSDictionary *> *__autoreleasing *' with no explicit ownership, for the record.

Test Plan

CI should pass

Copy link

changeset-bot bot commented Jan 31, 2025

🦋 Changeset detected

Latest commit: b0d402d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@react-native-async-storage/async-storage Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@tido64
Copy link
Member

tido64 commented Jan 31, 2025

Thanks for the fixes 🙏

@tido64
Copy link
Member

tido64 commented Jan 31, 2025

⚠️ No Changeset found

Latest commit: abafda4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Oh, can you add a change log?

@tido64 tido64 merged commit 5042047 into react-native-async-storage:main Feb 2, 2025
8 checks passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants