CODEWITHSUNDEEP
androiduser-interfacescreenvisibility
Renegade
Renegade

Reputation: 802

Building an Android app, UI goes blank after a second with some BinderProxy error

I've been building an app from last couple of days now. I'm getting this weird error, where after opening the app, the whole screen goes white and I can't do anything. I'm getting my logs normally although. Seems like the whole app is working fine just the UI goes blank and I think it has something to do with the following log that I get.

04-14 13:09:43.880: I/art(17944): Background partial concurrent mark sweep GC freed 5065(575KB) AllocSpace objects, 13(584KB) LOS objects, 29% free, 38MB/54MB, paused 8.631ms total 49.204ms

04-14 13:09:49.905: I/Timeline(17944): Timeline: Activity_launch_request id:com.packageName time:8607601

04-14 13:09:50.000: A/Home(17944): isFinishing = false

04-14 13:09:50.040: D/Activity(17944): performCreate Call secproduct feature valuefalse

04-14 13:09:50.040: D/Activity(17944): performCreate Call debug elastic valuetrue

04-14 13:09:50.150: I/Timeline(17944): Timeline: Activity_idle id: android.os.BinderProxy@a363fd9 time:8607846

04-14 13:09:50.220: V/ActivityThread(17944): updateVisibility : ActivityRecord{3fd6d07f token=android.os.BinderProxy@47236cc {com.packageName/com.packageName.Home}} show : false

Please help me out. Going crazy over here. Can't figure out what it is.

Some other things which might help you guys to understand my problem are:

  1. I'm using Facebook login in an activity and it only happens when I switch from the Facebook Activity to this activity(mostly)

  2. The activity is recreating itself which causes this bug.

Upvotes: 1

Views: 3391

Answers (3)

Renegade
Renegade

Reputation: 802

As I mentioned I was using SensorEventListener, I was using that in an activity previous to this one too. And I hadn't unregistered the listener before finishing that activity which caused this error. But thanks everybody for pointing me to the correct direction.

Upvotes: 0

AmDroid
AmDroid

Reputation: 131

The crash is because the binder you're getting back is an instance of BinderProxy, not your local binder class. This usually happens because your activity is attempting to bind to a service that is not in the same process. When binding across process boundaries, an instance of BinderProxy is used instead of the actual instance (since that's in a different process).

Try this

if(!((Activity) context).isFinishing())
{
    //your code
}

Upvotes: 0

AmDroid
AmDroid

Reputation: 131

  1. Have you used setContentView method properly to set layout
  2. Declared activity in menifest
  3. Please check in you class, may be there was any null reference of view or context

Upvotes: -1

Related Questions