新的 iOS 移动应用 beta 版本可供测试

Delegated authentication for Discourse Mobile app 之后,我们一直在为 iOS 开发 DiscourseHub 应用的新版本。此新版本包含多项底层改进,修复了 iOS 应用中长期存在的一些问题。您现在即可通过以下链接在 iOS 设备上打开并经由 TestFlight 安装该应用进行试用:

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

新版本说明

新版本应用主要有两项变更:

  1. 应用现在使用 Safari 进行身份验证。
  2. SafariViewController 现已替换为 WebView。

第一项变更意味着应用内的身份验证现在更加简便,并与 iOS 集成得更好。用户在应用内对站点进行身份验证时,现在可以使用已保存的密码、现有的 SSO 会话或通过电子邮件登录。但此变更也意味着用户需要重新登录其在应用中已配置的所有站点。这是一次性要求。(如果用户已在 Safari 中登录,则只需授权应用的 API 访问权限即可。)

第二项变更,即新的 WebView 浏览器,为应用带来了更好、更快速的 UI 体验,并修复了我们在 SafariViewController 方面遇到的若干问题缺陷

此测试版还包含其他几项改进:

  • 推送通知处理得到加强:当应用在后台运行时收到推送通知,用户现在会看到通知角标。
  • 来自应用的会话现在会在 Discourse 用户个人资料中的“最近使用的设备”部分被正确识别为应用会话。
  • 在 WebView 中,我们引入了一个新的导航栏。在 iPhone 上,该栏位于底部并自动隐藏(类似于 Safari 的导航栏);在 iPad 上,该栏为静态并置于视口顶部。该栏的样式将自动使用当前主题的颜色方案。
  • 应用现在会定期检查站点 API 版本和徽标的变更,从而确保品牌更新和 Discourse API 更新能反映在应用中(同时也修复了徽标消失的问题)。

要测试这些新功能,您的 Discourse 站点必须处于最新的 tests-passed 分支或最新的测试版(v2.3.0.beta9)。任何近期未更新的站点将在应用中回退到旧版身份验证和 SafariViewController。

26 个赞

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

11 个赞

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 个赞

Odd display issue on xsmax.

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

2 个赞

Can you paste a screenshot?

1 个赞

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

1 个赞

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:

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 个赞

Is there another caveat for preserving credentials beyond beta 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.

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.

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

1 个赞

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 个赞

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 个赞

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

3 个赞

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:

Conventional iOS share sheet icon:
image

5 个赞

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 个赞

@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 个赞

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"

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 个赞

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 个赞