Funding Choices Android UMP still not working

[Frank]

Hi again, 

after waiting over 1 month without any satisfying answer from your site i tried the

new funding choices several times and today again. 

Somebody told me that the bugs/errors should be fixed if i create a new form 

So i have created a new form in "German" and activated it in my test app.

Scenario : Hitting "agree" = Ads working

Scenario: Hitting "Options" and then "Submit" without doing anything = Ads failed to load with errorcode 3. This is the same problem like over one month ago

 Now i am asking :

Are you not interested in any way to solve these problems ?

We never got any satisfying answer yet if you are going to "improve and fix it" or 

if you do nothing to fix it ? 

Here is my new log and i hope you will improve and fix this really important problem

User hits "Agree" this key is [IABTCF_PurposeConsents] 1111111111

and seems to be ok to serve ads 

User hits only "Send" in option without touching any button then this key gos to 

[IABTCF_PurposeConsents] 0.  -----the result is Ads failed to load error code 3

Consent

2020-09-30 23:11:37.068 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=write&args=%7B%22IABTCF_CmpSdkID%22%3A300%2C%22IABTCF_CmpSdkVersion%22%3A1%2C%22IABTCF_PolicyVersion%22%3A2%2C%22IABTCF_gdprApplies%22%3A1%2C%22IABTCF_PublisherCC%22%3A%22DE%22%2C%22IABTCF_PurposeOneTreatment%22%3A0%2C%22IABTCF_UseNonStandardStacks%22%3A0%2C%22IABTCF_VendorConsents%22%3A%2200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001%22%2C%22IABTCF_VendorLegitimateInterests%22%3A%2200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001%22%2C%22IABTCF_PurposeConsents%22%3A%221111111111%22%2C%22IABTCF_PurposeLegitimateInterests%22%3A%220100111111%22%2C%22IABTCF_SpecialFeaturesOptIns%22%3A%221%22%2C%22IABTCF_TCString%22%3A%22CO6kYxyO6kYxyEsABBDEA5CoAP_AAE_AAAYgF5wAwAuAJ0AXmBecAIALgC8wAA%22%2C%22IABTCF_AddtlConsent%22%3A%221~1716.827%22%2C%22IABTCF_UserConsentRecordId%22%3A%22EBB9649B-F472-48E6-9544-8170578A5CC4%22%7D

2020-09-30 23:11:37.072 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[write]: {"IABTCF_CmpSdkID":300,"IABTCF_CmpSdkVersion":1,"IABTCF_PolicyVersion":2,"IABTCF_gdprApplies":1,"IABTCF_PublisherCC":"DE","IABTCF_PurposeOneTreatment":0,"IABTCF_UseNonStandardStacks":0,"IABTCF_VendorConsents":"00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001","IABTCF_VendorLegitimateInterests":"00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001","IABTCF_PurposeConsents":"1111111111","IABTCF_PurposeLegitimateInterests":"0100111111","IABTCF_SpecialFeaturesOptIns":"1","IABTCF_TCString":"CO6kYxyO6kYxyEsABBDEA5CoAP_AAE_AAAYgF5wAwAuAJ0AXmBecAIALgC8wAA","IABTCF_AddtlConsent":"1~1716.827","IABTCF_UserConsentRecordId":"EBB9649B-F472-48E6-9544-8170578A5CC4"}

2020-09-30 23:11:37.073 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=dismiss&args=%7B%22status%22%3A%22CONSENT_SIGNAL_SUFFICIENT%22%7D

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkID] 300

2020-09-30 23:11:37.076 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=complete

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkVersion] 1

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PolicyVersion] 2

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_gdprApplies] 1

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PublisherCC] DE

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeOneTreatment] 0

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UseNonStandardStacks] 0

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorConsents] 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorLegitimateInterests] 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeConsents] 1111111111

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeLegitimateInterests] 0100111111

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_SpecialFeaturesOptIns] 1

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_TCString] CO6kYxyO6kYxyEsABBDEA5CoAP_AAE_AAAYgF5wAwAuAJ0AXmBecAIALgC8wAA

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_AddtlConsent] 1~1716.827

2020-09-30 23:11:37.076 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UserConsentRecordId] EBB9649B-F472-48E6-9544-8170578A5CC4

2020-09-30 23:11:37.077 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[dismiss]: {"status":"CONSENT_SIGNAL_SUFFICIENT"}

2020-09-30 23:11:37.087 19570-19570/com.example.consentdialogtestapp E/Vidmake:  Consent form user reload dissmissed callback

2020-09-30 23:11:37.108 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[complete]: {}

2020-09-30 23:11:37.168 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=load_complete&args=%7B%22status%22%3A%22ok%22%7D

