{"id":55255,"date":"2022-07-11T15:06:46","date_gmt":"2022-07-11T09:36:46","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=55255"},"modified":"2022-07-11T15:06:46","modified_gmt":"2022-07-11T09:36:46","slug":"android-katha-onactivityresult-is-deprecated-now-what","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/android-katha-onactivityresult-is-deprecated-now-what\/","title":{"rendered":"Android Katha: onActivityResult is Deprecated. Now What?"},"content":{"rendered":"

\"Blog<\/p>\n

 <\/p>\n

Hi and welcome to my blog,<\/p>\n

During our Android application development, we have been using\u00a0startActivityForResult<\/strong>\u00a0and\u00a0onActivityResult<\/strong>\u00a0methods a lot for the sake of callbacks from activities. It was really-clear and easy to implement. But Google knows.<\/p>\n

Unfortunately, now we are getting a warning for this method in our code.<\/p>\n

So the question is, Now What?<\/p>\n

And the answer is:\u00a0ActivityResultLauncher.<\/strong><\/p>\n

Pros:<\/strong><\/p>\n

    \n
  1. We can now launch activities for the result from fragments and receive the results in fragments without going through the activity.<\/li>\n
  2. Instead of distinguishing requests with fallible INT codes we now have strongly typed classes.<\/li>\n
  3. We can have separate callbacks for separate requests, eliminating the need for switch-case in response handling.<\/li>\n<\/ol>\n

    onActivityResult(Kotlin)<\/strong>:<\/p>\n

    \n
    fun openSecondActivityForResult() {\r\n    val intent = Intent(this, SecondActivity::class.java)\r\n    startActivityForResult(intent, REQUEST_CODE)\r\n}\r\n\r\noverride fun onActivityResult(requestCode: Int, resultCode: Int, data: Intent?) {\r\n    super.onActivityResult(requestCode, resultCode, data)<\/span>    \r\n    \r\n    if (resultCode == Activity.RESULT_OK <\/em>&& requestCode == REQUEST_CODE) {\r\n        \/\/ Do operations\r\n    }\r\n}\r\n\r\n<\/span><\/pre>\n<\/blockquote>\n
    ActivityResultLauncher(Kotlin)<\/strong>:<\/p>\n
    \n
    fun openSecondActivityForResult() {\r\n    val intent = Intent(this, SecondActivity::class.java)\r\n    activityResultLauncher.launch(intent)\r\n}\r\n\r\n<\/span>\/\/ We can do the assignment inside onAttach or onCreate\r\nvar activityResultLauncher = registerForActivityResult(StartActivityForResult()) { result ->\r\n    \/\/ There are no request codes\r\n\r\n<\/span>    if (result.resultCode == resultCode1 && result.data != null) {\r\n        \/\/ Do operations\r\n    } else if (result.resultCode == resultCode2) {\r\n        \/\/ Do operations\r\n    }\r\n}<\/span><\/pre>\n<\/blockquote>\n
    \u2014 \u2014 \u2014 \u2014 \u2014 \u2014 \u2014 \u2014 How to replace existing calls\u2014 \u2014 \u2014 \u2014 \u2014 \u2014 \u2014 \u2014<\/em><\/p>\n
    Steps to replace old one with the new one (Kotlin):<\/p>\n
      \n
    1. In place of overridden method\u00a0onActivityResult(\u2026)<\/strong>, use<\/li>\n<\/ol>\n
      \n
      \/\/ We can do the assignment inside onAttach or onCreate\r\n<\/span>var activityResultLauncher = registerForActivityResult(StartActivityForResult()) { result ->\r\n    \/\/ There are no request codes    \r\n\r\n<\/span>    if (result.resultCode == resultCode1 && result.data != null) {\r\n        \/\/ Do operations\r\n    } else if (result.resultCode == resultCode2) {\r\n        \/\/ Do operations\r\n    }\r\n}<\/span><\/pre>\n<\/blockquote>\n
      \u00a0 \u00a0 \u00a02. In place of startActivityForResult(intent, REQUEST_CODE)<\/strong>, use<\/p>\n
      \n
      val intent: Intent = Intent(this, SecondActivity::class.java<\/em>) \r\nactivityResultLaunch.launch(intent)<\/span><\/pre>\n<\/blockquote>\n
      \u00a0 \u00a0 \u00a03. In SecondActivity.java class, while returning back to the source activity, code will remain the same like –<\/p>\n
      \n
      val intent = Intent()\r\nsetResult(FirstActivity.resultCode1, intent)\r\nfinish()<\/span><\/pre>\n<\/blockquote>\n
      \n
      \n<\/blockquote>\n
      Please find the complete code with some demo screens on GitHub<\/a><\/p>\n
      Thanks for visiting, Keep reading & keep improving \ud83d\ude42<\/p>\n
      <\/div>","protected":false},"excerpt":{"rendered":"
        Hi and welcome to my blog, During our Android application development, we have been using\u00a0startActivityForResult\u00a0and\u00a0onActivityResult\u00a0methods a lot for the sake of callbacks from activities. It was really-clear and easy to implement. But Google knows. Unfortunately, now we are getting a warning for this method in our code. So the question is, Now What? And […]<\/p>\n","protected":false},"author":1476,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":324,"footnotes":""},"categories":[518],"tags":[4993],"class_list":["post-55255","post","type-post","status-publish","format-standard","hentry","category-android","tag-android-kotlin-java-deprecated-onactivityresult"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t