blocks|key|1154230|text|是否保证调用Activity.onStop()+(API+11+%2B)|type|blockquote|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1154231|是的，它保证在蜂窝后设备(API+11+%2B)上调用。|unstyled|1154232|来源1：活动生命周期视频教程-由Google+developer倡导者教授|1154233|来源2：https://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle|1154234|​|1154235|📷|atomic|1154236|1154237|来源3：AndroidLifeCycle关于www.vogella.com的文章|1154238|1154239|1154240|1154241|entityMap|0|LINK|mutability|MUTABLE|url|https://www.youtube.com/watch?v=yGMMTxl_vho|1|https://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle|2|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/48229ee945feb6a159081d50a843e9d5.png|imageAlt|3|http://www.vogella.com/tutorials/AndroidLifeCycle/article.html|4|https://developer.qcloudimg.com/http-save/yehe-900000/518fa209c622a07d802470b3a5fe5029.png^0|6|H|0|0|4|X|0|0|4|2B|1|0|0|0|1|2|0|0|4|10|3|0|0|0|1|4|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1K|8|@]|D|@]|E|$]]|$1|I|3|J|5|H|7|1L|8|@]|D|@$9|1M|A|1N|1|1O]]|E|$]]|$1|K|3|L|5|H|7|1P|8|@]|D|@$9|1Q|A|1R|1|1S]]|E|$]]|$1|M|3|N|5|H|7|1T|8|@]|D|@]|E|$]]|$1|O|3|P|5|Q|7|1U|8|@]|D|@$9|1V|A|1W|1|1X]]|E|$]]|$1|R|3|N|5|H|7|1Y|8|@]|D|@]|E|$]]|$1|S|3|T|5|H|7|1Z|8|@]|D|@$9|20|A|21|1|22]]|E|$]]|$1|U|3|N|5|H|7|23|8|@]|D|@]|E|$]]|$1|V|3|P|5|Q|7|24|8|@]|D|@$9|25|A|26|1|27]]|E|$]]|$1|W|3|N|5|H|7|28|8|@]|D|@]|E|$]]|$1|X|3|-4|5|H|7|29|8|@]|D|@]|E|$]]]|Y|$Z|$5|10|11|12|E|$13|14]]|15|$5|10|11|12|E|$13|16]]|17|$5|18|11|19|E|$1A|1B|1C|-4]]|1D|$5|10|11|12|E|$13|1E]]|1F|$5|18|11|19|E|$1A|1G|1C|-4]]]]

<blockquote>
 Is <code>Activity.onStop()</code> guaranteed to be called (API 11 +)
</blockquote>

Yes, it is guaranteed to be called on post-Honeycomb devices (API 11 +)

Source 1: <a href="https://www.youtube.com/watch?v=yGMMTxl_vho" rel="noreferrer">Video tutorial on Activity life cycle - taught by Google developer advocate</a>

Source 2: <a href="https://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle" rel="noreferrer">https://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle</a>

<a href="https://i.stack.imgur.com/DgHBb.png" rel="noreferrer"><img src="https://i.stack.imgur.com/DgHBb.png" alt="Image screenshot from developer.android.com"></a>

Source 3: <a href="http://www.vogella.com/tutorials/AndroidLifeCycle/article.html" rel="noreferrer">AndroidLifeCycle article on www.vogella.com</a>

<a href="https://i.stack.imgur.com/vhosQ.png" rel="noreferrer"><img src="https://i.stack.imgur.com/vhosQ.png" alt="Image screenshot from www.vogella.com"></a>

blocks|key|1154147|text|如果你再往下看ActivityLifeCycle参考，上面写着：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1154148|对于那些未被标记为可杀死的方法，该活动的进程将不会被系统从调用该方法时开始并在其返回后继续终止。因此，活动处于可杀死状态，例如，在onPause()之后到onResume()的开始之间。|blockquote|style|BOLD|1154149|由于这似乎是重新生效点#1，我会错误地在保守的一边，设计和规划我的代码，就好像第1点是真的，忽略了第2点。|1154150|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle^0|7|J|0|0|1F|10|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@$A|X|B|Y|G|H]]|9|@]|C|$]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

If you look further down in the <a href="http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle" rel="nofollow noreferrer">ActivityLifeCycle reference</a>, it says:
<blockquote>
For those methods that are not marked as being killable, the activity's process will not be killed by the system starting from the time the method is called and continuing after it returns. Thus an activity is in the killable state, for example, between after onPause() to the start of onResume().
</blockquote>
Since this appears to re-inforce point #1, I would err on the conservative side and design and plan my code as if point #1 were true and ignore point #2.

It is unclear (to me, at least) from the documentation whether Activity.onStop is guaranteed to be called. There are two places with seemingly contradictory information.

<ol>
<li>Javadoc for Activity.onStop:</li>
</ol>

<blockquote>
 Note that this method may never be called, in low memory situations where the system does not have enough memory to keep your activity's process running after its onPause() method is called.
</blockquote>

<ol start="2">
<li>Documentation (in particular 'Killable' column) for Activity class <a href="http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle">http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle</a>:</li>
</ol>

<blockquote>
 Starting with Honeycomb, an application is not in the killable state until its onStop() has returned. This impacts when onSaveInstanceState(Bundle) may be called (it may be safely called after onPause() and allows and application to safely wait until onStop() to save persistent state.
</blockquote>

It's a bit of a struggle to find a way that both pieces of documentation are telling the truth. The only scenario I can think of is this: Suppose you are developing on target API 21 (with min sdk 10) and write an Activity with an onStop() method. If you then run this application on an API 10 phone, onStop() is not guaranteed to be called. This scenario means that the documentation from points 1. and 2. above are both true. Otherwise, one of them must be false.

Is Activity.onStop() guaranteed to be called (API 11 +)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

从文档中(至少对我来说)还不清楚是否保证调用Activity.onStop。有两个地方似乎有矛盾的信息。用于Activity.onStop的Javadoc：请注意，在内存不足的情况下，在调用活动的onPause()方法之后，可能永远不会调用该方法。活动类的文档(特别是“Killable”列)从蜂巢开始，应用程序在返回onStop()之前不会处于可杀死状态。当onSaveInstanceState(

问是否保证调用Activity.onStop() (API 11 +)
EN

回答 2

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否保证调用Activity.onStop() (API 11 +)EN

回答 2

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否保证调用Activity.onStop() (API 11 +)
EN