The optional category string may be assigned to a broadcast intent via a call to the addCategory() method. As with standard intents, data is added to a broadcast intent using key-value pairs in conjunction with the putExtra() method of the intent object. When a broadcast intent is created, it must include an action string in addition to optional data and a category string. In addition to providing a messaging and event system between application components, broadcast intents are also used by the Android system to notify interested applications about key system events (such as the external power supply or headphones being connected or disconnected). What’s not explicitly said on the documentation is that if there’s any activity from the application paused - or in other words, that wasn’t finished - it will be kept on the back stack (activity stack) and will be resumed once there’s no more activities on top of it.Broadcast intents are Intent objects that are broadcast via a call to the sendBroadcast(), sendStickyBroadcast() or sendOrderedBroadcast() methods of the Activity class (the latter being used when results are required from the broadcast). Note: I’ve cleaned the logs to filter and highlight the important information. On MainActivity it starts SecondActivity btn_tOnClickListener

The layout is also really simple on both - it has only one button with a defined user action. They extend from AppCompatActivity and don’t have any special attribute declared on the AndroidManifest (no launchMode, nothing) Imagine a simple application with just two activities: - MainActivity - SecondActivity My goal with this article (and probably a couple more that are gaining some dust on drafts) is to create awareness on some scenarios that might arise during Android development - in this first one, why you should never call System.exit(n) or in Kotlin exitProcess(n) Use caseĪlthough the use case where I’ve found the issue is a bit complex to exemplify, I’ve created a simple project to easily show what was happening. Well, this is not going to be a fairytale but instead a cautionary tale. Until one day, during a connectivity problem, he appeared leaving us speechless.

Once upon a time… there was an issue that was hidden in plain sight! It lived freely for years without no one noticing it.

Android studio java finish method