Hey all!

Edit 2: Well that was cool: https://i.imgur.com/sTKLG76.png

Looks like I hit a stray key before building…resubmitting now as version 0.0.1.75

Edit: Update released.

Going to be pushing an update here in a few hours with the following changes:

  • The issue where tapping a post in your profile would cause a crash is fixed. We were getting ready to fix up profiles and this happened…sorry
  • Profile page is now available for any user. Just tap their name in the feed or search.
  • You can now swipe on an item in your inbox to mark it as unread. Still need to finish up mentions and messages, but I’ll have that done tomorrow.
  • Additional themes and a better way to select them. I’ll get system default added either tomorrow or day after that.
  • Other bug fixes under the hood

Let me know what all needs working on still and we will get it fixed up! Happy scrolling!

On a side note, I want to ask the following of everyone:

If you are having issues subscribing to communities (crash), please let me know the instance you are on and the community you are trying to subscribe to. I’m really curious to know what is going on there, as I am 100% unable to reproduce this issue but obviously it’s happening to a lot of you.

There has not been any significant change to the subscription logic which makes me think that this might have something to do with something going on with a certain instance, but I cannot be sure. I am also curious if this is something that happened with the latest update to .18 and the use of the .18 API and API client inside of Memmy. There appears to be proper error handling here in this logic, so I am not sure what might be causing that crash.

Thanks!

  • SlovenianSocket
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 years ago

    After enabling 2FA on lemmy.ca & adding my token to Memmy I can no longer view my subscriptions list, and if I force quit the app and re-launch it I have to re-enter my 2FA code before it will load my feed

    • gkd@lemmy.mlOPM
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 years ago

      Hmm…what version is lemmy.ca running? 18 or 18.1? The 2FA integration was done for 18. I’ll take a look at what might be the issue. I can test with lemmy.world here in a bit. Let me know if you get this to work in the mean-time.

      • SlovenianSocket
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 years ago

        They are currently running 0.18.0, I was having issues earlier in the day connecting to their API with Memmy & web-ui but that seems to be resolved now

        • gkd@lemmy.mlOPM
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 years ago

          Weird. I use 2FA on Lemmy.ml without issue. Can you send over a debug log and I’ll see if there’s anything there that might help me see what this happened?

            • gkd@lemmy.mlOPM
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 years ago

              Is this an account that you added with a fresh install or added as a second account? I see where the request returned “missing_totp_token” which is odd. I’ll give this a look in a bit to make sure it isn’t something wrong on my end.

              • SlovenianSocket
                link
                fedilink
                English
                arrow-up
                1
                ·
                2 years ago

                It’s the one and only account I’ve had linked in Memmy since the TestFlight launched. I’ll try a clean install and see if that helps

                • gkd@lemmy.mlOPM
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  2 years ago

                  Oh that is probably the issue. Give that a shot and see if it helps.

                  I need to handle that better. Make sure that if the auth token fails, you get presented with a login screen or something to update the auth. Sorry, figured you had already tried that.

                  Let me know if it works for you!