Force close on record

fuzzweed · 2014-06-25, 07:38 PM

All attempts to press the record button are giving a force close in TE. Sorry no logs to hand as I post this so let me know if not repeatable and I'll dig them out later

bgowland · 2014-06-26, 10:02 AM

Is this related to using Search and record you mentioned in the beta test group? Or is it in general? I've fixed the issue with the Search / Record for the next beta release.

fuzzweed · 2014-06-26, 07:50 PM

No, I'm getting it via search and via EPG.

fuzzweed · 2014-06-26, 07:52 PM

I've just sent a crash report from the phone - do you get these?

fuzzweed · 2014-06-26, 07:54 PM

Here's the matching service logs
[ATTACH=CONFIG]38650[/ATTACH]

fuzzweed · 2014-06-26, 07:58 PM

And I've added the phone details to my signature before you ask again Smile

bgowland · 2014-06-27, 08:00 AM

fuzzweed Wrote:And I've added the phone details to my signature before you ask again

LOL

fuzzweed Wrote:I've just sent a crash report from the phone - do you get these?

They get sent to my Google Play dev console. I'm supposed to get an automated email to let me know but that doesn't seem to work any more and I don't check regularly so it sometimes takes a while before I spot them.

Anyway, here's the root of your problem...

Code:
java.lang.ClassCastException: [B]android.text.SpannableString cannot be cast to java.lang.String[/B]

at uk.co.beetec.android.nDroid.activity.GuideDetailActivity.onClick(GuideDetailActivity.java:159)

Hard to explain but that should never happen. Are you using a custom UI theme? In other words something which changes the default look / feel of things like buttons and other UI elements?

fuzzweed · (This post was last modified: 2014-06-27, 09:16 PM by fuzzweed.)

Struggling to think what it might be. I've just put the original ndroid back on and it's doing the same thing, and I know that used to work fine, so somethings changed, but no idea what. I've removed the last few apps I put on but no improvement. Any other pointers?

Also just tried on my work phone (same model and ROM) and getting the same force close.

bgowland · (This post was last modified: 2014-06-28, 07:46 AM by bgowland.)

fuzzweed Wrote:Struggling to think what it might be. I've just put the original ndroid back on and it's doing the same thing, and I know that used to work fine, so somethings changed, but no idea what. I've removed the last few apps I put on but no improvement. Any other pointers?

Also just tried on my work phone (same model and ROM) and getting the same force close.

I'm always prepared to admit something in my own code is broken but in this case I have to point the finger at the Cyanogenmod ROM.

The code that's triggering this problem is simply trying to work out if the text of the button is "Record" or "Cancel" by using a call to 'getText()'. In the context of my code 'getText()' should never return a 'SpannableString' and should always return a standard Java 'String' - this is where things are screwed up and it's not to do with my code.

I've Googled and found other issues related to the 4.4.2 Cyanogenmod ROM - similar although not identical.

I'll have a think and maybe put in a fix but it involves adding code I wouldn't normally have to.

fuzzweed · 2014-06-28, 09:01 AM

Is there anything to note in that the 'watch' and 'close' buttons work. Is this handled differently?