prasanna
09/08/2025, 10:33 AMBillUploaded, SelectParticipants, SelectSplitMethod, AssignItems, SelectPayer, ShowSummary) but curious if there’s a more elegant solution you’ve used.
Any suggestions / best practices would be really helpful 🙏khushal dadwal
09/10/2025, 10:03 AMMuthu
09/16/2025, 11:29 AMBrais Gabin
09/16/2025, 2:03 PMHenzel
09/16/2025, 4:24 PMhari
09/17/2025, 6:17 AMJack Eblan
09/23/2025, 9:06 PMRavi
09/27/2025, 3:40 AMBehzod
09/29/2025, 5:29 AMDequency Yates
09/29/2025, 4:15 PMPlugguto
10/01/2025, 7:23 PMDanail Boyukliev
10/02/2025, 6:43 AMOpen web links in Gmail is enabled, the deeplink would not be triggered. If tested on an emulator with Gmail running older version of Gmail, it works even if Open web links in Gmail is enabled. Does anybody knows if there's been change in Gmail for this feature?bazbo.222
10/04/2025, 4:15 PMfun Modifier.drawYellowCross() = then(
object : DrawModifier {
override fun ContentDrawScope.draw() {
drawLine(
color = Color.Yellow,
start = Offset(0F, 0F),
end = Offset(size.width - 1, size.height - 1),
strokeWidth = 10F
)
drawLine(
color = Color.Yellow,
start = Offset(0F, size.height - 1),
end = Offset(size.width - 1, 0F),
strokeWidth = 10F
)
drawContent()
}
}
)
However, if I try creating a new Compose project with the most recent version of Android Studio 2025, pasting that piece of code into the default "Empty Views App" project template, the code gives the following compilation error:
Modifier factory functions must use the receiver Modifier instance
Now, personally, what I understand from this error is that my drawYellowCross() function should be an extension function of the Modifier class... which it is.
Anyway, to sum up, here are my questions:
1. How should I understand this error?
2. What changed in the versions from 2023 up 'till now?
3. How do I migrate / update my code properly?
Thanks in anticipation to anyone who wishes to chime in and help.Nick
10/05/2025, 1:45 PMTower Guidev2
10/06/2025, 10:00 AMNurlibay
10/07/2025, 8:31 AMprivate fun applyAppLocale(languageCode: String) {
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
// Android 13+: Use LocaleManager for per-app persistence
val localeManager = context.getSystemService(LocaleManager::class.java)
localeManager.applicationLocales = LocaleList.forLanguageTags(languageCode)
} else {
// Pre-Android 13: Use AppCompatDelegate
val locales = LocaleListCompat.forLanguageTags(languageCode)
AppCompatDelegate.setApplicationLocales(locales)
}
// Immediate update for resources (affects View-based UI)
val config = Configuration(context.resources.configuration)
config.setLocale(Locale(languageCode))
@Suppress("DEPRECATION")
context.resources.updateConfiguration(config, context.resources.displayMetrics)
}Dan Rusu
10/10/2025, 4:24 PMigor.wojda
10/13/2025, 10:52 AMzimjon
10/18/2025, 12:43 PMJhsagiv
10/19/2025, 8:31 PMArchit69 Appdeveloper
10/21/2025, 2:02 PMKarlMcCree
10/22/2025, 10:32 AMPablo
10/22/2025, 2:29 PMappCategory="game" in manifest and the activity forced to "landscape", the OS rotates the screen, displaying the game in portrait but simulating a fake landscape mode, with two black spaces on top and bottom of the game screen. But the main issue is that is destroying and recreating my activity. That breaks completly the game. How is supposed we should sholve this? Some games are old games developed a lot of years ago, even in java, and are not prepared to survive activity recreation. Supposedly appCategory="game" should help us keeping our games alive in Android 16, but that onDestroy and onCreate doesn't help.Georg Prohaska
10/24/2025, 10:41 AMagp = "8.13.0"
kotlin = "2.2.20"
[plugins]
androidApplication = { id = "com.android.application", version.ref = "agp" }
kotlinMultiplatform = { id = "org.jetbrains.kotlin.multiplatform", version.ref = "kotlin" }
plugins {
alias(libs.plugins.kotlinMultiplatform)
alias(libs.plugins.androidApplication)
...
}
kotlin {
sourceSets.all {
languageSettings {
optIn("kotlin.uuid.ExperimentalUuidApi")
}
}
androidTarget {
compilerOptions {
jvmTarget.set(JvmTarget.JVM_21)
}
}
...
}
And in the settings it looks like this:Sudarshan
11/03/2025, 4:25 AMremoveFirst() and removeLast() extension functions. Can anyone help me understand why they are problematic? If you'd like, you can directly reply to the author on his post on X.Luka Štorek
11/03/2025, 7:52 AMVlad Ghilicica
11/03/2025, 4:02 PMMarc Ivan Lim
11/10/2025, 6:09 AMmalik bilal
11/14/2025, 10:58 AM-keep rules for my @Entity models, DAO interfaces, and sometimes even fields.
My concern is:
If I keep these classes, their names and structure are no longer obfuscated in release builds. Doesn’t this expose the database schema to reverse-engineering? How do people handle this securely?
Any guidance or best practices would be really helpful!