In Flow Diagram 1, we have illustrated all the phases the system undergoes when a user accesses a streaming URL. If the flow diagram is not understandable to you, don’t worry—we've provided a detailed explanation after the Flow Diagram.
Phase 1. Open the streaming URL in your browser
Phase 2. Requesting a slot
Phase 3. Waiting for machine
After securing a slot, system will need to wait for a machine to be allocated to run the app.
If you face any problem in this phase then check [1]
Phase 4. Acquiring App
If the allocated streamer machine already have the app, this step is bypassed. Otherwise, the machine will download the ZIP file from app server.
Phase 5. Preparing App
If the allocated streaming machine already have the app, this step is bypassed. Otherwise, the machine will extract your ZIP file and perform additional setup tasks during this phase.
Phase 6. Launching App
The app is launching for streaming.
Phase 7. Press Play button
If everything is ok you app will be ready to play
If you face any problems in this phase then check [2]
Phase 8. App is streaming
Troubleshooting
1. Stuck in queue issue
If you are consistently stuck in the queue, it is likely due to a network issue or all the machines are assigned to other apps. Please try again after some time.
2. Stuck on the “Starting App” issue
If your app typically streams without issues but sometimes gets stuck on the “Starting App” screen, this could be caused by a temporary network issue.
If your application is stuck on the "Starting App" page and displays a message similar to Figure 10, it likely indicates that the app was uploaded without enabling Pixel Streaming. To resolve this issue, please refer to the Enable Pixel Streaming Plugins Section to enable it.
The error message is “Our record indicates Your this app version don't have pixel streaming plugin enabled. So it can't stream”
After waiting for a short period, a message resembling Figure 11 will appear. To check whether you have enable pixel streaming or not you can go to Pixel Streaming Status Check Locally Section
3. Common causes of streaming failure
(i) The app name does not match the .exe file name inside the uploaded ZIP file.
(ii) The Pixel Streaming Plugin is not enabled.
0 Comments