-
Notifications
You must be signed in to change notification settings - Fork 31
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
MaxSdkCallbacks not trigger on newest version #358
Labels
duplicate
This issue or pull request already exists
Comments
We are aware of the issue and are working on a fix right now. The issue only happens in Unity editor and the Android and iOS builds should get the callbacks as expected. |
Closing this as duplicate of: #353 (comment) |
santoshbagadi
added
duplicate
This issue or pull request already exists
and removed
bug
Something isn't working
labels
Apr 10, 2024
I want to ask something. Can i just use older version with newest adapter
update?
And wait for sdk better to upgrade?
…On Wed, Apr 10, 2024, 21:25 Santosh Bagadi ***@***.***> wrote:
Closing this as duplicate of: #353 (comment)
<#353 (comment)>
—
Reply to this email directly, view it on GitHub
<#358 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADX7J7PNEBUN7XDELJ2GMKLY4VDT5AVCNFSM6AAAAABGAPT3IKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBXGY4TSOBZG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yes, our adapters are backwards compatible and you should be able to update the adapters without updating our SDK. Apologies for the inconvenience and we'll have a release with the fix soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
MAX Plugin Version
6.4.2
Unity Version
2020.3.42f1
Device/Platform Info
All
Current Behavior
MaxSdkCallbacks is not trigger on Unity MAX SDK v6.4.2.
All events of inter, reward... is not trigger after i upgrade to v6.4.2
Expected Behavior
No response
How to Reproduce
Additional Info
No response
The text was updated successfully, but these errors were encountered: