Just to add to what @Omgitstony indicated, what you’re describing was discussed quite a bit in the app v3.2.5 announcement topic, and the apparent bugs resulted in the v3.2.6 app release only 5 days later, so I’d expect an update to the latest app version to resolve your issue (if it hasn’t already).
Welcome to the Forum, @huntfamily98! 