Forum Discussion
AltocumulusCitrix Storefront with Chromebook Receiver App
EmployeeI believe ChromeOS apps are interpreted javascript via Webkit, so they rely on the browser to do all of the network calls. Since this use case on APM relies (as you've found) on user-agent to figure out if the client is citrix or a browser, it won't work as intended because the citrix app and the browser's requests look the same to the server.
Google has basically deprecated native ChromeOS apps though. I wonder if you could use the Android version, as mentioned in this Citrix blog post from a few years ago:
https://web.archive.org/web/20200408121108/https://www.citrix.com/blogs/2020/01/17/transitioning-to-citrix-workspace-app-for-android-on-chrome-os/
Dusty_CampI didn't get a notification on this response so I apologize about the late reply from me. Interesting to hear that about Google and native ChromeOS apps. I honestly don't understand why we're using the app anyway. It literally looks the exact same as the browser. Same exact experience so what's the point?
What I find really odd is that this all works through a Netscaler just fine. I've reviewed the configs and it's not doing anything differently than me. Identifying the session's client type and then applying rules based on that. The Netscaler basically treats the Chromebook app like a browser. I do that same thing and it doesn't work. The only issue I have left is the 20 minute timeout, which I just realized is happening in a browser as well. Makes sense because I'm treating the ChromeOS app and a browser the same way.
- Dusty_Camp
Also, I think Google must have changed their mind on native ChromeOS apps because this one we're running was released in December of 2023. I wish that weren't the case though!
- Lucas_Thompson
Sounds like it's probably time to make a support ticket. The support engineering teams should be able to characterize the issue.
