The Remembary 2 launch has gone pretty smoothly - especially considering that the app has been almost entirely rewritten and the upgrade process does a lot of data changes under the hood.
First, a big thank you to all of the people who have submitted such enthusiastic reviews to the App Store. After all the hard work that went into this latest version, it's heartening to see that people are enjoying it.
Also, a big thank you to everyone who has written in, either to say nice things or to point out problems they've been having (or both!) - in the last few days I've managed to identify two annoying bugs:
Twitter access request / password loop
If you are upgrading from an earlier version of Remembary and have a password on your diary, but you tell the app that you *don't* want to give it Twitter access when it starts, you'll end up stuck in an endless loop of entering your password and then being asked to allow Twitter access over and over again.
I've confirmed that this is genuine problem, and a fix for this will be coming soon, but in the meantime please note that:
- Remembary only uses the Twitter accounts for *receiving* Twitter - it doesn't send anything, and certainly won't spam your followers or anything like that
- You can turn off your Twitter accounts (and all feed fetches for that matter) from inside the app from the Feeds popup (the top bar button with all the inward-pointing arrows); and finally
- You can turn off Twitter access at the OS level using the "Settings" app.
So, if you're finding yourself in this situation, just say yes to the Twitter account access for now so you can get into Remembary and then you can immediately turn off all Twitter access from the feeds popover if you don't want to be bothered with it.
Data Export to Mail Crash
If you try to send a "data" export of your diary in an email, the application will crash when it tries to pop up the mail interface. This doesn't happen with plain text exports, and also doesn't happen if saving the data export locally or to DropBox - just data exports going to email.
A fix for this is also on the way, but in the meantime you can save your data exports to DropBox or locally to your device, from which they can be copied to your computer the next time you plug it in.
Also note that Remembary saves a copy of the data export on your device before trying to send it in email - so your export hasn't been lost, you just have to plug your device into your computer and get the file out of iTunes.
I should have Remembary 2.0.1 ready to go early next week and it will hopefully be live in the App Store before Labour Day (depending on the approval process).
Thanks again to everyone for making this such a great upgrade and launch. Stay tuned - exciting things are coming soon!