Upgrade to API Level 35 for Android possible?

Hi,

is it possible to upgrade apps for Android, as required, for API Level 35? If not, they can't be longer updated and will not run on new devices.


Regards, Marco

Comments

  • NoobDevNoobDev Member, PRO Posts: 50

    Targeted API level needs to be 35 by August 30 according to Google. And billing library needs to be updated to 7.0.0 by that date as well.

  • freneticzfreneticz SwedenMember, PRO Posts: 779
  • MarcoColMarcoCol Member Posts: 285

    Yes.

    But is that possible with the latest GameSalad build?

    I've read in the internet, that this isn't possible now and also wasn't not possible last year already with the update to API-Level 33/34

  • NoobDevNoobDev Member, PRO Posts: 50

    No we have to wait for the gamesalad team to update targeting level. They’ll have it updated soon I’m sure. We have a while before the deadline.

  • MarcoColMarcoCol Member Posts: 285

    Well, they didn't updated it last year and I fear they will not do it now.

    Then GameSalad is dead I think, because without the new API-Updates, it doesn't make sense for apps in the store(s). Lets wait and see, hopefully I am wrong.

    @the GameSalad-Team: An official-feedback/answer regarding that would be nice.

  • ArmellineArmelline Member, PRO Posts: 5,415

    It was updated for 33/34. They just tend to leave things to the last minute.

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Yeah we have an update in the wings, but haven't had a chance to test it with other work. I'll push to get it done by tomorrow.

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Never mind. It's on 34! I'll work on getting a 35 build out shortly.

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Bad news haven't had time to test it yet (need to make some time after dinner tonight). Good news, thing compiled with SDK 35 and API target 35 with no issues, so (fingers crosse) things will "just work".

  • NoobDevNoobDev Member, PRO Posts: 50

    Thank you. Also billing library has to be updated to 7.0.0 by the same deadline as I mentioned above. I pm’d you about this but is there any timeline on getting these loading wheels removed? You had thrown out an idea of making them completely transparent but if that’s too time consuming can we just take them out? You said they were part of compliance but I don’t see loading wheels in a lot of games so maybe check to see if that’s no longer necessary. Even delaying them would help so that they only show up after 5 seconds. Right now they appear for every little button click. It is an eyesore, especially on my iOS version.

  • guillefaceguilleface Member, BASIC Posts: 1,034

    @NoobDev so your saying without update to api level 35 and the other 7.0.0 , we cant publish any new game to android or ios?

  • ArmellineArmelline Member, PRO Posts: 5,415

    iOS should be fine, it's just Android affected. Play Store got super fussy in the last few years and they have constant new demands.

  • guillefaceguilleface Member, BASIC Posts: 1,034

    Oh thats actually bad for me in general, i end up buying a windows pc to publish first on android hopefully to make so $$ and then buy a mac to publish to ios, i really want to use gs for my games

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Base build looks good, made another round of IronSource updates and I'm testing them now. We should be good to go soonish (though we do need to adjust publishing because IronSrc now needs Ad Unit IDs built into the app).

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Build with ad networks and updated billing looks good. I'm going to do some more test and hopefully get the new RC tomorrow (I need to make some publishing changes first to support the new IronSrc / LevelPlay APIs).

  • guillefaceguilleface Member, BASIC Posts: 1,034

    , so you think publish to android should be available like 1-2 months?

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    No, as in available by the end of the week!

  • freneticzfreneticz SwedenMember, PRO Posts: 779

    How is it going ? @adent42 need that api and library updates.....many apps to update

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Sorry, been stuck on another problem. I'll try to get something up tonight.

  • MarcoColMarcoCol Member Posts: 285

    Hi, any news on that?

  • ArmellineArmelline Member, PRO Posts: 5,415
  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Ad network limitations now fixed, but you gotta update your IronSource configuration if you use it.

  • MarcoColMarcoCol Member Posts: 285

    Thank.

    So that means that build using API35 are now possible, like required by Google Android?

  • AHBGamesAHBGames Member, PRO Posts: 129

    Hi @adent42 I updated one of my apps, and by doing so, the API 35 message was removed. However, the message saying "The app must use version 7.0.0 or later of the Google Play Billing Library" still shows with the date August 30.

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Thanks for that, I just put in a fix.

  • MarcoColMarcoCol Member Posts: 285

    Does everything works now?

    Even with API35?

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    Yes, it should on RC. (the 7.0.0 fix was applied to both releases, but only the RC has been tested with API 35

  • NoobDevNoobDev Member, PRO Posts: 50

    Yes it works, my app updated with no issues but was given a recommendation from Google that says the following.

    Recompile your app with 16 KB native library alignment

    Your app uses native libraries that are not aligned to support devices with 16 KB memory page sizes. These devices may not be able to install or start your app, or your app may start and then crash.

    There are new app bundles in this release that do not support 16 KB.

    Version codes:

    • 112

    Android 15 supports devices with 16 KB memory page sizes, which can improve your app's performance. We recommend recompiling your app when you migrate to Android 15 and testing your app in a 16 KB environment to avoid issues for users.

    @adent42

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,253

    @NoobDev thanks for letting us know, we'll look into it!

Sign In or Register to comment.