Several users have reported a Mint sync and login problem from Mojito. The initial login succeeds, but after a few seconds the login window appears again, repeating over and over.
I have been able to reproduce the problem but have not identified the root cause yet. I will continue to investigate as time allows (given the holidays and all).
Thanks,
-b3
Update (2014-12-21):
I have found the problem and am fixing it. Give me a day or so to update the Download page with the new version.
Unfortunately, the fix requires a small change in the login code, which I have always kept in the script attached to the spreadsheet (so you can see exactly what the code does); but each time I need to fix an issue in the login code, you (the users) are forced to download a new copy of Mojito. I think I'm going to finally move that code into the separate script library (MojitoLib)...
Update (2014-12-23):
I've posted release 1.1.5 with the Mint login fix. Thanks for your patience. The fix requires you to download a new copy of Mojito. Sorry about that ...
-b3
I hear your dilemma.
ReplyDeleteJust an idea:
Perhaps you could host two different versions: the standard version, and also a "self-updating" version. This way, the "standard" version would retain its Mojito tradition of re-ensuring its (newer) users (that the code is safely hosted in their possession, and they can see exactly what the code does); whereas the "self-updating" version would be more up-to-date for those who want it. And to keep it simple (so the user isn't confounded with all these versions), the alternate version could be considered an "experimental" version, or available by request etc -
Another thing to consider is how often mint updates their API stuff; if its just once in a while then maybe we could get by with the way it is. But if they make changes often, then yeah, moving the script to the library host may be the better way to go
Its a good question
Sigh... I understand where you are coming from Laviator, and I would be asking for the same thing if I were on the other side of this project...
ReplyDeleteThe problem with your suggestion is that I would have to keep two copies of the same code, which essentially means that I couldn't update and refactor the "internal" copy because that would make it incompatible with the external (spreadsheet) code; and that would mean I would need to maintain and test two different versions. In fact, I would have to do that even if the two copies where identical. Also, from my perspective the "standard" and "alternate" versions would be reversed. The "standard" version would be the one with the login code inside MojitoLib because it would sit alongside the rest of the code where I could re-organize and improve it at will, and it would be the version I always test with. (You'd be surprised how often I change and refactor the code within MojitoLib.) The "alternate" version would be where the login code is in the spreadsheet itself, and it would probably be broken half the time because I wouldn't be testing it regularly, if at all.
Interestingly, I actually have two versions of the login code already (one small piece of it anyway). The second version, which is inside MojitoLib, is nearly identical to the code in the spreadsheet, except the internal version handles the case where the user saved his/her password in the Settings sheet. I didn't want the logic for how I "hide" the saved password to be in publicly visible code (security through obscurity).
As with many things, it comes down to trust. We are trusting Mint to protect the credentials to all of our financial accounts. (This was a big hurdle for me, I don't know about you.) Likewise, you are trusting me (MojitoLib) not to send your data to some hacker network as it is downloaded from Mint. And I can assure you, as a frequent user of Mojito myself, that nothing suspicious is happening to your data or mine.
Incidentally, I have already proceeded with moving the login code into MojitoLib (before you posted your comment), however I plan to keep a copy of the code in the spreadsheet script as well so users can see what it does, even though it won't be executed. I know this is not what you would prefer, but hopefully you see it as a gesture of goodwill.
-b3
Hello, when I click on either download link (demo or live) I get the error "We're sorry, your spreadsheet cannot be copied at this time. " Is this project still live and shared?
ReplyDeleteHi Tim. Thanks for bringing this to my attention. I have fixed the link. It seems that Google no longer supports the URL format I was using to automatically create a copy of the spreadsheet when you clicked the link. Now you must confirm that you want a copy of the spreadsheet first, rather than the copy being done automatically. It's an extra step, but pretty painless. Let me know if you have any problems.
DeleteThanks,
-b3
thanks for sharing this post with us.
ReplyDeleteDealersocket Login