2020-09-30 23:11:37.169 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[load_complete]: {"status":"ok"}

2020-09-30 23:11:37.172 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=start_transparency_status_updates

2020-09-30 23:11:37.172 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[start_transparency_status_updates]: {}

2020-09-30 23:11:37.173 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=configure_app_assets

2020-09-30 23:11:37.173 19570-19707/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[configure_app_assets]: {}

2020-09-30 23:11:37.197 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Wall html loaded.

Hit only submit button !!!

2020-09-30 23:13:03.546 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=load_complete&args=%7B%22status%22%3A%22ok%22%7D

2020-09-30 23:13:03.546 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[load_complete]: {"status":"ok"}

2020-09-30 23:13:03.551 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=start_transparency_status_updates

2020-09-30 23:13:03.552 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=configure_app_assets

2020-09-30 23:13:03.563 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[start_transparency_status_updates]: {}

2020-09-30 23:13:03.610 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[configure_app_assets]: {}

2020-09-30 23:13:03.614 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Wall html loaded.

2020-09-30 23:13:03.814 19570-19635/com.example.consentdialogtestapp D/OpenGLRenderer: endAllActiveAnimators on 0x70273fbd90 (MenuPopupWindow$MenuDropDownListView) with handle 0x6f472f2480

2020-09-30 23:13:06.712 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=write&args=%7B%22IABTCF_CmpSdkID%22%3A300%2C%22IABTCF_CmpSdkVersion%22%3A1%2C%22IABTCF_PolicyVersion%22%3A2%2C%22IABTCF_gdprApplies%22%3A1%2C%22IABTCF_PublisherCC%22%3A%22DE%22%2C%22IABTCF_PurposeOneTreatment%22%3A0%2C%22IABTCF_UseNonStandardStacks%22%3A0%2C%22IABTCF_VendorConsents%22%3A%220%22%2C%22IABTCF_VendorLegitimateInterests%22%3A%2200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001%22%2C%22IABTCF_PurposeConsents%22%3A%220%22%2C%22IABTCF_PurposeLegitimateInterests%22%3A%220100111111%22%2C%22IABTCF_SpecialFeaturesOptIns%22%3A%220%22%2C%22IABTCF_TCString%22%3A%22CO6kY_sO6kY_sEsABCDEA5CgAAAAAE_AAAYgAAALzgBABcAXmAAA%22%2C%22IABTCF_AddtlConsent%22%3A%221~%22%2C%22IABTCF_UserConsentRecordId%22%3A%2239FA97C8-28A7-4078-BE0B-6824B7E6A75F%22%7D

2020-09-30 23:13:06.713 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[write]: {"IABTCF_CmpSdkID":300,"IABTCF_CmpSdkVersion":1,"IABTCF_PolicyVersion":2,"IABTCF_gdprApplies":1,"IABTCF_PublisherCC":"DE","IABTCF_PurposeOneTreatment":0,"IABTCF_UseNonStandardStacks":0,"IABTCF_VendorConsents":"0","IABTCF_VendorLegitimateInterests":"00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001","IABTCF_PurposeConsents":"0","IABTCF_PurposeLegitimateInterests":"0100111111","IABTCF_SpecialFeaturesOptIns":"0","IABTCF_TCString":"CO6kY_sO6kY_sEsABCDEA5CgAAAAAE_AAAYgAAALzgBABcAXmAAA","IABTCF_AddtlConsent":"1~","IABTCF_UserConsentRecordId":"39FA97C8-28A7-4078-BE0B-6824B7E6A75F"}

2020-09-30 23:13:06.716 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=dismiss&args=%7B%22status%22%3A%22CONSENT_SIGNAL_SUFFICIENT%22%7D

2020-09-30 23:13:06.718 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=complete

2020-09-30 23:13:06.719 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkID] 300

2020-09-30 23:13:06.719 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_CmpSdkVersion] 1

2020-09-30 23:13:06.719 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PolicyVersion] 2

2020-09-30 23:13:06.719 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_gdprApplies] 1

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PublisherCC] DE

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeOneTreatment] 0

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UseNonStandardStacks] 0

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorConsents] 0

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_VendorLegitimateInterests] 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeConsents] 0

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_PurposeLegitimateInterests] 0100111111

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_SpecialFeaturesOptIns] 0

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_TCString] CO6kY_sO6kY_sEsABCDEA5CgAAAAAE_AAAYgAAALzgBABcAXmAAA

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_AddtlConsent] 1~

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Writing to storage: [IABTCF_UserConsentRecordId] 39FA97C8-28A7-4078-BE0B-6824B7E6A75F

2020-09-30 23:13:06.720 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[dismiss]: {"status":"CONSENT_SIGNAL_SUFFICIENT"}

2020-09-30 23:13:06.730 19570-19570/com.example.consentdialogtestapp E/Vidmake:  Consent form user reload dissmissed callback

2020-09-30 23:13:06.748 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[complete]: {}

2020-09-30 23:13:06.803 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=load_complete&args=%7B%22status%22%3A%22ok%22%7D

2020-09-30 23:13:06.804 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[load_complete]: {"status":"ok"}

2020-09-30 23:13:06.807 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=start_transparency_status_updates

2020-09-30 23:13:06.808 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[start_transparency_status_updates]: {}

2020-09-30 23:13:06.809 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Receive consent action: consent://consent/?action=configure_app_assets

2020-09-30 23:13:06.809 19570-19859/com.example.consentdialogtestapp D/UserMessagingPlatform: Action[configure_app_assets]: {}

2020-09-30 23:13:06.831 19570-19570/com.example.consentdialogtestapp D/UserMessagingPlatform: Wall html loaded.

[Mobile Ads SDK Forum Advisor Prod]

Hi Frank,

We understand your frustration on this. Other publishers also reported that setting up a new funding choices IDFA explainer messages solves the issue. If the situation persists despite the above, then please provide us a project (or at least a test project) reproducing the behavior so that we can further investigate.

Kindly understand that we will truly be needing a sample project before we can continue with our investigation on this as this will greatly help us narrow and identify the issue. Once provided, I'll then raise this to the rest of the team (including the information that you provided thus far) to get their insight as well, and to provide a decisive resolution to this issue.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q25YEcH:ref

[fran...@gmail.com]

Hello Teejay

yes it is frustrating. I mean you must understand that this problem will affect the income from all of us if the ads are not working anymore with funding choices in our mobile apps. 

I understand completely that you have to fulfill the newest requirements with UMP but in my opinion it is also very important to have here an "open" communication with the developers/publishers. 

On millions of  websites here in europe the newest integration for web is working too and all websites are still showing ads. At least non personalized

The minimum should be that non personalized ads are shown in europe if the user goes to options and hits "submit" without doing anything. At least this must be guaranteed like 

in the previous consent sdk before ! 

Also an option to know if the user declines all. Then we could also offer an option or dialog like this: "Sorry you cannot use our app without showing any ads. Apps are developed for a long time et. etc.  Please agree again "

or an option to offer a pro version /quit the app.

I will test it with test ads today again and also with an dialog in english.

OK  how can i send my test project to you ?  . Can you please give me an  email address where i can send it 

Greets Frank

[b.a.van...@gmail.com]

Dear Teejay,

You mention that "Other publishers also reported that setting up a new funding choices IDFA explainer messages solves the issue". I have two questions about that:

