Questions tagged with Amazon AppStream

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Appstream 2.0 Mac Microphone Crashes Appstream Connection and does not Work

We have been serving our application (which requires user microphone input) on appstream 2.0 for roughly a year now with few issues. However, at the beginning of November, Mac users began reporting microphone input had stopped functioning in appstream. Our build of our application and our setup in appstream has not changed. Upon testing, we discovered the following issues on Mac (Chrome and Firefox): In both imagebuilder and normal appstream access via user setup- **After enabling microphone(via settings in upper left), the input seems to be registered in Windows sound settings for a moment, then stops showing. Then the VM or Streaming performance rapidly degrades (laggier and laggier input) until finally the instance freezes. Eventually the screen shows the connecting swirl with "Reconnecting to your session…", and after a few seconds the Appstream instance re-appears *with top left Microphone disabled* and the Appstream functioning as normal.** This has been tested across 5 Macs running the latest Apple update. Our image/imagebuilder is running with the following specs: * Microsoft Windows Server 2019 Base * AppStream 2.0 agent version 10-13-2022 * Graphics design XL instance type We also tested a ‘general purpose XL’ instance type imagebuilder and received the same results. Is anyone having similar issues/does anyone know of a fix? Is this a known bug due to an apple update or otherwise?
0
answers
0
votes
8
views
Avi
asked 2 days ago

How users can reconnect to an active AppStream session

Case Embedded: User connects to SPA and requests a new embedded AppStream session. This session is embedded as IFrame or as in the [AWS sample example](https://clients.amazonappstream.com/embed.html) in a container. Initially, a request to Streaming URL is sent, then after authentication the URL changes to the URL I called Active Session URL in the example below. That's where the AppStream session is actually streamed at. If a user closes down the browser and wishes to come back to his active session (within Disconnect Timeout) - we cannot send a new `create streaming url` request because this will lead to an attempt to open a new instance of our app that's already running on this session and crashes it. It's essential to allow the app to be kept running - this case assumes that the user has a work in progress and wants to return to it. ![reconnect](/media/postImages/original/IMTgOY0_oOTmW_A7vwm1PA3Q) Case Redirect to AppStream: Testing shows that if a user is instead redirected to that Streaming URL the URL changes to *Active Session URL*, but at this point, the user has left SPA which isn't the desired outcome. Redirecting to the Streaming URL and connecting to the session within AppStream gives us access to parameters created by AppStream in `localstorage` such as `sessionid`, something that's not available while embedding. **How can we get that user's *active session URL*?** Neither iFrame nor the sample container contains that URL. **Is there a way to store that URL used in iframe?** And then use it to reconnect to the same session without passing a request to start one more app instance?
0
answers
0
votes
9
views
asked 14 days ago