crash on manual connection

[ginjaninja 605]

Version 3.0.5420.23466

1.69

on first entry was prestented mediabrowser.tv pin or manual connection.

chose manual connection...client crashed. (to roku home page)

client continued to crash immediately on entry

 

had to quit server.

client then presented pin screen again.

started server

authenticated by pin.

can now logon but client doesnt auto logon to last user at startup..ie does not remember last user.

 

dont know how to get logs for roku client...

Edited November 4, 2014 by ginjaninja

[Luke 42077]

Ok, I've pushed another update that will wipe a lot of the saved server info, so it should be more like a fresh start. let me know if the crash happens again.

[ginjaninja 605]

@@Luke

I couldnt get the client to crash with the further update.

but playing around, clicking on all options madly...

 

it seems

'turning off' MB connect makes 'remember last user' work,,,aka with MB connect on, the client wont go straight in using the last users authentication...

(i have my user configured for no local authentication)

 

the interplay between MBConnect and Scan Manually is not intuitively presented in the interface, after initial setup...i mean in the change server interface.

 

initial understanding suggests that connect by 'MB connect' is the alternative to 'scan network'...they are ways of connecting the client to server...

but the preferences seem to suggest that they potentially complement each other..might be better to sign out of current connection method...to get back to the option of connect via ...MB Connect or Scan Network...

or to put it another way...if you have used scan network to connect to the server....why show anything todo with mbconnect in the interface.....does it make sense to do both at the same time?

if you have connected via scan manually....why give the user the option to connect by mb connect from within those preferences for that configuration.

i guess what i am saying is that the user login/connection options under change server options..seemed unintuitive to me...as i clicked between options..

 

Edit

Ok i think i understand better now..

 

the client shows options both for logged on username but also for the person sitting at the client who may want to connect to multiple servers as multiple separate usernames or usernames with a global scope accross multiple servers eg with mbconnect.....

 

so i guess the client is allowing the person sitting at the roku to slave multiple connections and user logons to the client's non volatile profile/configuration of the currently logged on username.

 

In this way the person can select between collections on multiple servers when identified as a user.

 

There is an issue about removing servers and once removed how the client behaves for the username and also the person sitting at the client...

 

I was unable to remove my local scanned server..the entry did not disappear..

 

On removal on my single currently connected server i was taken back to a select user/server interface...

 

Given the only server should have been removed..there should be no users to select until i have made a connection (using any method)..but the connection to the local server persisted and could not be removed...

 

 

Also when

1. Enter client by a user

2. Go to change server..remove server

3. Ui still shows users for old server (covered above)

4. Click back...shows retrieving..indefinitely...

5. Click back..client still shows content as if still logged on as user tp server which i disconnected from in 2

 

It probably all boils down to removed servers persisting...and this is what made me feel it was unintuitive.

Edited November 7, 2014 by ginjaninja