Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

FirebaseAndroid: fix & remove nullability annotations #60

Merged
merged 1 commit into from
Apr 2, 2024

Conversation

compnerd
Copy link
Collaborator

@compnerd compnerd commented Apr 2, 2024

The nullability annotations seem to cause warnings due to -Wnullability-completeness. Correctly annotating the types as _Nullable JavaVM * _Nonnull seems to not work across Swift and C/C++. Rather than try to force this, simply avoid the nullability annotations.

Clear up the method registration which was never being invoked due to an early return in the success case.

The nullability annotations seem to cause warnings due to
`-Wnullability-completeness`. Correctly annotating the types as
`_Nullable JavaVM * _Nonnull` seems to not work across Swift and C/C++.
Rather than try to force this, simply avoid the nullability annotations.

Clear up the method registration which was never being invoked due to an
early return in the success case.
@compnerd compnerd merged commit 03fe03a into thebrowsercompany:main Apr 2, 2024
2 checks passed
@compnerd compnerd deleted the compnerd/nullability branch April 2, 2024 20:16
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.

2 participants