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.

The screen does not show up in AppStream 2.0

## **Overview** The AppStream 2.0 screen (Windows) does not show up in a browser even after signing into the AppStream's UserPool account. I encountered this bug in us-west-2 a few weeks ago, so I set up a new stack and fleet in us-east-1 to make it work. Today (2022-06-24 PST), my us-west-2's session was expired, so I logged in to the account and encountered the same issue again. From this point, I cannot get into the AppStream's Window screen. ## **Repro steps** I do not know the reproducible steps, but it seems that AppStream is stuck in this situation after session gets expired. 1. Open the link from the AppStream invitation email. 2. Sign in to the AppStream using the UserPool account. 3. The Windows screen does not show up. ##* *Expected behavior:** The application selection page (or the previous session's Windows screen) should appear in a browser. ## **Actual behavior:** The browser shows a plain dark-navy screen (AppStream's background color) and outputs the following errors in the browser console: ``` Error: Template (/appstream/views/directives/notification.html) could not be loaded. TypeError: Cannot read properties of undefined (reading 'ownerDocument') {code: 2, message: 'Display channel is not available.'} ``` **Notes** - OS: macOS Big Sur 11.6.5 - Browsers: Chrome 102.0.5005.115 and Firefox 101.0.1 - Reproducible in an Incognito/Private window. I also removed the cookie/local storage and tried again.
2
answers
0
votes
114
views
asked 5 months ago

Appstream Elastic Fleet - Application Not Launching

I have an application being deployed on the "Microsoft Windows Server 2019 Base" platform as an Elastic Fleet deployment. Unfortunately, the application does not launch, it just gives a black screen. I have confirmed that the VHD, deployment script, and icon file are all accessible to the instance from S3. I did this by launching as a Desktop Stream View and downloading the files via S3 pre-signed URL and the file did download. What is odd, is that when I launch the fleet in Desktop-Stream-View, and then click on "Desktop" it takes me to the Windows desktop and I can see the VHD mounted both on the folder path and as a drive. I can navigate to the executable and launch it. But while in this view, if I click on the "4 boxes" icon on the top-left and try to launch my application from it's AppStream catalog link, nothing happens. After logging out and then back in, while still in Desktop-Stream-View, I then clicked directly on the app's AppStream catalog icon (not the "Desktop" icon). It still takes me to the Windows desktop, but the VHD is not mounted! Naturally, the app link in the "4 boxes" icon to load the Catalog still does not work. Now, when launching the fleet in "App-Stream-View", I only get the AppStream catalog icon, so I click on it and it just loads to a black screen, probably since it did not load the VHD nor set everything up. I cannot understand why I can see the mounted VHD and my application files in one instance but not in the other. And no setup has a working AppStream catalog link. Here are my relevant customizations to the "mount-vhd.ps1" script ``` # Specify a folder path to mount to. When specified, the script will check to see if the folder exists, and is empty, before mounting. If the folder doesn't exist, the folder will be created. If the folder exists, and isn't empty, the folder mounting will fail. $MountFolder = "C:\myApps" # Specify a drive letter to mount to. Specify the colon after specifying the drive letter. Note: A-E are reserved for AppStream 2.0. You will need to choose a different drive letter. $MountDriveLetter = "F:" #If $PathToVHD isn't specified, the script will automatically search for the VHDX file in the same directory to mount. $PathToVHD = "" ``` For the "Application" setup, I have the following: Application executable launch path: C:\myApps\TestApp\TestApp.exe Application working directory: C:\myApps\TestApp\ Any assistance would be greatly appreciated, thank you!
2
answers
0
votes
77
views
m-SS
asked 6 months ago