That’s very strange, since I haven’t removed anyone and I also can’t see this anywhere in the dashboard.
If you send me your email through a PM, I could check if adding you as tester manually might resolve this (:
That’s very strange, since I haven’t removed anyone and I also can’t see this anywhere in the dashboard.
If you send me your email through a PM, I could check if adding you as tester manually might resolve this (:
Hmm strange, since the build should still be available:
Does the public link not work for you either? I also hope to push a new build this weekend, so perhaps that fixes this issue otherwise 🤞
There is indeed something funky happening with link rendering, I’ll look into it (:
I’m guessing this is indeed related to timezones, I’ll look into it!
I will look into this, since I’m updating this part anyways to incorporate notifications :D
Great find, I’ll look into this! I also noticed that the edit and delete option shows up in one menu, even if it isn’t your own comment. So something funky is happening in those menu’s
Great suggestion, I’ll add that to the list as well!
While using the app myself I ran into a similar “issue” where subscribing to a new community would take quite a few steps. I’ve been playing around with the idea to nest the community menu inside the post menu, which would reduce the amount of steps. I’ve been trying out the following setup:
In parallel I’m working on a bigger update that includes notifications and widgets, so it might take a bit longer to release this update. But hopefully this makes your requested flow to block communities a bit easier (:
Thanks to your suggestion I found a way to disable the predictive text feature in the markdown editor. While this is not the perfect solution, it does at least seem to fix the issue for now.
I’ll keep looking for a better solution, but in the meantime I’ll try to have a new app update ready in the coming week that includes this temporary fix :D
I think it’s a problem related to React Native. The package that I use for the markdown editing is a native iOS package, so I had to write a bridge for the package to be able to use it in my app.
Avelon uses the same package for example, but there it works fine as far as I know. Avelon is however a completely native app, therefor I have the suspicion that the problem is related to the bridge that I wrote.
I already tried to isolate the bridge, to see if any other code in my app is interfering but that didn’t seem to be the case. My plan is to write a dummy application somewhere this week, to see if the package does work out of the box in a native app to make sure that my suspicion is right.
I’m not too familiar with native iOS development though, so that’s why it’s all taking a bit longer.
It is however very helpful to hear that the prediction setting seemed to resolve it in your case. Bit by bit we’ll get closer to fix this 🤞
I think there might’ve been some changes with regards to 2FA and Lemmy v19. I see that feddit.uk is running v19, so I will double check if I need to update my 2FA implementation (: