mView has no focus+DecorView setVisiblity: visibility = 4+Finishing stop of ActivityRecord

最新推荐文章于 2022-09-22 10:09:05 发布
原创 最新推荐文章于 2022-09-22 10:09:05 发布 · 2.7k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#Android开发

09-24 18:22:23.692: E/AndroidRuntime(22703): FATAL EXCEPTION: main
09-24 18:22:23.692: E/AndroidRuntime(22703): Process: com.example.nongmin, PID: 22703
09-24 18:22:23.692: E/AndroidRuntime(22703): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.example.nongmin/com.jarvis.user.info.UApplyedActivity}: android.view.InflateException: Binary XML file line #17: Error inflating class com.clockrock.widget.PullToRefreshLayout
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2392)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2443)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.app.ActivityThread.access$800(ActivityThread.java:157)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1354)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.os.Handler.dispatchMessage(Handler.java:110)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.os.Looper.loop(Looper.java:193)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.app.ActivityThread.main(ActivityThread.java:5348)
09-24 18:22:23.692: E/AndroidRuntime(22703): at java.lang.reflect.Method.invokeNative(Native Method)
09-24 18:22:23.692: E/AndroidRuntime(22703): at java.lang.reflect.Method.invoke(Method.java:515)
09-24 18:22:23.692: E/AndroidRuntime(22703): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:829)
09-24 18:22:23.692: E/AndroidRuntime(22703): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:645)
09-24 18:22:23.692: E/AndroidRuntime(22703): at dalvik.system.NativeStart.main(Native Method)
09-24 18:22:23.692: E/AndroidRuntime(22703): Caused by: android.view.InflateException: Binary XML file line #17: Error inflating class com.clockrock.widget.PullToRefreshLayout
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:707)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.view.LayoutInflater.rInflate(LayoutInflater.java:755)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.view.LayoutInflater.rInflate(LayoutInflater.java:758)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.view.LayoutInflater.inflate(LayoutInflater.java:492)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.view.LayoutInflater.inflate(LayoutInflater.java:397)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.view.LayoutInflater.inflate(LayoutInflater.java:353)
09-24 18:22:23.692: E/AndroidRuntime(22703): at com.jarvis.user.info.UApplyedActivity.onCreate(UApplyedActivity.java:47)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.app.Activity.performCreate(Activity.java:5451)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1097)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2346)
09-24 18:22:23.692: E/AndroidRuntime(22703): ... 11 more
09-24 18:22:23.692: E/AndroidRuntime(22703): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.clockrock.widget.PullToRefreshLayout" on path: DexPathList[[zip file "/data/app/com.example.nongmin-2.apk"],nativeLibraryDirectories=[/data/app-lib/com.example.nongmin-2, /vendor/lib, /system/lib]]
09-24 18:22:23.692: E/AndroidRuntime(22703): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
09-24 18:22:23.692: E/AndroidRuntime(22703): at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
09-24 18:22:23.692: E/AndroidRuntime(22703): at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.view.LayoutInflater.createView(LayoutInflater.java:559)
09-24 18:22:23.692: E/AndroidRuntime(22703): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:696)
09-24 18:22:23.692: E/AndroidRuntime(22703): ... 20 more


错误原因：自定义布局没有搞




09-24 18:42:59.296: V/ActivityThread(23911): Finishing stop of ActivityRecord{42556780 token=android.os.BinderProxy@42555df8 {com.example.nongmin/com.jarvis.mytaobao.home.Main_FA}}: show=false win=com.android.internal.policy.impl.PhoneWindow@42626968
09-24 18:42:59.296: V/PhoneWindow(23911): DecorView setVisiblity: visibility = 4 ,Parent =ViewRoot{425587f8 com.example.nongmin/com.jarvis.mytaobao.home.Main_FA,ident = 0}, this =com.android.internal.policy.impl.PhoneWindow$DecorView{426278f8 I.E..... R....... 0,0-1080,1920}


09-24 18:47:02.781: V/ActivityThread(24144): Finishing stop of ActivityRecord{42561c30 token=android.os.BinderProxy@425612a8 {com.example.nongmin/com.jarvis.mytaobao.home.Main_FA}}: show=false win=com.android.internal.policy.impl.PhoneWindow@42581038
09-24 18:47:02.782: V/PhoneWindow(24144): DecorView setVisiblity: visibility = 4 ,Parent =ViewRoot{4255d6d0 com.example.nongmin/com.jarvis.mytaobao.home.Main_FA,ident = 0}, this =com.android.internal.policy.impl.PhoneWindow$DecorView{42581e68 I.E..... R....... 0,0-1080,1920}


09-24 18:52:35.296: D/ActivityThread(24420): ACT-STOP_ACTIVITY_HIDE handled : 0 / android.os.BinderProxy@4255eed0




09-24 19:06:15.949: W/ViewRootImpl(25176): mView has no focus, use com.android.internal.policy.impl.PhoneWindow$DecorView{441e4480 V.E..... R.....ID 0,0-1080,1920} instead








09-24 19:28:16.927: V/InputMethodManager(25968): onWindowFocus: null softInputMode=288 first=true flags=#1810100
09-24 19:28:16.928: V/InputMethodManager(25968): START INPUT: com.android.internal.policy.impl.PhoneWindow$DecorView{44095670 V.E..... R.....ID 0,0-1080,1920} ic=null tba=android.view.inputmethod.EditorInfo@440b8f20 controlFlags=#104
09-24 19:28:16.934: W/ViewRootImpl(25968): mView has no focus, use com.android.internal.policy.impl.PhoneWindow$DecorView{44095670 V.E..... R.....ID 0,0-1080,1920} instead
09-24 19:28:16.942: D/GraphicBuffer(25968): register, handle(0x7b8a1f18) (w:1080 h:1920 s:1088 f:0x1 u:0x000900)
09-24 19:28:16.954: D/OpenGLRenderer(25968): Flushing caches (mode 0)
09-24 19:28:16.956: D/GraphicBuffer(25968): unregister, handle(0x7b4f08e0) (w:1080 h:1920 s:1088 f:0x1 u:0x000900)
09-24 19:28:16.957: D/GraphicBuffer(25968): unregister, handle(0x7b508798) (w:1080 h:1920 s:1088 f:0x1 u:0x000900)
09-24 19:28:16.959: D/GraphicBuffer(25968): unregister, handle(0x7b899978) (w:1080 h:1920 s:1088 f:0x1 u:0x000900)
09-24 19:28:16.960: D/GraphicBuffer(25968): unregister, handle(0x7b396148) (w:1080 h:1920 s:1088 f:0x1 u:0x000900)
09-24 19:28:17.292: V/ActivityThread(25968): Finishing stop of ActivityRecord{4255f890 token=android.os.BinderProxy@4255ef08 {com.example.nongmin/com.jarvis.mytaobao.home.Main_FA}}: show=false win=com.android.internal.policy.impl.PhoneWindow@4262bcd0
09-24 19:28:17.293: V/PhoneWindow(25968): DecorView setVisiblity: visibility = 4 ,Parent =ViewRoot{42561908 com.example.nongmin/com.jarvis.mytaobao.home.Main_FA,ident = 0}, this =com.android.internal.policy.impl.PhoneWindow$DecorView{4262cb00 I.E..... R....... 0,0-1080,1920}
09-24 19:28:17.293: D/ActivityThread(25968): ACT-STOP_ACTIVITY_HIDE handled : 0 / android.os.BinderProxy@4255ef08

09-24 19:28:17.397: D/GraphicBuffer(25968): unregister, handle(0x7ab5a4c0) (w:534 h:105 s:544 f:0x1 u:0x000933)


上面的错误都是：少了一行代码  setContentView(view);

标题的错误是：少了一行代码  setContentView(view);




