Beta do novo aplicativo móvel iOS disponível para testes

Dev
1

Seguindo Delegated authentication for Discourse Mobile app, temos trabalhado em uma nova versão do aplicativo DiscourseHub para iOS. Esta nova versão inclui várias alterações internas que corrigem alguns problemas de longa data com o aplicativo iOS. Você pode experimentar esta nova versão agora mesmo, abrindo o link abaixo no seu dispositivo iOS e instalando o aplicativo via TestFlight:

https://testflight.apple.com/join/NkdBQgmg

Observações sobre a nova versão

Há duas alterações principais na nova versão do aplicativo:

  1. o aplicativo usa o Safari para autenticação
  2. o SafariViewController foi substituído por um webview

A primeira alteração significa que a autenticação no aplicativo agora é mais fácil e melhor integrada ao iOS. Os usuários poderão aproveitar senhas salvas, sessões SSO existentes ou fazer login por e-mail ao autenticar um site no aplicativo. No entanto, essa alteração também significa que os usuários precisarão fazer login novamente em todos os sites que já configuraram no aplicativo. Isso é uma exigência única. (Se o usuário já estiver logado no Safari, ele só precisará autorizar o acesso da API do aplicativo.)

A segunda alteração, o novo navegador webview, permite uma experiência de interface do usuário melhor e mais rápida no aplicativo e corrige vários problemas que tínhamos com o SafariViewController.

Algumas outras melhorias incluídas nesta versão beta:

  • o tratamento de notificações push foi reforçado: os usuários agora verão indicadores de notificação ao receber uma notificação push enquanto o aplicativo está em primeiro plano
  • as sessões do aplicativo são agora corretamente identificadas como tal no Discourse, na seção “Dispositivos Usados Recentemente” do perfil do usuário
  • no webview, introduzimos uma nova barra de navegação. Em iPhones, essa barra fica na parte inferior e se oculta automaticamente (como a barra de navegação do Safari); em iPads, ela é estática e posicionada no topo da viewport. O estilo da barra usará automaticamente o esquema de cores do tema ativo.
  • o aplicativo agora verificará regularmente alterações na versão da API de um site e no logotipo, garantindo que mudanças na marca e atualizações da API do Discourse sejam refletidas no aplicativo (e isso também corrige um problema com logotipos desaparecendo)

Para testar esses novos recursos, seus sites Discourse devem estar na branch mais recente “tests-passed” ou na última versão beta (v2.3.0.beta9). Quaisquer sites que não foram atualizados recentemente retornarão à autenticação legada e ao SafariViewController no aplicativo.

26 curtidas
2

Awesome work on this @pmusaraj and @sam, major improvements! :tada:

11 curtidas
3

One immediate thing I’ve noticed is that while the new app got straight into Meta after re-authorizing, a bunch of sites on b9+7 needed me to reauthenticate.

1 curtida
4

Odd display issue on xsmax.

The app “back” rendering is cutoff on left side of notch.

2 curtidas
5

Can you paste a screenshot?

1 curtida
6

image
8AD312D4-0710-4F29-BB64-82CD0D4091E8.jpeg1242×621 174 KB

It’s minor, and no issue when displaying normal layout, only when previous app link is displayed

1 curtida
7

I think I see what you mean (but I’m not sure), the button to go back to TestFlight is halfway between the two background colors. In the app, we have added some logic to change the background color behind the status bar in the iOS app. It will follow the background of your Discourse header. For example, here is how the header would look on the Fakebook theme:

image
image.png790×390 61.3 KB

On your site you have a custom header above the Discourse header, with a different background color (blue). I will look to find a way to cover these cases as well, but it might be a tiny bit tricky, there are multiple ways to add a custom header above the Discourse header.

12 curtidas
8

Is there another caveat for preserving credentials beyond beta 9?

9

Credentials from SafariViewController can’t be preserved. SVC runs in an isolated context, the app has no access to any of the sessions/cookies in it. So, this one-time re-authentication is necessary for all users that have no sessions in Safari. I think in your case, you had a Safari session for meta, but not for the other sites in the app.