1. Are you sure that it solved this particular issue (Ads not showing if user chooses 'manage options' and 'submit)? I thought it fixed an issue with the form not showing on IOS?

2. If somebody indeed confirmed that this issue is resolved, could you please give a link to that response, so that the people who are still suffering from this problem can have a look at that discussion?

Underneath is a list of recent cases where developers still observe this issue:

Oct 01: this message

Oct 01: Also for me, no ads are shown if you choose 'manage options' and 'submit'

Sep 29: https://groups.google.com/g/google-admob-ads-sdk/c/QWnSRYhmQ5g/m/xC0zzngOAwAJ

Sep 29: https://groups.google.com/g/google-admob-ads-sdk/c/UcveWmtBm4Q/m/HHhZEi7UAgAJ

Sep 27: https://groups.google.com/g/google-admob-ads-sdk/c/KUXEPzh1o_A/m/vlwCSi5vAgAJ

So this issue does not seem to be solved yet. 

@frank It would be great if you could provide them with a sample project, although I don't understand why they can't reproduce this. Like everyone else, I followed the exact instructions from their website to migrate to the UMP SDK. As AndreasB mentioned in his post, nobody is adding some arcane voodoo magic.

[Luis lp]

Still having the same problem here. No solutions yet.

It has no sense to use UMP until this is solved.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/b2a73834-df62-46ad-a3dc-a81d4744ed21n%40googlegroups.com.

[Mobile Ads SDK Forum Advisor Prod]

Hi Luis,

Thank you for responding back. I see that you also commented on another post. I will be responding to you on that one with everything so as to keep it consistent.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q25YEcH:ref

[Mobile Ads SDK Forum Advisor Prod]

Hi Bastiaan,

Thank you for responding back. I was able to find this link that talks about messages for Funding Choices. I believe this is what is being referenced as it talks about apparently creating multiple EEA consents.

[fran...@gmail.com]

Hello 

so please give me an email address where i can send you my test project if you need this to reproduce the problems with funding choices. Then i will send it to you .

Frank

[Mobile Ads SDK Forum Advisor Prod]

Hi Frank,

Thank you, if you would like. You can send the sample to:

• mobileads...@gamil.com

[fran...@gmail.com]

Hello William,

i will send you my test project now. I hope to get any feedback from you when you discuss the problems with the responsible persons in your team. 

Also i hope that you will fix the problems or improve it so we could use UMP in the future. 

Other problems too : Even if go to options and turn on "personalized app" and turn "consent" on and then hit the submit button no ads will be shown. 

With all these problems at the moment we cannot use UMP.

Greets Frank

[fran...@gmail.com]

Hello again 

its getting weird :-(  :-( 

I cannot send you my  test application as zip file.   mobileads...@gamil.com  was wrong so i thought logically its gmail at the end

The receiver address is refusing  my email with the zip attachment. 

So how can i send you my test app without getting refused ?? 

Frank 

[John Doe]

I confirm it still does not work. Today I deleted the message I had in Funding choices and created new EU Consent and IDFA messages. Deleted app from simulator to make sure it behaves like a new install. Consent form is shown and works, but More Options\Submit still results in no ads.

BTW, IDFA message is being shown now, so I see at least some progress during this month.

[Mobile Ads SDK Forum Advisor Prod]

Hi John,

Thank you for sharing your findings after doing the solution suggested previously. We're also getting the same feedback from some publishers that the issue still exists even creating a new funding choices IDFA explainer messages. However, others reported back that this solves their issue. That said, let me share this to the rest of the team for further investigation and to get their insight as well. We'll update this thread the soonest they provide their feedback.

@Frank,

Could you kindly upload your project file into your Google Drive, then share an access to mobileads...@gmail.com instead? Please let us know here once this is done.

[fran...@gmail.com]

Hi 

OK i have sent the email now.. Hopefully the problems will be solved. 

Greets

Frank

[b.a.van...@gmail.com]

@Frank: Many thanks for taking the effort, very much appreciated.

@William Pescherine: About your single response to my two questions (numbered 1 and 2). I don't see how that is an answer to any of the questions, nor do I see how this is related at all to the issue described in this thread.

As a reminder, the issue, as described by Frank in the first message, is the following:

Scenario : Hitting "agree" = Ads working

Scenario: Hitting "Options" and then "Submit" without doing anything = Ads failed to load with errorcode 3. This is the same problem like over one month ago

Is there any update on this?

[Luis lp]

I really expected a fast solution for such a big problem. UMP is completely useless with this bugs. Are you really trying to solve this issue? 

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/c412a2c6-149c-4ac0-9b3f-d32f238852b2n%40googlegroups.com.

[fran...@gmail.com]

Hello 

i am sorry more than 1 1/2 month are gone now and really nothing happened and still no answer from you yet.

 - You got many informations from other publishers about the problems with UMP.

- I told you the problems too . Also i sent my test project to you .

I have tested UMP today again and all the problems still exists. No consent status, no info if personalized or no personalized is choosen etc..etc...etc.

What is the problem that nothing happens ? Are you not interested in solving the problems ? 

Is it not possible to give an answer like "We are solving the problems" or " Sorry we are doing nothing here " ???

What should we "all" do if UMP maybe becomes mandatory and no problems are resolved in the future ?

Should we then "all" stop developing apps because we have no income anymore ?

Frank

[mydevelo...@gmail.com]

++++++++

13 Ekim 2020 Salı tarihinde saat 04:54:24 UTC+3 itibarıyla fran...@gmail.com şunları yazdı:

[mydevelo...@gmail.com]

Hi,

I have been a follower of this problem for 2 months, the problem is still not solved. When will the problem be solved? It really disappointed us that problems are resolved so slowly.

Best regards,

Mehmet.

13 Ekim 2020 Salı tarihinde saat 14:51:44 UTC+3 itibarıyla mydevelo...@gmail.com şunları yazdı:

[alexander]

Hi Frank,

I have found a work-around (or I'm using it the way google intended it, since the documentation is lacking who knows). I've also posted the answer on stackoverflow so I'll just copy and paste my answer here:

" I was facing the same issue, but a Google Engineer pointed me in the right direction. Apparently this is the default behavior if you're using the IAB TCF v2 framework. The consent type is only applicable to the simplified version of the form. The full conversation can be found here Since the Google documentation is lacking information I had to dig a little deeper to find the answer on the IAB Techlab Github.

To find the Consent status of your user all you need is SharedPreferences(Android) OR NSUserDefaults(iOS) the key value pairs and full explanation can be found here

So to solve your problem be sure to check out the In-App Details section:

1. An app publisher should embed a CMP SDK – The setup and configuration as well as the protocol for how to initialize the CMP SDK are all proprietary to each CMP SDK. (Google Funding Choices)
2. Since more than one CMP SDK may be included in publishers' linked SDKs, the publisher must initialize only one of them. The initialized CMP shall set IABTCF_CmpSdkID with its ID as soon as it is initialized in the app to signal to vendors that a CMP is present.
3. The CMP SDK will determine if GDPR applies to this user in this context. But, a publisher may choose to initialize a CMP dialogue UI manually.
4. The CMP shall set the NSUserDefaults(iOS) or SharedPreferences(Android) variables and vendors will then be able to read from them directly.
5. Vendors should listen to IABTCF_* key updates to retrieve new TC data from NSUserDefaults(iOS) or SharedPreferences(Android).

In order to show at least unpersonalized ads you need to have consent for at least:

1. Store and/or access information on a device

Legitimate interest (or consent, where a publisher configures their CMP to request it) is established for Google to:

2. Select basic ads
3. Measure ad performance
4. Apply market research to generate audience insights
5. Develop and improve products

Since the first one cant be checked by default (GDPR rule..) Google wont be able to show ads once a user presses settings-> submit.

If you need any more help please let me know!

[Anteger]

>Since the first one cant be checked by default (GDPR rule..) Google wont be able to show ads once a user presses settings-> submit. 

So it seems like the ruling literally killed ad serving and it's just a matter of time people will reproduce those steps to disable ads, many applications still don't have a consent form like this implemented and I've been seeing apps not following the opt-in ruling for a long time now.

[AndreasB]

Even then, I don't think that this rules out pre-filling the form with previous consent information if the user visits the form a second time to change their consent. Doing so should not be considered "wrongful opt-out", because the user obviously already opted in to something before and probably just wants to change that consent, not completely revoke it.

Personally, I would have much less of an issue with UMP if this was the case. If someone absolutely wants to opt out of all ads, I can probably live with losing that part of my userbase while cutting my losses and just not make costly functionality available to them. If I lose everyone who simply clicks around and doesn't even know what they are doing, I might as well stop offering my app for good.

[alexander]

> any applications still don't have a consent form like this implemented and I've been seeing apps not following the opt-in ruling for a long time now.

Same goes for me haha, however Google notified me that if no TCF2 string is set by (correct me if I'm wrong) 15 nov. they won’t be serving ads anymore. For now limiting the user when they don’t give consent seems the only viable option, however this again is in conflict with the GDPR rules. As to how this will unfold I'm curious as well, maybe it’s the end of free apps?

 

> Even then, I don't think that this rules out pre-filling the form with previous consent information if the user visits the form a second time to change their consent. Doing so should not be considered "wrongful opt-out"

I don’t see where I stated this, but this would definitely be an upgrade to the existing UMP.

[AndreasB]

Sorry, I wasn't trying to put words in your mouth. Rather, I assume that Google's reason for always displaying a blank consent form, even if the user already opted in to something before, must be that they think doing otherwise might be construed as forcing the user into an opt-out situation where they should always opt-in instead. I believe this reasoning to be wrong. GDPR is very clear about allowing users to revoke their previous consent, but that doesn't mean that a form mustn't display that previous consent in the first place.

[alexander]

Couldn’t agree more, maybe Google can get in on this?

[fran...@gmail.com]

@Alexander

Hi Alexander

they send you a message ???When did you receive this message . You wrote "  Same goes for me haha, however Google notified me that if no TCF2 string is set by (correct me if I'm wrong) 15 nov. they won’t be serving ads anymore. "

Then this would be the end for anybody and Admob should also close his doors and we should look for another job. Then Admob is dead in maybe 6 month or less ?! 

The submit button problem still exists without any answer .

The only solution would be : Programming an extra dialog with 2/3 options and catch the pref key if key IABTCF_PurposeConsents is = 0 

like this : 

Sorry we cannot offer you our app without showing ads 

--Agree again 

--Buy Premium version ...minimum price like 1000$ ......just to be sarcastic :-) or abo for 500$ per month

- Quit app

I do not think that this is against gdpr-rules. because it is my "decision" if i do not want to offer my app without any ads.

I really do not understand why nobody from google admob team is supporting/helping us with theses issuses. I always thought that google makes an option communication with

publishers.

[b.a.van...@gmail.com]

I also received an email from AdMob:

"reaching out in order to ensure you are aware of common IAB TCF v2.0 implementation errors that may be impacting your integration. It is critical that you work to remediate these errors because they will impact your Google monetization if they go unresolved. FYI, we are also reaching out to CMPs to ensure that they are also working to address IAB TCF v2.0 implementation errors."

...

"To give publishers time to manage errors and misconfigurations related to the launch of IAB Europe’s Transparency & Consent Framework v2.0, Google is extending a 90 day grace period that is scheduled to end on November 15th, 2020. During this grace period, where errors are present, monetization will continue, though the grace period treatment, and its effect on monetization, varies from error type to error type."

So what this mean if you are still using the 'legacy' consent-library? Would that still be oke?

[alexander]

> The only solution would be : Programming an extra dialog with 2/3 options and catch the pref key if key IABTCF_PurposeConsents is = 0 

This is the way (SO to Mandalorian). However, is this legal? this is written in the GDPR legislation:

"Freely given” consent essentially means you have not cornered the data subject into agreeing to you using their data. For one thing, that means you cannot require consent to data processing as a condition of using the service. They need to be able to say no. According to Recital 42, “Consent should not be regarded as freely given if the data subject has no genuine or free choice or is unable to refuse or withdraw consent without detriment.” (https://gdpr.eu/gdpr-consent-requirements/)

 

So it's kind of a grey area, which in due time probably will be specified better, but as of now the GDPR is a shitshow..

 

> So what this mean if you are still using the 'legacy' consent-library? Would that still be oke?

I think the legacy library is build on TCF1, but you need to check the docs to be sure, if thats the case then unfortunately the answer is no..

 

All this is based on my own research so please correct me if I'm wrong (which I hope I’m)

[AndreasB]

> This is the way (SO to Mandalorian). However, is this legal?

I am not a lawyer, but I think it can be if done right. I'm currently thinking about implementing it like this in my app:

1. Offer "basic" functionality for free, but make it obvious to users that they can purchase "advanced" functionality, perhaps by combining this with a sign-in flow that the app has, anyway.
2. On the screen where in-app purchases are possible, inform users that they can also opt in to ads if they just want to check out advanced functionality without having to pay up front.
3. If the user chooses to opt in to ads, show the UMP dialog.
4. Check SharedPreferences/NSUserDefaults myself, and (a) offer full functionality while consent is fully given, or (b) pretend as if nothing happened if not (meaning "basic" functionality and the offer to purchase advanced functionality).

Through this multi-tiered approach, GDPR consent is not tied to app functionality directly. It's hilariously convoluted and might lead to more people choosing payments over ads at least in the long run - but if that's the case, I won't even complain. ;)

[alexander]

> I am not a lawyer, but I think it can be if done right.

Great minds think alike Andreas my friend,  thats the beauty of a grey area.

[Hassan Usman]

What

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/82a27808-344e-496f-98a5-bf40e002aee8n%40googlegroups.com.

[fran...@gmail.com]

Hi Guys

i just see a new option in my funding choice test app ?! 

in admob go to your created funding choices app 

and click on "Details on the notification of EU user consent"

and then click on "Select purposes for your own use" 

 ...there you can set up to 10  own purposes ..i guess the switches in the form ...i quess this is new ??!

i tried this out. deleted my consent dialog and created a new one. but again "nothing" worked for me after setting the switches.  (it sucks)

Is this working for anybody ?? 

[AndreasB]

I'm seeing the same, thanks for pointing this out.

It is a good start - however, the fact that the form still always shows these preset default settings and not what the user has set for themself before makes it worse (and potentially illegal to use!) for the time being. Consider the following:

1. I set one of the "own use" purposes to "legitimate interest".
2. When the form is displayed in my app, I click through to a detailed view, and in fact now see this switch in an active default state.
3. However, if I manually toggle this switch to OFF before saving, then open the form again to change my consent, the switch is back to ON.

So, while allowing us to add our own purposes to the consent form is a welcome change, the current implementation that does not read and display what a user previously set still means that a user might accidentally opt-out of ads even if they don't intend to - and, worse, might now lead to situations where users are faced with switches set to ON for purposes they expressly do not want to allow.

[Georg von der Howen]

OK, it seems I am running into the same problem after receiving an email about an IAB TCF Implementation Error for the second time. My app is on iOS using Google-Mobile-Ads-SDK (7.66.0), GoogleUserMessagingPlatform (1.2.0).

Same symptoms: 

- User in the EU gets Funding Choices dialog and clicks "Consent" and ads are shown.

- User in the EU clicks "Manage Options" / "Submit" and no ads are shown.

- User in the EU clicks "Manage Options" / "Consent to store and/or access information on a device" / "Submit" and still no ads are shown.

As far as I understand @alexander 's post above, case 1 and two are expected, but case 3 should serve ads.

[AndreasB]

Welcome to the club, Georg.

In your third step, what happens if the user also opts in to the second purpose "Select basic ads"? I would assume that both this and "store information on device" is necessary for at least non-personalized ads to be served.

[alexander]

Hi Georg,

I"ve written a stackoverflow post about this as well.

I'll copy the answer down below so everyone in this thread can read it, if you need more help just let me know!

"As per the Google documentation:

Google will serve personalized ads when all of the following criteria are met:

1. The end user grants Google consent to Store and/or access information on a device
2. Create a personalized ads profile
3. Select personalized ads

And legitimate interest (or consent, where a publisher configures their CMP to request it) is established for Google to:

1. Select basic ads
2. Measure ad performance
3. Apply market research to generate audience insights
4. Develop and improve products

If the consent requirements for personalized ads are not met, Google will serve non-personalized ads when all of the following criteria are met:

1. Store and/or access information on a device

Legitimate interest (or consent, where a publisher configures their CMP to request it) is established for Google to:

1. Select basic ads
2. Measure ad performance
3. Apply market research to generate audience insights
4. Develop and improve products

If none of the conditions above are met Google won't be showing ads.."

On Thursday, October 15, 2020 at 10:35:34 AM UTC+2 Georg von der Howen wrote:

[b.a.van...@gmail.com]

@Georg: for case 3, you also need to go to the vendors list, scroll until you find Google, and enable that. For me the ads were served in that case.

[Georg von der Howen]

@AndreasB: Still no ads, even if "Select basic ads" is checked (as well as legitimate interest)

@Alexander: Thanks for resending. I did read your post but it is not working for me as described: Even if "Store and/or access information on a device" is granted and the other four options have "legitimate interest" checked, NO ads are served, not even unpersonalized ones.

[Georg von der Howen]

@b.a.van Yes, if I scroll down the list and enable Google, it works, even though "legitimate interest" is already enabled there. But no user in his right mind is going to do that ;)

I still have the feeling that I have not fully grasped this topic (being a developer and not a lawyer) but at the same time I think that somehow the "legitimate interest" options are being ignored by the SDK at the moment?

Is there a way to check for me in the app if all the criteria are met to serve ads (either personalized or unpersonalized)? Then I could "force" the user to either consent (with a nice explanation why this is necessary) or to subscribe (which removes all ads).

[b.a.van...@gmail.com]

I fully agree with you on that Georg, users will never ever do that (why would they take the effort?). I have mentioned that in one of the many threads on this topic, but Google remains unresponsive. I am in the exact same position as you are Georg, a developer who has difficulty understanding all of this legal stuff.

[alexander]

@b.a van, nice one! I'll edit my post as well, this group is better than the actual documentation

@Georg I've written a piece of java code to do just that, so you need to translate it to swift. If you send me a private E-mail I don't mind sharing it with you!

[Georg von der Howen]

@b.a.van The more I look at this the more I think that Google is currently ignoring the legitimate interest settings. If they would respect them, users would not have to scroll down the vendors list to explicitly enable Google. What also is not acceptable is that the dialog is ignoring previous settings made by the user. 

@Alexander E-Mail sent.

[fran...@gmail.com]

Hello 

it would be nice to hear any answer from the admob team here about the new option to preset the switches ? It is a new problem that this does not work too 

I am on Android and i see the other guys are on IOS  but both have the same problems. 

Regardless which switch i want to preset it does not work in the form. Setting any switch to legitimate interests or agree does not show up in the form. 

Can you please tell us anything about these new problems and when they will be solved ? It is really not nice to get never any satisfying answer. 

I really do not understand this "no answer" policy 

Frank

[fran...@gmail.com]

Hello

regarding to my last message  

i just see a new option in my funding choice test app ?! 

in admob go to your created funding choices app 

and click on "Details on the notification of EU user consent"

and then click on "Select purposes for your own use" ...there you can set up to 10  own purposes ..i guess the switches in the form ...i quess this is new ??!

i tried this out. deleted my consent dialog and created a new one. but again "nothing" worked for me after setting the switches. 

Is this working for anybody ?? 

Update:  Regarding these new 10 options !!!

You are telling in the info: You are responsible for these settings : But none of these settings are working 

For example: I put all options to "Agree" and save this .

No i am making a new form for example in english

In the form i have now two sections ?? :  TCF Provider with options  and Website/App  with almost the same options

If i turn in "Details on the notification" all 10 options to agree like i mentioned above then alle these settings are used for the options Website/App.

There is everything turned on. 

But if i go again to options and hit only submit then i have the same scenario again : No Ads Error 3

Again no non-personalized ads at least ..

It is getting  now more and more confusing with double options now  and also these 2 sections. 

You are adding a lot of new stuff (which looks not bad)  but really nothing is working :-(

Also another bug in my opinion is that all legitimate interests are totally ignored/not respected. Also not Google as a TFC member/vendor 

Frank

[Robot Android]

New settings for those who place their personal ads in app! 

[fran...@gmail.com]

Hi 

i think my last message did not save 

If i go to a website and click on options and then submit without doing anything it works and ads are shown. So minimum ads/non-personalized ads are working 

on websites. 

So i do not understand what is the problem here  to fix the problems with the mobile funding choices. 

Funding choices as it is at the moment is a total disaster for every publisher because 

nothing is really working correctly.

 Also i do not understand why you guys from google  do not answer any question or give us a feedback if you are improving/solving something. 

I do not know what i should say/think about this...

Frank

[Bastiaan]

Today I stumbled upon this website (the mobile site, not really recommended, but that's not the point) and was presented with a Funding Choices consent form. So I thought, let's see what happens there. Turns out that I can also simply switch off advertisements there by selecting 'Manage options' and 'Submit'. So also on web sites, showing ads to EU citizens will soon be history..

@George, about your comment:

The more I look at this the more I think that Google is currently ignoring the legitimate interest settings. If they would respect them, users would not have to scroll down the vendors list to explicitly enable Google. What also is not acceptable is that the dialog is ignoring previous settings made by the user.

I don't know the difference between consent and legitimate interest, so I don't know if that is the case. And yes, it is unacceptable that previous settings are not loaded in the form. Frank and many others have mentioned this a million times, with the usual response, none.

[fran...@gmail.com]

@Hi Bastiaan

very good example this website..in one browser i hit options and submit = no ads anymore --adios 

in  another brother i hit agree = Ads serving. 

This is the funding choice disaster  ! On similar scripts it is "working" 

and nobody is reacting . This  policy looks like: We let the publisher die 

Frank

[AndreasB]

I think this latest example, while related, is slightly different from what we've discussed before.

If, whether on any web page or in an app, you go to manage options directly, all the switches probably need to default to OFF for legal reasons. There might be some loopholes, but I'm not a lawyer. For example, if you have a "legitimate interest" to collect some data, you perhaps don't need to offer your users a switch in the first place - but if it is there, it needs to be OFF when the user first chooses their options.

In our previous examples, what is different is that the user did already choose their options before, by tapping "Consent to all" or similar -  and if they bring up the dialog again for whatever reason, this previous consent is not being displayed and will easily be overridden.

For what it's worth, I tried to do some experiments on the web myself, but so far I haven't found a single website that allows me to bring up the UMP dialog again, to change my consent. As far as I can tell, this means all of these pages do not currently implement GDPR properly.

[fran...@gmail.com]

Hi AndreasB the problem here is almost the same.  For example i put all 10 options in the Web/App to Agree 

and then load the form ..go to options again and hit submit ...here are also no values saved like in the "mobile" only options. 

These are big BUGS in my eyes. Another example: 

I go to options (mobile android form)  and put really "every" switch to on, go to vendors and "put" every button to on 

(So normally ads should be served then ???  In my logic = Yes

but then hitting "Submit" ...again no ads are served . Not even 1 value is saved. I have tested it many times. 

Only the main "Agree" button brings yo to wonderland e.g. the desired freedom ..

So what is going wrong here if not even "one" value is saved even if the user would turn every switch to on ?

So theses bugs are getting resolved or not resolved ..thats the question

[luis...@gmail.com]

How is it that we are not getting even an update of such a problem? Are you guys working on this issue or should we stop trying to use UMP? Should we use the legacy consent API?

[Mobile Ads SDK Forum Advisor Prod]

Hi Luis,

Thank you for posting here. We want everyone to know that we are talking about this always within our team. At the moment we just have nothing that we can share with you all.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q26A1se:ref

[fran...@gmail.com]

Hi William 

but if you "at least" talk about this in your team maybe you could talk about this here to : 

I made some additional brainstorming for some proposals. 

1. Add at least maybe a return value on dialog dismissed in funding choices (com.google.android.ump:user-messaging-platform ) after closing/submitting the form 

    or an extra void/callback returning a boolean value (depending on the saved values in the preference keys) like  adserving = true or adserving = false for example. ..i quess this would be legal !

There is only IABTCF_PurposeConsents and maybe IABTCF_VendorConsents to check and make a function with this.

This would help a lot !

 So if adserving is = false then we could get this value and make easily  an extra dialog for the user:

 for example offering again to use the app with ads and enjoy all features for free ,maybe offering a pro version or offering only a demo/test Version of  the app as long as the apps are disabled.

Greets Frank

[Mobile Ads SDK Forum Advisor Prod]

Hi Frank,

I work along with William and thank you for adding insights regarding your query. Let me relay this information with the team and we will give you an update as soon as possible.

Regards,

Sherwin Diesta Mobile Ads SDK Team

ref:_00D1U1174p._5004Q26A1se:ref

[hiddeneyes02]

as soon as possible ??? More than six months and still nothing