-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
UMP ConsentForm.ShowPrivacyOptionsForm getting an error everytime for US messages #3695
Comments
I was unable to replicate this. Can you share anymore details ? |
Hi I am facing same issue. I'm trying to simulate consents for DebugGeography.RegulatedUSState. In my tests I always use ConsentInformation.Reset(); I have a button for the user to manage their data consent, as instructed in the documentation. In my tests, when pressed, the form appears for both DebugGeography.RegulatedUSState and DebugGeography.EEA. However, when I'm using DebugGeography.RegulatedUSState, when I finish using the form. The same error mentioned in the first post occurs and my app is killed. `2024/12/02 16:11:59.494 29157 30202 Error Unity <>c__DisplayClass5_0:b__0(String) 2024/12/02 16:11:59.496 29157 30202 Error Unity We are getting something wrong with the webview. 2024/12/02 16:11:59.506 29157 30201 Debug UserMessagingPlatform Writing to storage: [IABGPP_HDR_GppString] DBABL~BVQqAAAAAg 2024/12/02 16:11:59.518 29157 30202 Error Unity Graphics device is null. 2024/12/02 16:11:59.522 29157 29157 Debug DecorView[] onWindowFocusChanged hasWindowFocus true |
[REQUIRED] Step 1: Describe your environment
[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
Every time I save the data preferences in a message for regulated states in the US, I get a warning in the console that says, "we are getting something wrong with the webview." Then, the same message is sent as a FormError in ConsentForm.ShowPrivacyOptionsForm().
This happens whether the device naturally connects from a regulated state or if I use DebugGeography.RegulatedUSState.
However, the selected option seems to persist when reopening the form, even in another session but I don't know if its being effective for Ad requests.
Relevant Code:
The text was updated successfully, but these errors were encountered: