Android Binaries RC 2024-06-26 - Ad Network Upgrades. Play:core issue. epochTime. Chartboost
To get these benefits use "Build RC". It doesn't matter which version of GameSalad Creator you publish with as long as it's a version 1.25.x. Previous RC has been promoted to Release version.
For people used to the old RC thread, I will be repeating features that are not present in the regular "Generate" build, so you know in total what you are getting with this RC. New fixes since the last RC will be in bold.
Android (Compile SDK 34, TargetSDK 34, MinSDK24)
Bug Fixes:
- Upgraded from com.google.android.play:core:1.10.3 to new broken out libraries (com.google.android.play:review:2.0.1 and com.google.android.play:asset-delivery:2.2.2)
- Fixed Chartboost and enabled support chartboost banner ads (needs publishing page update to support).
Changes
- Google UMP 2.2.0 Integrated
- Ad Network Updates
- Admob 23.0.0
- Chartboost 9.7.0
- IronSource 8.1.0
- Adcolony 4.8.0
- Amazon 9.9.3
- AppLovin 12.5.0
- Bidmachine 2.7.0
- Facebook 6.17.0
- Fyber 8.2.7
- HyprMX 6.2.3
- InMobi 10.6.6
- Liftoff 1.9.1
- Maio 1.1.16
- Moloco: 2.3.0
- MyTarget 5.20.0
- Pangle 5.8.0.8
- Smaato 22.6.0
- SuperAwesome 9.3.2
- Unity 4.12.0
- Vungle 7.3.2
- Yandex 7.0.1
Ad networks in italics are new, but we'll need to update publishing to allow you to use them.
2024-07-19 patch update:
Pushed update to fix epochTime implementation
We've also put in code for epochTime, but have not tested it yet (as seen in the HTML5 engine here). If you were waiting on any other fixes for android, feel free to ask about them here, I might have lost track of them. (But label them something like Feature Request: Thing I Want) so I can quickly differentiate them from comments and bug reports for this release.
Something about the build configuration and tool combination forces me to make the minimum supported version 24 instead of 21. We're working on fixing that.
Cheers!
Comments
Nice one 👍 Thanks for the update.
I compiled and uploaded to play console and got the error: Your app currently targets API level 33 and must target at least API level 34 to ensure it is built on the latest APIs optimized for security and performance. I used Build RC.
Could you DM me your publishing link. The system is indeed set up to compile to API 34, so not sure what's going on here.
So we compile against 34 but target 33, @C. Victory
I've adjusted the target to 34 and all looks well!
I confirm the error is gone. Thanks a lot.
I used build RC today and got the same issue. Says I'm targeting api 33.
I am also receiving the same issue with a build created today using the RC - says I'm targeting API 33, not API 34.
Can confirm it's also targetting 33 for me. Build RC.
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
Okay, not sure what happened there but the RC is back to 34.
@adent42 - Has the target reverted back to API 33 again? - I've just built with RC and Google is warning me it's targeting 33.
Yesterdays builds seemed to be targeting 34 fine.
The RC has not, but the general release (non-RC) targets 33. Since there are no big bugs, I think we should just promote the RC this week to avoid confusion.
@adent42 thanks, looks like i must have pressed the wrong button when generating the build! Oops.