-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
feat(ios): UMP Consent on new arch #667
Conversation
To view this pull requests documentation preview, visit the following URL: docs.page/invertase/react-native-google-mobile-ads~667 Documentation is deployed and generated using docs.page. |
764362a
to
e16bb7b
Compare
e546cf5
to
def14f4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious about the async-ness on the type signatures but can't see anything truly wrong
Testing always good though if anyone else has time
Still async. But there is the possibility now to make some methods sync for new arch. Not sure what path we should take there, introduce new methods / breaking change? Send it back sync on the new arch, but wrap it in a promise for now... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think changing it to sync and taking a break really has any value for people personally, these are things people are doing on startup (where maybe, just maybe async isn't available)
🎉 This PR is included in version 14.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
UMP Consent on new arch
Note that importing types does (still) not work with codegen, so I moved the types to the spec directly.
Any folks that can test this? @TaylorDale @wjaykim @DoctorJohn @birdofpreyru