Correctly handling unknown client error

R Ruben Ruben 2 years 11 months ago
0 2 0

Hi,

Following the documentation, i'm trying to get my app to correctly handle unkown_client errors when a user logs in after resetting rhoconnect or having deleted the user from the console.

According to the documentation, one must perform a full database reset, and try to login again. I've managed to do this without the user noticing anything, but it seems that it will generate a new device ID. This is a problem, since the old device id will be using a rhoconnect license until someone manually removes in from the web console.

Is there any way around this?

Please register or login to post a reply

2 Replies

B Brendan Higgins

UGH!  Tell me about it.

I spent weeks on this trying to come up with the work around for this.  I finally found one -- well at least it did what it was supposed to do, log the person in and remove the old device id.

I'd post the code, but in the meantime, while working though other issues with JavaScript code, we found a RhoConnect Client bug which Zebra acknowledged and put out a fix:

https://github.com/rhomobile/rhoconnect-client/blob/fix-v4-reset/ext/rh…

Oops, I should have checked the link, it does not work any more, contact me (or Zebra) for the fix

Once I used this code, it "broke" my code for Unknown Client.

I reverted to the documented handling and now you can do the reset and it will work.

I have been very frustrated with the JS code so far.

Let me know if you want more info.

K Kutir Mobility

Hi Ruben,
Have you tried
Rhom::Rhom.database_full_reset(false,true) ?
it will reset the db and protects the client information.
For more information,  Please see doc at http://docs.rhomobile.com/en/2.2.0/rhodes/rhom#resetting-the-database

Visnupriya R
Kutir Mobility

CONTACT
Can’t find what you’re looking for?