10

Not sure if this might be fixable or not, but I just tried this and mostly works great but the login / authentication was slightly roundabout for sites w/ SSO using WP Discourse. After logging in through the WordPress site I’m taken back to the forum, but not the authentication page for the app. So I click “cancel”, go back to the app home screen, then click back to the forum and (since I’m now logged in) hit the screen where I can authorize access. Not a big issue but perhaps there’s a way to save a step here.

11

I’ll look into why this is, it should redirect back to the authorization screen. Thanks for the report.

1 curtida
12

Totally unrelated to my previous comment but I also just thought of an idea for a small UX enhancement:

I like the new bottom nav bar (much easier than reaching to the top on a large phone; thanks!) but notice it only appears on scroll up. This makes total sense for the main topic list view where it’s infinite scroll, but for individual topics (where there is an “end of page”) I would suggest also showing the nav bar upon scrolling to page bottom.

See the Pocket iOS app for a great example of this — also a bottom action/nav bar, hidden on scroll down; shows on scroll up or upon reaching the bottom of an article.

I think this makes a lot of sense for my typical Discourse mobile use flow as well; I’m on three forums regularly and (if multiple have updates) typically right after I finish catching up on the last new topic is when I want to close out of that forum view and switch to another.

2 curtidas
13

We have implemented something like this, you need to scroll twice to the bottom of the page for the nav bar to show up again. It’s very similar to what Safari does upon hitting the bottom of a page.

3 curtidas
14

Ah cool I see that now! Did not occur to me to try that, good to know :slight_smile:

3 curtidas
15

If possible, could the icon circled in the screenshot match the icon conventionally used to launch the share sheet on iOS? It being a link is a little ambiguous until you click on it.

Current icon:

image
8FD3D28C-B25C-4E16-B25D-9B9F5872F132.jpeg1125×2436 425 KB

Conventional iOS share sheet icon:
image

5 curtidas
16

I’ve just realised we’ve lost the old refresh button which was previously top-right.

Appreciate that it shouldn’t be necessary, but it’s definitely useful on occasion. Is there any plan to implement pull-to-refresh?

3 curtidas
17

@justin I also find the link icon sub-optimal when it comes to sharing. I chose it because it’s the same icon we use when sharing a post in Discourse. FontAwesome doesn’t have a direct equivalent to the conventional iOS share icon, the closest icons to the conventional iOS icon are share-square and external-link-alt, both of which I’m not particularly fond of. That said, we don’t have to stick to FontAwesome, we could use iOS-style icons for all four of the bottom bar actions…

@Stephen we don’t currently have plans to add a refresh button or to support pull-to-refresh. In fact, pulling from the title bar downwards currently dismisses the webview, which is useful, sometimes.

6 curtidas
18

The app works fine with Meta, but not with my own Discourse instance.
This is what I see in the error log:

Message

Failed to handle exception in exception app middleware : PG::UniqueViolation: ERROR:  duplicate key value violates unique constraint "index_user_api_keys_on_client_id"
DETAIL:  Key (client_id)=(42c39dc...) already exists.
: INSERT INTO "user_api_keys" ("user_id", "client_id", "key", "application_name", "push_url", "created_at", "updated_at", "scopes") VALUES (4, '42c39dc...', '19eaf98...', 'Discourse - iPhone', 'https://api.discourse.org/api/publish_ios', '2019-04-30 15:05:35.056396', '2019-04-30 15:05:35.056396', '{notifications,session_info,one_time_password}') RETURNING "id"
19

I have seen this error on my dev instance (in your case, it’s likely related to an old auth token that hasn’t been removed properly). Have you tried removing the site from the app (swipe right-to-left and then delete) and trying again? Alternately, in your Discourse instance, you can go to your user preferences and “Revoke Access” for the apps you have listed.

2 curtidas
20

I’ve tried both ways unsuccessfully. Although,

I couldn’t find this exact preference. What I did find is Recently Used Devices on my account preferences, where I could log out on my iPhone.

1 curtida