As of around five seconds ago, thanks to new Google Play tools, we are starting open enrollment into the beta tier of our Android app.
If you'd like to enroll or unenroll into the beta tier, please visit: https://play.google.com/apps/testing/com.stackexchange.marvin
After enrolling on that page you'll be able to see a beta version of the app when using the Play Store on your Android device. You'll still get the newest production version if we don't have anything actively in beta, but you can differentiate between the two tiers by looking at the release notes.
Beta updates's release notes begin with "NOTE: This is a beta update".
This post will be updated whenever we add in new beta features.
- Fix for Android app should not scroll back to top of page when rotation occurs while writing a comment
- Overhaul of how answer drafts are stored. We now properly support saving drafts for answer edits in addition to saving drafts for new answers.
- Fixed login with Google on Android 6.0 devices.
- Fixed a crash when trying to load certain feed item types on Android 6.0 devices.
- Switched out compile target from API 22 (Android 5.1) to API 23 (Android 6.0) to work with the new Marshmallow APIs and permission model.
- Fixed a crash when trying to join private beta sites.
- Fixed a bug when opening the app from a push notification while the app was not running previously, which resulted in an empty inbox being displayed in the app.
- Brings in the Chrome Custom Tabs API which gives much faster access to loading external links from the app. Note that this is only supported on Chrome 45 and above right now, so you'll need to be using the "Chrome Beta" app on your phone to see it.
- Fixes a crash when trying to load a question then leaving the view before it's fully finished loading.
- Attempts to fix a possible crash when entering the app from
- Implementation of the App Indexing API -- This means that you'll be able to quickly revisit questions and answers you've browsed in the app by searching from them using Google Now on your device.
If you have any feedback from beta testing, feel free to e-mail the team directly at [email protected] or post a comment or answer on this post.