-
Bug
-
Resolution: Done
-
Low (View bug fix roadmap)
-
8.17.0, 8.5.15, 8.13.7
-
8.05
-
2
-
Severity 3 - Minor
-
25
-
Issue Summary
Some customers need to identify all requests that are made from the Jira Mobile App.
This can be useful for traffic routing policies on the load balancer or for troubleshooting purposes.
The mobile app should send the mobile-app-request: true request header on all requests.
This isn't happening on some of the requests.
Steps to Reproduce
- Install a Jira Software vanilla instance.
- Install the Android Jira Mobile App.
- Access Jira through the Android mobile app.
Expected Results
All requests made from the Jira Mobile App send the mobile-app-request: true request header. AtlassianMobileApp user agent
Actual Results
Some requests are sending the expected request header, some are not.
Here's an example of a request that sends the header.
Here are examples of a requests that doesn't send the header, but can be identified through the user-agent.
Workaround
If you need to identify requests made from the mobile app, rely on the following rules:
- If the request has the mobile-app-request: true request header
OR - If the request is made with one of the following user-agent.
okhttp* AtlassianMobileApp* JIRA* Dalvik*
- relates to
-
JRASERVER-71956 Requesting the Atlassian Mobile applications be built using a Standard browser user agent instead of currently identifying itself as an AtlassianMobileApp user agent which is non-standard.
- Closed
- is related to
-
SHRK-1352 You do not have permission to view this issue
-
[JRASERVER-72568] Some requests made from the Jira mobile app are not sending the mobile-app-request header
As per the investigation outcome - it's not feasible to add `mobile-app-request` header to all in-app requests due to technical limitations related to loading resources in WebView (Login flow).
Indeed the workaround is still relevant (temporary), however it's still involves several conditions to check.
Thus it was decided to keep it simple by introducing only single check to be made on customer side - userAgent.contains("AtlassianMobileApp") - that will allow to indicate all possible in-app requests.
The solution is yet to be implemented in iOS, but it's already available in Android v0.21.
The other options mentioned in the workaround will be deprecated.
DC Mobile team will investigate the issue and will update the status
Done in Jira Data Center/Server 1.32.0