-
Notifications
You must be signed in to change notification settings - Fork 72
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
Comments
@maximkir-fl could you confirm if you are initializing the SDK with the new |
Yes.
…On Fri, 15 Mar 2024 at 0:53 Santosh Bagadi ***@***.***> wrote:
@maximkir-fl <https://github.com/maximkir-fl> could you confirm if you
are initializing the SDK with the new ALSdkInitializationConfiguration
API?
—
Reply to this email directly, view it on GitHub
<#303 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV4TRGHAJZUI4BWSNSGONILYYITAHAVCNFSM6AAAAABEV53626VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJYGYYTANZRG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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 |
Thanks!
Can you please point out to the docs regarding the old api usage?
…On Fri, 15 Mar 2024 at 8:56 Santosh Bagadi ***@***.***> wrote:
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
—
Reply to this email directly, view it on GitHub
<#303 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV4TRGABPBTAZ7WF64VB7ETYYKLRZAVCNFSM6AAAAABEV53626VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZGA2DONJWHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Our docs are available here: https://dash.applovin.com/documentation/mediation/ios/getting-started/integration#add-the-sdk-key |
@maximkir-fl - We just released v12.3.1 SDK which fixes this issue. Please let us know if there are any questions. |
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
` versions: s.dependency 'AppLovinSDK', '12.3.1' |
@llfabris If you are using the new initialization API, you must remove the |
@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 |
@llfabris Could you share your code for creating the |
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.
Expected Behavior
No response
How to Reproduce
Follow the iOS integration guide.
Additional Info
No response
The text was updated successfully, but these errors were encountered: