Back

Migration to 16kb Pages | Google Play Requirements

S
Szanik
Published Oct 2, 2025
Read3 min

This migration took around 2-3 hours of work. Which i did on the side, most of the time spent on building the app or waiting for the cli.

This were the problems I encountered:

  • gradle problems
  • kotlin problems
  • dependency problems
  • emulator not working any more
  • vs code deinstalled, whuuaaat???

My Migration Journey


flutter upgrade

First i needed to upgrade my flutter. So using the flutter cli I called this and the cli did the rest:

text
flutter upgrade

Followed by some clean up and retrieven the package dependencies:

text
flutter clean
flutter pub get

gradle-wrapper

Then I just basically followed the console. I tried to start my app but it would launch. In the console I so many stuff like "this will be deprecated in the future". So I just fixed it. grade-wrapper.properties was the first one.

I changed the value from 8.3 to 8.7

text
distributionUrl=https\://services.gradle.org/distributions/gradle-8.7-all.zip

build.grade

i needed to upgrade the ndk version. I once needed to set a specific version (don't remember why). But thats not needed anymore. Just make sure there is the following written:

text
` ndkVersion = flutter.ndkVersion`

settings.gradle

(also from console logs, thanks flutter team)

i needed to upgrade the"com.android.application" and the "org.jetbrains.kotlin.android"

text
id "com.android.application" version "8.6.0" apply false
id "org.jetbrains.kotlin.android" version "2.1.0" apply false

Dependencies

That's was it basically.

One dependency I need to upgrade tho. Some vibrations package i need to upgrade from version 1.7.0 to 3.1.4. Again I saw some logs in the console when trying to launch my app and this package complained to not be 16kb pages ready.

Hiccups

One of my emulators couldn't start my app again, flutter set it was not supported.

I guess its because this emulator was x86. I couldn't make another emulator with this architecture so i guess it was because of that.

And at one point also thought my it would be nice to just restart the notebook. It was before i checked the console logs for future deprecations to fix those. I wondered why the hell the app won't work. A restart will not hurt anybody, right?

Well it somehow removed my vs code. Everything was still in place after a fresh install. So i was wondering if the internal update system of vs code did something wrong ...


Focuslist is 16kb pages ready

Any way now its working!

Raised the version of Focuslist and uploaded to the google play store. Google play store didn't complain and Focuslist is now 16kb pages ready.

Thanks for reading,

hope it helped a little bit.

Try out Focuslist: Here


Have a nice Day

Szanik
Thanks for reading! Subscribe for free to receive new posts and support my work.

Join the Adventure

New articles delivered to your inbox. No spam, unsubscribe anytime.

0 Comments

No comments yet. Be the first to comment!