# New iOS mobile app beta available for testing
**URL:** https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912
**Category:** Development
**Tags:** dev-news
**Created:** [4월 25, 2019, 1:24오전 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912 "2019-04-25T01:24:56Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [4월 30, 2019, 4:10오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/21 "2019-04-30T16:10:55Z")
“Revoke Access” is under Preferences \> Apps (if you have an authenticated app, then you should have an Apps tab).
---
### Author:  [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [4월 30, 2019, 4:20오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/22 "2019-04-30T16:20:12Z")
~~It’s not there. I also don’t have a “Saved Searches” tab, which I see I have here on Meta.~~
Edit: Deleted and re-installed the app. Everything’s working as expected now.
---
### Author:  [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [4월 30, 2019, 4:22오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/23 "2019-04-30T16:22:41Z")
Here‘s another issue. I got this push notification twice.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [4월 30, 2019, 4:39오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/24 "2019-04-30T16:39:52Z")
Cool, glad to see removing/reinstalling app fixes the api key issue.
The double push notification issue in the screenshot is an issue we’ve seen recently, where some PNs (about once every two weeks for me) are sent twice. This is likely because in our PN implementation we retry sending a PN if Apple’s servers don’t return a status code, and that happens sometimes, even for PNs that Apple delivered correctly to the device. Anyhow, it’s not an issue with the current version of the app.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [4월 30, 2019, 5:59오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/25 "2019-04-30T17:59:26Z")
> [@pmusaraj](#):
>
> (about once every two weeks for me)
This happens at least twice a week for me.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [4월 30, 2019, 6:08오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/26 "2019-04-30T18:08:49Z")
Since updating to the new app I’ve seen it three maybe four times. I don’t recall it happening at all on the public version.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 1, 2019, 1:22오전 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/27 "2019-05-01T01:22:06Z")
Do we ship some unique id with PNs that is stable? Then prior to showing the notification we can have the app check if it has seen it before?
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [5월 1, 2019, 1:36오전 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/28 "2019-05-01T01:36:27Z")
The way I understand PNs is as system events: the app doesn’t _see_ them at all, it only sees them if you interact with a PN. One small case when the app can suppress PNs is if it is in the foreground, but this is a small use case (we were suppressing PNs while app was in foreground prior to the beta, for example). When the app is in the background or not running at all, the PN is shown to the user by iOS, with zero interaction with our app.
What we can do instead as a start to tackle this issue of duplicate identical PNs, is add more granular logging to our sending API.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 1, 2019, 1:38오전 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/29 "2019-05-01T01:38:29Z")
Yeah my understanding is that you can send “invisible” PNs to the app that would wake it up, would be a big change to the way we do stuff.
Probably better go down the diagnostics route first, then we can queue extra clean up here maybe for one of the future app releases.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 1, 2019, 4:58오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/30 "2019-05-01T16:58:05Z")
I’m beginning to wonder if what I’ve been experiencing are duplicates at all.
I just received a pair of notifications for the same reply, but the two notifications were different. The respondent had added a line of text _above_ their original message.
Is it possible that we’re not getting duplicates, but instead we’re getting notifications for responses that have been updated?
I can’t rule out that my previous “duplicates” weren’t edits as typically people edit their post to either correct something, or append more text. It’s quite uncommon for the top of the message which gets included in the notification to be edited.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [5월 1, 2019, 5:42오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/31 "2019-05-01T17:42:58Z")
In some cases, they are edits, yes, but I do think that sometimes exact duplicates are sent without edits.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 1, 2019, 6:46오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/32 "2019-05-01T18:46:59Z")
Do edits trigger notifications on the site? Don’t recall seeing a notification for an edit.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [5월 2, 2019, 3:41오전 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/33 "2019-05-02T03:41:27Z")
Sorry for the delay, I was wondering about that question as well and wanted to look into the relevant code before answering.
Edits to a post by its author do not trigger the same _type_ of notification. So you might get a second notification for a post if it is of a different type, for example, userA replies to you, you get a notification of type “reply”, then userA edits the post and mentions you, then you will get notification 2 of type “mention”. This is the case even if the excerpt of the notification is identical in both notifications, we should probably not trigger a notification in this last case (when excerpt is identical).
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 2, 2019, 10:51오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/34 "2019-05-02T22:51:32Z")
Receiving notification for some edits would be more confusing than not getting them at all.
I would prefer edit notification excerpts be prepended with `edited:`, or suppressed entirely.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 3, 2019, 12:27오전 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/35 "2019-05-03T00:27:24Z")
I totally support adding `edited: ` in front of push notifications for edits. But 100% mixed on if this is a push notification class event. Leaning on no … this is not a push notification event.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 3, 2019, 12:30오전 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/36 "2019-05-03T00:30:04Z")
I’m curious to know how many users perceive duplicates once edit notifications go away.
---
### Author:  [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [5월 3, 2019, 1:14오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/37 "2019-05-03T13:14:44Z")
> [@pmusaraj](#):
>
> in the webview, we have introduced a new navigation bar. On iPhones, this bar is at the bottom and auto-hides (like Safari’s nav bar)
I’m afraid this doesn’t cut it for me. On one of the Discourses I use, the bar doesn’t come up at all and I struggled to get back to the overview screen until I accidentally found out that swiping down a lot gets me there.
[https://global.discourse-cdn.com/meta/original/3X/4/c/4c46ba843d017f97cc1c6f7fb198673f5df7abc6.mov](https://global.discourse-cdn.com/meta/original/3X/4/c/4c46ba843d017f97cc1c6f7fb198673f5df7abc6.mov)
However, even when the bar is coming up, it’s not a natural place for me to look for a home button and I don’t find the downward arrow very intuitive.
I wish there was a way to go back with a swipe.
I’d like to suggest to take a look at the podcast app Castro, which I think does a fabulous job with navigation.
[https://global.discourse-cdn.com/meta/original/3X/e/6/e6f4feaeae2514dbd7068384f05ae960a3d18db4.mov](https://global.discourse-cdn.com/meta/original/3X/e/6/e6f4feaeae2514dbd7068384f05ae960a3d18db4.mov)
The sheet sitting at the top would probably be too present and unnecessary when you spend a lot of time on one Discourse. But the right swipe, which has some resistance and then haptic feedback as the ℹ icon lights up, I think would work great if the Discourse app used a 🏠 icon instead.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [5월 3, 2019, 1:25오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/38 "2019-05-03T13:25:39Z")
> [@tomtjes](#):
>
> On one of the Discourses I use, the bar doesn’t come up at all
This is almost certainly because the site isn’t up to date with `tests-passed`. The bottom bar was added to core very recently, so if the site isn’t up to date, it won’t be there.
> [@tomtjes](#):
>
> I wish there was a way to go back with a swipe.
Umm, there is… you stumbled on this, you can swipe down from the title bar to dismiss. It might be a little hidden, but once you figure it out, it’s easy to invoke. Also, horizontal swiping (left/right) triggers back/forward navigation in the webview, I don’t think we should (and I don’t know how we could) add another horizontal gesture to return to the site list.
---
### Author:  [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [5월 3, 2019, 1:59오후 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/39 "2019-05-03T13:59:07Z")
Oh, I hadn’t realized either of those things. I thought swiping right from the homepage of a Discourse would never work, but it does when there is a browsing history.
And even after swiping down to return to the overview I didn’t know that I’d have to hit the title bar. Thanks for clarifying.
What about a more intuitive button in the nav bar? The iOS equivalent would be
> **[Clone Filled Icon (Classic Solid) — Free SVG Download | Font Awesome](https://fontawesome.com/icons/clone?style=regular)**
>
> Download the Clone filled icon as a free SVG or PNG. A bold Classic Solid style icon for web and app projects.
turned 180 degrees, but because the app doesn’t use sheets, maybe a bullet list icon?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5월 4, 2019, 1:40오전 UTC](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912/40 "2019-05-04T01:40:29Z")
🤔
[이전 페이지](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912.md?page=1)
[다음 페이지](https://meta.discourse.org/t/new-ios-mobile-app-beta-available-for-testing/115912.md?page=3)