Skip to content

Conversation

murilopereirame
Copy link
Contributor

Google now requires all Android apps to support 16KB page sizes until November to remain eligible for publishing on the Play Store.

This commit updates the Kotlin version, NDK, target and compile SDK versions, as well all third-party dependencies used by the apps, making our Apps compatibility with 16KB page size support.

Closes #9679

Google now requires all Android apps to support 16KB page sizes
until November to remain eligible for publishing on the Play Store.

This commit updates the Kotlin version, NDK, target and compile SDK
versions, as well all third-party dependencies used by the apps,
making our Apps compatibility with 16KB page size support.

Closes #9679
applicationId = "de.tutao.calendar"
minSdk = 26
targetSdk = 35
targetSdk = 36
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we have to raise target SDK already?
https://developer.android.com/about/versions/16/behavior-changes-16

We currently opt out of edge-to-edge if I remember right and it's going away
https://developer.android.com/about/versions/16/behavior-changes-16#edge-to-edge

I'm also not sure we do the back gesture right still?
https://developer.android.com/about/versions/16/behavior-changes-16#predictive-back

Do we need to handle local network for debugging?
https://developer.android.com/about/versions/16/behavior-changes-16#local-network-permission

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, we must solve Edge to Edge bugs first. Some stuff shows behind the navigation bar :/ I moved back to 35.

Regarding the other points:

  • The back gesture we already do it in the right way and I also updated the Activity lib, as recommended;
  • The app seems to be working fine within our local network.


buildscript {
ext.kotlin_version = '2.0.0'
ext.kotlin_version = '2.2.20'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked and it seems like there should be no changes that break things for us which is good

}
}
ndkVersion = "26.1.10909125"
ndkVersion = "28.2.13676358"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there are quite a few places where we might need to update the ndk version as well…

here is one:

ENV ANDROID_NDK_VERSION="25.2.9519653"

you said you needed a new flag for it as well. We also check in the compiled artifact for it so you need to rebuild it I guess.

there's also a change on F-Droid side that we should not forget:
https://gitlab.com/fdroid/fdroiddata/-/blob/b42b43252a71167333dc7e20536c5e41cf085712/metadata/de.tutao.tutanota.yml#L4857

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we saw, sqlchipher adopts the use of flags in Application.mk, making the NDK update on our fork not needed.
Regarding F-Droid, I'll create a PR on their side.

Unfortunately we still have some pending changes that
we must do before upgrading to 36.
@murilopereirame murilopereirame linked an issue Sep 23, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update Android to support 16KB

2 participants