Hi,
On our iOS project we've set the TREAT_WARNINGS_AS_ERRORS flag to YES and we've noticed the following error in the UMPConsentForm:
Conflicting nullability specifier on return types, 'nullable' conflicts with existing specifier 'nonnull'
This error arises from the use of - (nullable instancetype)init NS_UNAVAILABLE;, where the nullable specifier is causing a conflict.
Is there any chance this could be fixed?
I’ve attached an example project to help demonstrate the issue.
UserMessagingExample.zip
Thanks!
Hi,
Please note that the presents a privacy options form from the provided viewController if UMPConsentInformation.sharedInstance.privacyOptionsRequirementStatus is UMPPrivacyOptionsRequirementStatusRequired. Calls completionHandler with nil error after the user selects an option and the form is dismissed, or on the next run loop with a non-nil error if no form is presented. Must be called on the main queue. For more information visit this UMPConsentForm document.
The sample project you provided is currently not executable. Kindly share runnable sample project in order for us to proceed with further investigation.
If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, kindly provide requested information to us via reply to author option or using the steps below:
1. Navigate to
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.
Mobile Ads SDK Team |
On 11 Jun 2024, at 18:36, Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google> wrote:
Hi,
I will raise this concern to the team. Meanwhile, i would suggest to change TREAT_WARNINGS_AS_ERRORS to No for both debug and release, delete the derived data and run the project. it will run and keep and eye on iOS release.
Thanks