Still not able to type in the beta app for me. Affecting both meta and the other board I have configured.
Saying this could be an iOS bug seems a little disingenuous given that these problems only started occurring with the new Discourse Hub. The reviews on the App Store seem to indicate many people are affected by the regressions in 1.4.x
FWIW: Crashlytics beta install process is much more clunky/painful than the TestFlight. I had to manually uninstall before I could install the beta? Had to manually copy install link from gmail to paste into Safari. So much friction.
So please, I’m all for fixing bugs, but let’s have constructive discussions here, I’m not trying to avoid anything, just it’s far more complicated than what you seem to think, and it’s iOS world, I can’t fix any issue instantly.
Are you properly authenticated with the app, I saw issues that during the “auth” flow you get a terribly broken SVC instance, can you try removing meta and re-adding it including the full auth flow?
BTW if you can help, any help getting visibility on this will be extra appreciated.
I’m not sure how I could be improperly authenticated? But anyway, I removed my account and added it again (auth in app and on site) and now I see no keyboard at all.
I believe you can, it’s just using the drag and drop API instead of the re-order API which means the three vertical bars to indicate re-ordering are missing.
Agreed, Testflight isn’t perfect, but it follows a familiar UI pattern (notification on parent app) and even if the app isn’t in use the user is notified that a new build is available to test. Discourse app betas totally fell off the map for me when you guys moved from Testflight and even now I’m on Crashlytics I have to open the home screen shortcut or open Discourse to find that there’s a new build.
There also appears to be a slight delay between you pushing new builds and us picking them up, when you told me to pick up 179 I opened Crashlytics and received an earlier version (r174?r175?) which I had missed because of the way it notifies and updates. It wasn’t until a couple of hours later that I came back to the app and received 179.
I’m sure some of this will come with familiarity over time, but are the benefits of Crashlytics so great that it warrants going down that route?
One thing we definitely lose with the Crashlytics approach is the ability to easily hop between App Store and development versions. Testflight builds don’t require an app be uninstalled prior to download, it’s possible to install directly over the top and use the existing settings stored on device. For the ~10 other apps I currently have in Testflight the option to do this is incredibly useful.