android finish 判断当前_踩坑之路：Activity执行finish以后onStop方法10s以后才调用
weixin_34443842的博客
01-26 1132
背景某天，测试提了一个bug，说当前页面关闭了以后回到了上一个页面，但是对应的音乐并没有立刻停止，而是过了一段时间才停止。于是翻阅了一下代码:@Overrideprotected void onStop() {super.onStop();if (mIsLoading) {mAudioTool.pausePlayAudio();}}mAudioTool.pausePlayAudio方法是停止播放音...
activity的几个相关类
编程生活
03-20 2184
android  中主要对activity管理的几个相关类。 ActivityRecord:通常的的 我们用的activity都是以继承activity的形式出现，但是在系统中,每个                      activity都是以activity record的形式出现，这个类包涵了 activity的各种信息。 ActivityThread：负责管理并执行主线成中的
android踩坑记录之view.setVisiblity()
Nbin_Newby的博客
12-10 417
问题 在某次做悬浮侧边栏的时候，遇到了一个问题：我用windowManager创建的悬浮侧边栏。点击中心view展开菜单，再次点击则隐藏菜单，如此简单的一个需求，却遇到了奇怪的问题，我没有对view的隐藏和显示设置动画，但是点击中心view，其他view在隐藏和显示的时候都会做一次过渡动画，即时设置android:animateLayoutChanges="false"也无效。手动添加动画后，也只...
DecorView的setSystemUiVisibility方法
weixin_43926327的博客
07-03 2395
开发中，通常都是在onCreate()中调用setContentView(R.layout.custom_layout)来实现想要的页面布局。页面都是依附在窗口之上的，而DecorView即是窗口最顶层的视图。想要更改一些高级一点的样式的话可以调用DecorView的setSystemUiVisibility方法，DecorView通过getWindow().getDecorView()获取，如下...
2.3 setVisiblity GONE 仍能响应事件
fyfcauc的专栏
11-14 1660
在适配2.3设备时，遇到一个问题， 将一个view已经设为GONE了，但是仍能收到touch事件，后来查了下stackoverflow, http://stackoverflow.com/questions/9333220/buttons-within-view-are-still-clickable-even-though-views-visibility-is-gone android的v
setSystemUiVisibility方法和getSystemUiVisibility方法
weixin_30938149的博客
04-12 532
这两个方法的调用方式如下： getActivity().getWindow().getDecorView().setSystemUiVisibility; getActivity().getWindow().getDecorView().getSystemUiVisibility; 参考资料： http://blog.youkuaiyun.com/stevenhu_223/article/det...
好的，继续帮我覆盖下面的方法 public void clickPowerMode(boolean check) { mDisplay.enablePowerSaveMode(!check); if (mView != null) { mView.updatePowerSwitch(mDisplay.isPowerMode()); } } public void updateSettingFocus(int type) { Log.i(TAG, "updateSettingFocus: type = " + type); SystemNotifyManager.getInstance().onSettingsClearFocus(type); } @Override public void onBrightnessModeChanged(int mode) { Log.i(TAG, "onBrightnessModeChange: mode = " + mode); if (mView != null) { mView.updateBrightnessAuto(mode == IOptixDisplay.MODE_AUTO); } }
07-24
之前的测试可能已经覆盖了基本调用，但需要确认是否测试了check为true和false的情况，以及mView为null的情况。用户可能希望确保这两种情况都被测试到，特别是mView为null时不会抛出异常。 接下来是...
帮我用mockito编写下面代码的单元测试 package com.st.systemsettings.presenter; import android.content.Context; import android.util.Log; import com.st.systemsettings.R; import com.st.systemsettings.base.BasePresenter; import com.st.systemsettings.contract.TimeContract; import com.st.systemsettings.interfa.TimeChangeListener; import com.st.systemsettings.manager.SystemNotifyManager; import com.st.systemsettings.manager.TimeManager; public class TimeManagerPresenterImpl implements BasePresenter<TimeContract.View> { private static final String TAG = "TimeManagerPresenterImp"; private TimeContract.View mView; private TimeManager mTimeManager; private Context mContext; @Override public void registerView(TimeContract.View view) { this.mView = view; this.mContext = view.getContext(); mTimeManager = TimeManager.getInstance(); mTimeManager.setTimeChangeListener(mTimeChangeListener); } @Override public void init() { if (mView != null) { mView.updateWatchSwitch(mTimeManager.getWatchSwitch(), mTimeManager.getRestSwitch()); mView.updateWatchTime(mTimeManager.getWatchTime() + mContext.getResources().getString(R.string.time_item_manager_unit_minute)); mView.updateRestSwitch(mTimeManager.getRestSwitch()); mView.updateRestTime(mTimeManager.getRestTime() + mContext.getResources().getString(R.string.time_item_manager_unit_minute)); } } public void clickSwitchWatch(boolean open) { Log.i(TAG, "clickSwitchWatch: open = " + open); mTimeManager.setWatchSwitch(open); } public void clickWatchTime(int time) { Log.i(TAG, "clickWatchTime: time = " + time); mTimeManager.setWatchTime(time); } public void clickSwitchRest(boolean open) { Log.i(TAG, "clickSwitchRest: open = " + open); mTimeManager.setRestSwitch(open); } public void clickRestTime(int time) { Log.i(TAG, "clickRestTime: time = " + time); mTimeManager.setRestTime(time); } public void updateSettingFocus(int type) { SystemNotifyManager.getInstance().onSettingsClearFocus(type); } public boolean getSingeWatch() { return mTimeManager.getWatchSwitch(); } private final TimeChangeListener mTimeChangeListener = new TimeChangeListener() { @Override public void onWatchSwitchChanged(boolean open) { Log.i(TAG, "onWatchSwitchChanged: open = " + open); if (mView != null) { mView.updateWatchSwitch(open, mTimeManager.getRestSwitch()); } } @Override public void onWatchTimeChanged(int time) { Log.i(TAG, "onWatchTimeChanged: time = " + time); if (mView != null) { mView.updateWatchTime(mTimeManager.getWatchTime() + mContext.getResources().getString(R.string.time_item_manager_unit_minute)); } } @Override public void onRestSwitchChanged(boolean open) { Log.i(TAG, "onRestSwitchChanged: open = " + open); if (mView != null) { mView.updateRestSwitch(open); } } @Override public void onRestTimeChanged(int time) { Log.i(TAG, "onRestTimeChanged: time = " + time); if (mView != null) { mView.updateRestTime(mTimeManager.getRestTime() + mContext.getResources().getString(R.string.time_item_manager_unit_minute)); } } }; @Override public void unRegisterView() { } }
最新发布
07-25
- 测试监听器触发时，View的更新方法是否被调用，例如当调用mTimeChangeListener.onWatchSwitchChanged(true)，则验证mView.updateWatchSwitch(true, ...)是否被调用。 - 对于updateSettingFocus，验证...
好的，没有问题，继续帮我编写下面类的单元测试 package com.st.systemsettings.presenter; import android.util.Log; import com.optix.display.adaptor.IOptixDisplay; import com.st.systemsettings.base.BasePresenter; import com.st.systemsettings.contract.DisplayContract; import com.st.systemsettings.manager.DisplayManager; import com.st.systemsettings.manager.OptixDisplayManager; import com.st.systemsettings.manager.SystemNotifyManager; public class DisplayPresenterImpl implements BasePresenter<DisplayContract.View> { private static final String TAG = "DisplayPresenterImpl"; private DisplayContract.View mView; private DisplayManager mDisplay; private OptixDisplayManager mOptixDisplayManager; @Override public void registerView(DisplayContract.View view) { mView = view; } @Override public void unRegisterView() { mView = null; } @Override public void init() { Log.i(TAG, "init: "); mDisplay = DisplayManager.getInstance(); mOptixDisplayManager = OptixDisplayManager.getInstance(); mView.updateFountSize(mDisplay.getFontSize()); mView.updateThemeMode(mDisplay.getThemeMode()); mView.updateBrightnessAuto(mDisplay.getBrightnessModeAutomatic()); mView.updateMousePointer(mDisplay.getMousePointer()); mView.updatePowerSwitch(mDisplay.isPowerMode()); mOptixDisplayManager.setOptixDisplayListener(mOptixDisplayListener); } public void clickPowerMode(boolean check) { mDisplay.enablePowerSaveMode(!check); if (mView != null) { mView.updatePowerSwitch(mDisplay.isPowerMode()); } } public void adjustBrightness(int value) { Log.i(TAG, "adjustBrightness: value = " + value); mDisplay.setBrightValue(value * 5); } public void clickBrightAuto(boolean check) { mDisplay.setBrightnessModeAutomatic(check); } public void clickMousePointer(boolean check) { Log.i(TAG, "clickMousePointer: check = " + check); mDisplay.setMousePointer(check); mView.updateMousePointer(check); } public void clickFountItem(float size) { Log.i(TAG, "clickFountItem: size = " + size); mDisplay.setFontSize(size); if (mView != null) mView.updateFountSize(size); } public void clickThemeItem(int position) { mDisplay.setThemeMode(position); if (mView != null) mView.updateThemeMode(position); } public void updateSettingFocus(int type) { Log.i(TAG, "updateSettingFocus: type = " + type); SystemNotifyManager.getInstance().onSettingsClearFocus(type); } private final OptixDisplayManager.OptixDisplayListener mOptixDisplayListener = new OptixDisplayManager.OptixDisplayListener() { @Override public void onBrightnessChanged(int value) { Log.i(TAG, "onBrightnessChanged: value = " + value); if (mView != null) { mView.updateBrightnessValue(value / 5); } } @Override public void onBrightnessModeChanged(int mode) { Log.i(TAG, "onBrightnessModeChange: mode = " + mode); if (mView != null) { mView.updateBrightnessAuto(mode == IOptixDisplay.MODE_AUTO); } } }; }
07-24
用户之前的测试使用了JUnit4、Mockito和PowerMockito，所以继续沿用这些框架。测试类需要@RunWith(PowerMockRunner.class)和@PrepareForTest注解，准备需要mock的类。 测试用例的编写需要覆盖各个方法，包括init、...
非常好，继续帮我编写下面代码的单元测试 package com.st.systemsettings.presenter; import android.util.Log; import com.st.systemsettings.base.BasePresenter; import com.st.systemsettings.contract.PictureContract; import com.st.systemsettings.manager.PictureManager; import com.st.systemsettings.manager.SystemNotifyManager; public class PicturePresenterImpl implements BasePresenter<PictureContract.View> { private static final String TAG = "PicturePresenterImpl"; private PictureContract.View mView; private PictureManager mPictureManager; @Override public void registerView(PictureContract.View view) { this.mView = view; } @Override public void unRegisterView() { mView = null; } @Override public void init() { mPictureManager = PictureManager.getInstance(); mPictureManager.setPictureModeChangedListener(mPictureModeChangedListener); int result = mPictureManager.getPictureMode(); if (mView != null) { mView.updatePictureMode(result); } } public void clickItem(int position) { Log.i(TAG, "clickItem: position = " + position); mPictureManager.setPictureMode(position); } public void updateSettingFocus(int type) { Log.i(TAG, "updateSettingFocus: type = " + type); SystemNotifyManager.getInstance().onSettingsClearFocus(type); } private final PictureManager.PictureModeChangedListener mPictureModeChangedListener = new PictureManager.PictureModeChangedListener() { @Override public void onPictureModeChanged(int mode) { Log.i(TAG, "onPictureModeChanged: mode = " + mode); if (mView != null) { mView.updatePictureMode(mode); } } }; }
07-24
最后，根据用户之前的回复，可能需要遵循类似的测试结构，使用JUnit4、Mockito和PowerMockito组合，并在测试类中添加适当的注解如@PrepareForTest和@RunWith。同时，确保测试覆盖所有关键路径，包括正常流程和异常...
关于View在后台的getVisibility的坑
星光的专栏
12-20 6059
今天遇到了一个坑，直播间界面，用户清屏后，所有的View都不显示，恢复清屏后，所有的View都恢复显示。 为了判断此时是清屏还是非清屏状态，直接随便判断一个View的显示状态： public boolean isVisibility(){     return textView.getVisibility() == View.VISIBLE; } 奇怪的事情发生了，虽然所有的View都显
DecorView的setSystemUiVisibility方法和getSystemUiVisibility方法
boguesfei的博客
07-16 4219
开发中，通常都是在onCreate()中调用setContentView(R.layout.custom_layout)来实现想要的页面布局。页面都是依附在窗口之上的，而DecorView即是窗口最顶层的视图。Android frameworks中，与窗口视图处理相关的类，主要是Window及其实现类PhoneWindow public class PhoneWindow extends Wi...
BiometricPrompt 之二 - 启动流程
u013398960的博客
03-28 1626
BiometricPrompt涉及跨进程间调用实现。 启动APP， BiometricService服务，Settings app(可能有参与), SystemUI锁屏应用。 看一次启动的log如下： 01-01 10:16:06.546 9457 9457 D WifiDppUtils: showLockScreen: 01-01 10:16:06.559 1043 1043 ...
Android源码解析之（十五）-->Activity销毁流程
热门推荐
一片枫叶的专栏
04-24 2万+
继续我们的源码解析，上一篇文章我们介绍了Activity的启动流程，一个典型的场景就是Activity a 启动了一个Activity b，他们的生命周期回调方法是： onPause(a) –> onCreate(b) –> onStart(b) –> onResume(b) –> onStop(a) 而我们根据源码也验证了这样的生命周期调用序列，那么Activity的销毁流程呢？它的生命周期
Activity启动流程（十）栈顶Activity执行onStop
perfectnihil的博客
06-06 2169
在ActivityThread的handleResumeActivity中，最后一行 一：从handleResumeActivity到Idler @Override public void handleResumeActivity(IBinder token, boolean finalStateRequest, boolean isForward, S...
Activity Stop条件及原理
xiaoyantan的博客
09-22 1379
在遇到窗口显示相关问题时，Activity Stop慢总是被先关注到，但是很多情况下Stop慢只是问题的结果并非原因。本文阐述Activity stop需要满足的条件，帮助分析Activity stop慢的原因。
android异常/错误集(暂停更新)
大辉的专栏
08-21 1万+
[2014-08-12 15:42:10 - Dex Loader] Unable to execute dex: Multiple dex files define  Lcom/jeremyfeinstein/slidingmenu/lib/CanvasTransformerBuilder$1; [2014-08-12 15:42:10 - NewInterest] Conversion
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值