I have just pushed Build 161 to Google Play, which fixes the crash issue with the Account Manager. HOWEVER, Google has recently changed its policy and I must include a Privacy Policy that meets their requirements. I've structured one based on a policy I used for another app (Bike Tracker), but I don't know how long this will take to clear. Even if my policy is acceptable, I would guess that someone has to check it out in person, which might mean the build will not be approved until Monday at the earliest. If the policy isn't approved, and I have to go through countless rewrites to get it correct, then who knows how long this might take.
If anyone currently uses the MULTIPLE ACCOUNTS feature and is DESPERATE to get a fixed copy, I have provided an APK to sideload, but there's a big gotcha that goes with this. When apps are uploaded to the Play Store, they are RE-SIGNED by Google. That means that the signature of this APK and the signature of the copy you previously installed from the Play Store are NOT COMPATIBLE. If you try to install this one over your existing copy IT WILL FAIL.
The only way to install APK is to UNINSTALL the existing one and then sideload the app afresh. Later, once the new build is accepted on the Play Store, you'll have to uninstall the sideloaded app and reinstall the one from the store. Any configurations you made will need to made again, unless you have a reliably way of backing up app data and applying it to a new install.
If you absolutely can't wait, and are willing to go through this pain described above, then you can download the APK attached to this message. Otherwise, just wait for the Play Store to approve me.
NOTE: If you do not use the MULTIPLE ACCOUNTS feature, then this update is completely useless to you anyway, so definitely DO NOT bother to go through this.