Skip to content
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

AppLovin SDK Not Triggering Callback Handler After Initialization in GDPR Region #303

Open
maximkir-fl opened this issue Mar 14, 2024 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@maximkir-fl
Copy link

maximkir-fl commented Mar 14, 2024

MAX SDK Version

12.3.0

Device/Platform Info

iOS 17.4

Current Behavior

After initializing the AppLovin SDK (version 12.3.0) on iOS within the GDPR region, the completion handler callback is not being triggered.

Based on the log snippets provided, it appears that the SDK is re-initializing itself. This might be causing the provided callback handler not to be triggered.

Once the app restarted, the callback executed.

[AppLovinSdk] DEBUG [ALGoogleCMPAdapter] Successfully loaded consent form
[AppLovinSdk] DEBUG [ALSdk] Transitioning to state: [ALConsentFlowState: id=21, type=cmp_show, isInitialState=0]
[AppLovinSdk] DEBUG [ALGoogleCMPAdapter] Showing consent form...

[AppLovinSdk] DEBUG [ALGoogleCMPAdapter] Consent form finished showing
[AppLovinSdk] DEBUG [ALSdk] Transitioning to state: [ALConsentFlowStateEvent: id=13, type=event, isInitialState=0, name=gdpr_ok]
[AppLovinSdk] DEBUG [ALEventService] Tracking event: "gdpr_ok"
[AppLovinSdk] DEBUG [ALSdk] Transitioning to state: [ALConsentFlowState: id=1001, type=decision, isInitialState=0]
[AppLovinSdk] DEBUG [ALSdk] Transitioning to state: [ALConsentFlowState: id=14, type=att, isInitialState=0]

[AppLovinSdk] DEBUG [ALSdk] Transitioning to state: [ALConsentFlowState: id=14, type=att, isInitialState=0]
[AppLovinSdk] DEBUG [ALSdk] Transitioning to state: [ALConsentFlowState: id=99, type=reinit, isInitialState=0]
[AppLovinSdk] DEBUG [ALEventService] Tracking event: "tac"
[AppLovinSdk] DEBUG [ALSdk] Unified flow completed with status: [ALConsentFlowCompletionStatus: isCMPPromptShown=1, isATTPromptShown=1, error=(null)]
[AppLovinSdk] DEBUG [ALSdk] Re-initializing SDK with the updated privacy settings...

Expected Behavior

No response

How to Reproduce

Follow the iOS integration guide.

Additional Info

No response

@maximkir-fl maximkir-fl added the bug Something isn't working label Mar 14, 2024
@santoshbagadi
Copy link
Contributor

@maximkir-fl could you confirm if you are initializing the SDK with the new ALSdkInitializationConfiguration API?

@maximkir-fl
Copy link
Author

maximkir-fl commented Mar 15, 2024 via email

@santoshbagadi
Copy link
Contributor

Thank you for confirming and raising the issue. We'll add a fix for this in our next SDK release.

Note that the issue is not present when using our old APIs, so please hold off on updating to the new APIs until our next release. Apologies for the inconvenience

@maximkir-fl
Copy link
Author

maximkir-fl commented Mar 15, 2024 via email

@santoshbagadi
Copy link
Contributor

Our docs are available here: https://dash.applovin.com/documentation/mediation/ios/getting-started/integration#add-the-sdk-key

@thomasmso
Copy link
Member

@maximkir-fl - We just released v12.3.1 SDK which fixes this issue. Please let us know if there are any questions.

@llfabris
Copy link

llfabris commented Mar 19, 2024

I'm having a similar issue outside gpdr, where the initialization callback is never called. Updating to the latest version didn't help.

https://dash.applovin.com/documentation/mediation/ios/getting-started/integration#add-the-sdk-key

All my networks show on the "Completed SDK INTEGRATIONS" and I have the SDK key inside the app's plist as "AppLovinSdkKey".

@thomasmso Any ideas? I'm using debug build. Any info that could help us debug this issue would be greatly appreciated.

` obj-c
[ALSdk shared].mediationProvider = @"max";

[[ALSdk shared] initializeSdkWithCompletionHandler:^(ALSdkConfiguration *configuration) {
    // Start loading ads
}];

`

versions:

s.dependency 'AppLovinSDK', '12.3.1'
s.dependency 'AppLovinMediationAdColonyAdapter', '4.9.0.0.4'
s.dependency 'AppLovinMediationChartboostAdapter', '9.7.0.0'
s.dependency 'AppLovinMediationFacebookAdapter', '6.14.0.1' # Meta Audience Network
s.dependency 'AppLovinMediationFyberAdapter', '8.2.7.0' # DT Exchange
s.dependency 'AppLovinMediationGoogleAdManagerAdapter', '11.2.0.0'
s.dependency 'AppLovinMediationGoogleAdapter', '11.2.0.0' # Google AdMob
s.dependency 'AppLovinMediationHyprMXAdapter', '6.3.0.1.0'
s.dependency 'AppLovinMediationIronSourceAdapter', '7.9.0.0.0'
s.dependency 'AppLovinMediationMintegralAdapter', '7.5.9.0.0'
s.dependency 'AppLovinMediationByteDanceAdapter', '5.8.0.8.0' # Pangle
s.dependency 'AppLovinMediationTapjoyAdapter', '13.2.1.0'
s.dependency 'AppLovinMediationUnityAdsAdapter', '4.9.3.0'
s.dependency 'AppLovinMediationVungleAdapter', '7.2.2.0' # Liftoff Monetize
s.dependency 'AppLovinMediationAmazonAdMarketplaceAdapter', '4.8.0.0' # Amazon
s.dependency 'AmazonPublisherServicesSDK', '4.8.0' # Amazon

@wootaejeon
Copy link
Contributor

wootaejeon commented Mar 19, 2024

@llfabris If you are using the new initialization API, you must remove the AppLovinSDKKey entry from your Info.plist. Here is the relevant link to our docs for your reference https://dash.applovin.com/documentation/mediation/ios/getting-started/migration123

@llfabris
Copy link

llfabris commented Mar 19, 2024

@wootaejeon still didn't work, but thanks!

I see the following line in the logs:

[AppLovinSdk] DEBUG [ALErrorReporter] integration_error reported with code 200

any idea of what it means?

I don't see it in this list: https://support.applovin.com/hc/en-us/articles/13893928943629-Error-Handling

@wootaejeon
Copy link
Contributor

@llfabris Could you share your code for creating the ALSdkInitializationConfiguration object and calling initializeWithConfiguration: method with your completion handler? Feel free to share your code snippet through my email wootae.jeon@applovin.com if you'd like.

@wootaejeon wootaejeon reopened this Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants