[英]app closing every time i log in with facebook
Every time i log in with facebook in my app it get closed without any error... But, this is the log i get when the app calls the loginfacebook dialog.每次我在我的应用程序中使用 facebook 登录时,它都会关闭而没有任何错误......但是,这是我在应用程序调用 loginfacebook 对话框时得到的日志。
Help!帮助! and thanks.
谢谢。
D/OpenGLRenderer: GL error from OpenGLRenderer: 0x501
D/OpenGLRenderer:来自 OpenGLRenderer 的 GL 错误:0x501
E/OpenGLRenderer: GL_INVALID_VALUE
E/OpenGLRenderer:GL_INVALID_VALUE
E/ViewRootImpl: sendUserActionEvent() mView == null
E/ViewRootImpl: sendUserActionEvent() mView == null
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
D/dalvikvm: GC_FOR_ALLOC freed 499K, 29% free 8575K/11996K, paused 23ms, total > 23ms
D/dalvikvm:GC_FOR_ALLOC 释放 499K,29% 释放 8575K/11996K,暂停 23 毫秒,总计 > 23 毫秒
I/v_gralloc: Self allocation
I/v_gralloc:自分配
W/IInputConnectionWrapper: getCursorCapsMode on inactive InputConnection
W/IInputConnectionWrapper:非活动输入连接上的 getCursorCapsMode
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
W/IInputConnectionWrapper: getSelectedText on inactive InputConnection
W/IInputConnectionWrapper:非活动输入连接上的 getSelectedText
W/IInputConnectionWrapper: getTextBeforeCursor on inactive InputConnection
W/IInputConnectionWrapper: getTextBeforeCursor on inactive InputConnection
W/IInputConnectionWrapper: getTextAfterCursor on inactive InputConnection
W/IInputConnectionWrapper:非活动输入连接上的 getTextAfterCursor
W/IInputConnectionWrapper: getCursorCapsMode on inactive InputConnection
W/IInputConnectionWrapper:非活动输入连接上的 getCursorCapsMode
D/dalvikvm: GC_FOR_ALLOC freed 645K, 29% free 8565K/11996K, paused 17ms, total > 17ms
D/dalvikvm:GC_FOR_ALLOC 释放 645K,29% 释放 8565K/11996K,暂停 17 毫秒,总计 > 17 毫秒
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/Choreographer: Skipped 38 frames!
I/编舞:跳过38帧! The application may be doing too much work on its main thread
应用程序可能在其主线程上做了太多工作
E/ViewRootImpl: sendUserActionEvent() mView == null
E/ViewRootImpl: sendUserActionEvent() mView == null
I/chromium: [INFO:CONSOLE(0)] "event.returnValue is deprecated. Please use the > standard event.preventDefault() instead.", source: (0)
I/chromium: [INFO:CONSOLE(0)] "event.returnValue 已被弃用。请使用 > 标准 event.preventDefault() 代替。",来源:(0)
W/chromium: [WARNING:spdy_session.cc(2388)] Received WINDOW_UPDATE for invalid > stream 13
W/chromium: [警告:spdy_session.cc(2388)] 收到 WINDOW_UPDATE 无效 > 流 13
W/chromium: [WARNING:spdy_session.cc(2388)] Received WINDOW_UPDATE for invalid > stream 15
W/chromium: [警告:spdy_session.cc(2388)] 收到 WINDOW_UPDATE 无效 > 流 15
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
I/v_gralloc: Self allocation
I/v_gralloc:自分配
D/dalvikvm: GC_FOR_ALLOC freed 590K, 29% free 8605K/11996K, paused 54ms, total > 54ms
D/dalvikvm:GC_FOR_ALLOC 释放 590K,29% 释放 8605K/11996K,暂停 54 毫秒,总计 > 54 毫秒
E/ViewRootImpl: sendUserActionEvent() mView == null
E/ViewRootImpl: sendUserActionEvent() mView == null
E/ViewRootImpl: sendUserActionEvent() mView == null
E/ViewRootImpl: sendUserActionEvent() mView == null
E/ViewRootImpl: sendUserActionEvent() mView == null
E/ViewRootImpl: sendUserActionEvent() mView == null
help!帮助!
This happens because your application is doing too much processing in UI thread
So do work with high processing on a different thread try implementing Async Tasks
因此,请尝试在不同线程上进行高处理,尝试实现
Async Tasks
check out below link AsyncTask Android example查看下面的链接AsyncTask Android 示例
I had android:noHistory="true" on my manifest file for the Activity.我的活动清单文件中有 android:noHistory="true" 。 So whenever the facebook activity was being loaded the login activity was being destroyed.
因此,每当加载 facebook 活动时,登录活动就会被销毁。
changing to "false" solved it更改为“false”解决了它
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.