app_home_opened not firing on iOS client
Closed this issue · 15 comments
Reproducible in:
Slack iOS client 24.01.50 (437812)
The Slack SDK version
3.17
Node.js runtime version
v20.11.0
OS info
ProductName: macOS
ProductVersion: 12.3.1
BuildVersion: 21E258
Darwin Kernel Version 21.4.0: Fri Mar 18 00:46:32 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T6000
Steps to reproduce:
Access the app home on the Slack iOS client
Expected result:
The app_home_opened event is fired and sent to the app backend
Actual result:
No event is received by the app backend
Requirements
In most (but not all) cases, the app_home_opened is not being fired when a user enters the app home from mobile. The event is fired consistently when accessing the app home from the desktop client. This behavior was first reported on Jan 30 and has been consistent since then. No app deployments on our end had occurred in the days leading up to Jan 30 which suggests that this is a regression on Slack's end. The difference in behavior between mobile and desktop clients further suggests that this is a Slack client issue.
A solution to this issue would result in app_home_opened events being sent to the app backend consistently across both desktop and mobile clients.
By using which mobile client are you able to reproduce this, and what would you say the occurrence/frequency of this is? Just trying to gather data to see how to go about reproducing this problem.
I am using the OSX mobile client. The issue occurs 100% of the time when I enter the app home by clicking the app icon on the main sidebar.
Noting that this issue does not seem to affect all workspaces. In another workspace where the app is installed, this issue is not occurring even on mobile. So it occurs consistently on affected workspaces, but not all workspaces are affected.
Thanks for the info! Do you have any clues as to the differences between the two workspaces? Is one an enterprise workspace while the other a standalone workspace? Perhaps one has certain admin settings enabled that the other doesn't?
Another question: is your app OAuth enabled, and thus is distributable publicly to any workspace?
It's a great question! One is a pro workspace and the other is free, which might be the issue. But the fact that everything works fine on the desktop client for both workspaces makes me think it's not a configuration issue.
Yes, the app is oauth enabled, you can install it here. Noting that the issue seems to affect two of my apps in identical ways, which is another data point suggesting it's a mobile client issue.
OK great, that's helpful. I'll set up some test workspaces on my side and see if I can reproduce the behaviour. Me and our entire team is traveling today so I won't be able to take a stab at this until Monday, FYI.
Following up, I'm having more users reporting this issue. They are on a pro workspace.
Hi @kronosapiens - That is unusual behavior. Thanks for your patience and for giving all this helpful detail to @filmaj and I. He's going to be headed out of office soon, so I'm taking over this issue. 🙇
Based on what you've provided above, we've been able to reproduce this issue below:
With the Chores app installed on a Pro slack workspace, the App Home loads properly in both desktop and mobile (android) clients, but not when accessing the same app from the Slack OSX mobile client.
So weird! I agree that it doesn't appear to be related to your app's configuration, usage of the bolt-js SDK, how you're using the app_home_event.
The best thing I can do from here now is to escalate this to an internal team responsible for the Events API, and to see what they think could be the issue. I'm also going to assign this issue to myself in the meantime and will get back to you if we're able to find out more on why this might be happening on the mobile client.
Separately, I would recommend that you report this issue to the general slack customer help page with details on your App ID, the behavior you're seeing here. The Slack customer experience team is much better at aggregating similar reports and joining in on escalations from there.
Please reference that you've also reported this issue to developer experience us via the Slack SDKs site.
Hey Guys, I'm also having the exact same issue. The app_home_opened event triggers fine on my desktop (windows) but not on my iPhone app.
It was working previously (maybe last week I cant recall specifically), so I think a recent change has caused this issue.
Node version 18.16.1 and @slack/web-api version ^6.11.2
Please let me know when there is more information.
Cheers.
Thanks for adding to the thread @NickSig! I'm starting to see our internal Customer Experience agents also picking up feedback around this, so I'm hoping we'll have a root cause / resolution soon.
@kronosapiens @NickSig - Can I confirm that you can still consistently reproduce this issue when meeting the requirements for the latest minimum mobile client versions? https://slack.com/help/articles/115002037526-System-requirements-for-using-Slack
Hi, I am using iOS 17.2.1 and the Slack mobile client 24.02.10, which meets your minimum requirements.
I have this same issue, I am seeing app_home_opened fired on desktop but not on mobile. I am using the same workspace on mobile and desktop. iOS 17.3.1 and slack mobile client 24.02.20
@kronosapiens - Thank you, internal teams have able to reproduce with latest minimum required mobile clients, but unfortunately, reproduction has been inconsistent internally (some folks can load your Chores app home and others can't the behavior can also be seen in other apps) which we're trying to get to the bottom of.
This is clearly a server-side issue at this point, so I will just be updating as internal teams do more investigation.
HI @kronosapiens , @carlypecora , @NickSig, can you retry to see whether the behavior in iOS has been fixed? We rolled out a fix.
Seems like it's working. What was the underlying issue?
@kronosapiens - The mobile team rolled out a new feature that changed the behavior around fetching and checking the contents of the app home tab. It appeared more likely to impact the first time view of an app vs subsequent views, but I was seeing it pretty consistently, I don't know :P 🤷♀️
Glad this resolved the issue for you and thanks to all for also reporting via the main help form. It absolutely helped us get this server-side issue to resolution faster. I'm going to close this issue now.