Force close after linking to my Netflix account

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Go into app
2. The app directs me to api-user.netflix.com
3. I log into my account
4. I click the "Yes, link this account" button
5. It says it's linking and queueman FC's and gets caught in this loop over
and over

What is the expected output? What do you see instead?

The app should open linked to my account and it just FC's

What version of QueueMan are you using? I'm using version 0.9.6
On what version of Android? Cyanogen's 1.6 version 4.2.3.1
What type of device? MyTouch

Please provide any additional information below.

Original issue reported on code.google.com by jason...@gmail.com on 11 Nov 2009 at 8:06

[GoogleCodeExporter]

I refuse to support Cyanogen's builds (For ideological and logical reasons).  If
anyone is using an official 1.6 release please report it here. 

Original comment by OlliTech on 12 Nov 2009 at 1:31

• Added labels: OpSys-1.6, OpSys-Cyanogen, Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Cyanogen's builds are basically stock 1.6, good job alienating a vast amount of 
your customer base.

Original comment by jason...@gmail.com on 12 Nov 2009 at 2:40

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

:) I don't have customers, I have users..its a free app.

And 'basically' stock is meaningless. It is a modified version of the platform 
and
introduces code not found in official releases. I and many users rely on 
Android 1.6
without issue.

I am not contending that Cyanogen introduces bugs, but the simple truth is that 
it is
different, and developers should not be expected to support every home brew 
version
that is released out of compliance.

Sorry to see you go.

Original comment by OlliTech on 12 Nov 2009 at 7:39

[GoogleCodeExporter]

Anyone who is experiencing a Force Close error after authorizing for Netflix, 
please
see Issue 7.

Original comment by OlliTech on 12 Nov 2009 at 10:46

• Changed state: Invalid

[GoogleCodeExporter]

The issue, is that Cyanogen's build seemed to handle background applications
differently, effectively killing QM while the browser was present. This cause 
the
request token to be lost, so when the user returned QM was restrted, and looked 
for A
RT that was no longer there.

I have introduced code that allows QM to reinstantiate itself after a kill from 
the
activioty manager

Original comment by OlliTech on 21 Dec 2009 at 2:28

[GoogleCodeExporter]

Original comment by OlliTech on 21 Dec 2009 at 2:29

• Changed state: Verified