View Single Post
Old 12-09-2015, 11:30 AM   #93
the.Mtn.Man
Guru
the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.
 
the.Mtn.Man's Avatar
 
Posts: 710
Karma: 2483502
Join Date: Jul 2011
Device: Kobo Aura
Quote:
Originally Posted by eschwartz View Post
The only reason to write such checks, is if there is an expectation that they might, potentially, fail.

What do you think the purpose of it was, if not for people whose registration is broken without a third-party hack?
In which case the user would simply follow the prompts and reregister/re-sync their device, which seems to be the failsafe in this instance. The only reason you're encountering this "bug which isn't actually a bug" is because you're trying to bypass the normal function of your reader.
the.Mtn.Man is offline   Reply With Quote