CMP Name - No value set, when using Sourcepoint

[mrbodich]

Almost always, I can't understand how to reproduce (same code, same simulator, try both fresh build and reinstall), AppLovin initializes without detecting CMP, showing CMP Name - No value set. Sometimes AppLovin can detect it and shows CMP Name - Sourcepoint Dialogue CMP.

Yesterday it detected Sourcepoint every time, today never detects it. Can you help us to fix it please?

• Initializing AppLovin after Sourcepoint
• Tried both simulator and real device
• Tried to set delay after the app launch before starting all initializations (just in case)

UPD: Now AppLovin detects Sourcepoint again, just randomly doing actions I have found that if I tap Accept ALL in Sourcepoint, then AppLovin can't detect Sourcepoint. I can accept multiple times and no result. But if I tap Save Selection button, then AppLovin will detect Sourcepoint after that. No matter which settings was selected in Sourcepoint, I can just show the already selected dialog and tap Save Selection, and AppLovin will detect Sourcepoint well after that, though no settings was changed.

[wootaejeon]

Hi @mrbodich, thanks for reporting the issue. Would you able to share the related logs (any logs from Sourcepoint and our verbose logs with tag ALTCFManager) when you tap Accept ALL?

[mrbodich]

Hi @wootaejeon Thanks for your reply.

From Sourcepoint no logs (can't found in their docs any logs configuration), when I manually log GDPR results on ready, it's identical regardless of the button pressed.

From AppLovin I can't see ALTCFManager tag. Attaching 2 zipped txt files with logs so you can compare.

• Files named accordingly with the button pressed
• Every test was made on fresh install first launch

applovin-logs.zip

[mrbodich]

Hey @wootaejeon I have prepared the Demo App which contains Sourcepoint (see the link at the bottom). All you have to do is get this parameters by creating Sourcepoint account

• CONSENT_ACCOUNT_ID
• CONSENT_PROPERTY_ID
• CONSENT_PROPERTY_NAME
• CONSENT_GDPR_PRIVACY_MANAGER_ID

Then in the project

• fill parameters for Creds object initialization in ALAppDelegate.swift file
• In project settings, AppLovin MAX Demo App - Swift target, Signing & Capabilities tab
  • set bundle identifier to your existing app from App Store (If you want to run on the real device)
  • Set your development team associated with the bundle (If you want to run on the real device)

Real adUnitId is not required to just test initialization, but we have issues displaying ads in EU, possible because of Sourcepoint trouble, we have to fix the current problem at the moment.

AppLovin+Sourcepoint Demo App.zip

[wootaejeon]

@mrbodich Before I try it out, can you try reading the TC data from UserDefaults which should have been written by Sourcepoint by the time you finish their prompt? Here is the link to the IAB documentation with the keys.

Main ones to check are IABTCF_CmpSdkID, IABTCF_gdprApplies, IABTCF_TCString and IABTCF_VendorConsents.

[mrbodich]

Hi @wootaejeon Thank you for sharing this info, we have investigated with the Sourcepoint team and in some specific cases their SDK failed to write these settings to UserDefaults. So, I believe you can close this issue and it is a Sourcepoint bug.