Ah. Got it.

Finally had some time to look into each of these features. I think most of these are all doable and they will all be added to the roadmap. The only one I need more information on is the bonus. Could you give a bit more information on what you mean? Thank you!

People who go faster than you are reckless.

People who go slower than you are dumb.

And people who go the same speed as you are weirdos.

Buy a chest freezer

Figured it out. I was disabling crashlytics but the rest of Firebase was still being initialized. I will fix this issue in the next release.

FK I bit it

Thanks for reporting! Will look into this tonight.

Catler

more like 3-4 devs

I like Quebec but it is preferred to learn French (I am horrible at spoken languages, I’m having enough trouble with English let alone another language) and I don’t like their secession movement.

That doesn’t sound right but I don’t know enough about this to disprove it.

Right here is good. My preference is for people to comment feedback or feature requests on any of the release threads. You can also make a post here.

Unfortunately I did find a few bugs with this release so I will be doing another release later today to address the bugs.

If you just pour some green sprinkles on it then it’s essential the same thing as peas as green sprinkles are the same color as peas.

A13 added the concept of predictive back but it only supported a tiny fraction of what is considered predictive back now. A13 only supported the part where the back gesture would close the app and nothing else. In A14 and above, predictive back evolved into something that can be added for every single screen. Eg. if you go from ScreenA -> ScreenB and then initiate a back gesture from ScreenB then you will see ScreenA to show that will be where you end up.

The v1.45.0 release adds complete support for A14’s predictive back. The A13 predictive back has been supported by the app for a long time now so that support is not new with this release.

Looks like the issue is related to predictive back. I have a reproduction finally. I’ll have a fix for it in the next update. One workaround seems to be to swipe really quickly (although not a great workaround). Or you can tap the up button.

Confirmed I received the information. I also saw the video. Unfortunately even with the settings I cannot reproduce the issue in the video. I have more test devices that I can test on. I can also look at the code to see if I can find any issues as well. In any case I think I have everything I need to look into this.

Thank you for the reproduction step. I attempted to reproduce this issue on 3 different devices but I was unable to. I ran these tests on the play store release (v1.44.4). It might be something specific to your app settings. If you’d like me to look into it further could you please send me (reply here or DM me) a dump of your app settings? You can generate this settings dump by going to Settings > Import & Export settings > Export settings > Copy to clipboard. Thanks!

A holes a hole 😔

There are no fish in the comic strip