Rise Player Chrome App - New Version available.

  • 4
  • Announcement
  • Updated 3 years ago
  • (Edited)
EDIT MARCH 19, 2018: Please note that all conversations related to Chrome OS in this Community should be considered obsolete and out of date. As announced in our new Community, Rise Vision is adding support for Chrome OS with a new version of Rise Player for Chrome OS.

To receive updates, make sure to subscribe to the Rise Vision Blog, or join the new Community and post questions.


=================================================

Hello Community,

Many of our users have been experiencing crashes on their ChromeOS devices when an update is released to the Rise Player. After some thorough research into the issue, we believe we have found a solution. The downside to this, is that in order to fix the issue, we would have to push another update out to the Rise Player Chrome App, and risk bringing down many of our user displays in the process. As an alternative, we have decided to release a new Rise Player Chrome App instead of an update. This will give all users the opportunity to update players at their own pace, without risking a widespread outage to displays.

The new version is available here

If you have a managed ChromeOS device, the following are instructions on how to upgrade your version.

  • Navigate to http://admin.google.com

  • Click Device management

  • Click Chrome devices

  • Select the organizational that your ChromeOS devices using Rise Player are associated with

  • Click the Settings (three vertical dots) icon on the top right

  • Click Chrome Device settings

  • Scroll down to Kiosk apps and click Manage Kiosk applications

  • Click ‘remove’ beside the current Rise Player

  • In the Chrome web store window, search for the app ID ilcmohdkjfcfekfmpdppgoaaemgdmhaa

  • Click ‘add’.

  • Scroll down to Auto Launch Kiosk app

  • Select ‘Rise Player’ from the dropdown

  • Click save.


Your changes may take up to 24 hours to update.

-

Blake | Community Success

Get the help you need in 10 minutes or less, and let us remotely connect, diagnose and correct display problems with Priority Support!

Book a one-on-one training session with us here.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb

Posted 3 years ago

  • 4
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Hello Blake,
Thanks a lot. I will try.

Specifically for Chrome OS users with a Google managed domain, I would suggest first to test this new extension with a few stations only.

The easy way to do is :
- to create a new child OU inheriting the settings of the current OU used for RiseVision signage.
- in this new child OU, change the Kiosk application to use the new Chrome extension ID (ilcmohdkjfcfekfmpdppgoaaemgdmhaa)
- move one or a few of Chromebox'es from the parent OU to this new child OU
- check how it behaves for some times
- once it is approved and stable, you may change the Kiosk default Chrome extension from the parent OU and finally, move back the stations from the child to the parent one.

This is the way we will manage our release management. By default, we will stop any Chrome OS update in the default production OU's used for RiseVision. Once a new revision will be released, we will test it in specific OU with auto-update that is enabled in which we have only a couple of Chromeboxes. Once it will be validated, we will enabled auto-update temporarily on the production OU's (we will have several simply because of various timezones) one by one. Once all Chromeboxes will be updated, we will disabled again the version auto-update. 
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
We'll test this in our Beta OU before deploying. That said, I'm curious about whether the Display ID will transition over? If we deploy this to our players since it is a new app will each player need to have its Display ID re-entered? Since there's no way to do this remotely in ChromeOS managed devices it requires a human to do it in person on each player. 
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Robert,

You will need to re-enter the Display ID on each media player.
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
Bummer. Looks like we'll have to hold off for a while on deployment. What improvements/fixes does this include? 

Also, as a side thought, has there been any thought given to the idea of automating deployment a bit more? With the Chrome Management platform allowing the inclusion of a file with the deployed app it would, in theory, be possible to upload a file to the management console with a list of device IDs and the corresponding chrome device serial number. This would allow the app to self-ID from the list without the need for user intervention. 
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Robert,

This is simply a change to the way ChromeOS restarts after receiving an update to Rise Player. Keep in mind, if any further updates are released for the Rise Player Chrome App, it will be to this new version.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
I wanted to test today but I've very strange issues. When rebooting, the Chrome Risevison extension stay stuck telling 'Waiting for a network connection'. I've the feeling RiseVision is not the root cause.
Either I've a problem with my Internet connection from the office or, there are some issues at Google today (Nov, 10th 10:48 UTC) which is for me most probable sine some colleagues reports also issues with Drive.
By the way, when I connect interactively on the Chrome box, I may browse the Net but trying to access Chrome Web store, the page stay blank & loading. This might explain my issue if ChromeOS can not download the newest extension (I've just configured it now on a test OU).

Did anybody get some troubles today with Google ?

Best regards.
Thierry

PS. At least nothing reported today by Google (but yesterday there were some issues)
(Edited)
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Blake, can you tell what the version number of this new release must be?
Currently, I'm in trouble and totally puzzled. Once my Chromebox is connected on Ethernet, the extension does not boot "waiting for the network". If I enable Wifi, after having failing to boot on Ethernet, it switches to Wifi (as far as I understand) and it boots.  
I've even reinstalled ChromeOS using a USB memory stick. 
Currently, over Wifi, I've Chrome 45.0.2454.98 and RisePlayerPackagedApp 15.11.6.6958.
Is it the last one?
Yesterday, I've seen a RiseVision logo that is a bit different during the boot time but today, it is the usual one. In the meantime, I've moved the station from one OU to another with the kiosk mode enabled for the old and new version alternatively.
Even if set the OU with Extension=ilcmohdkjfcfekfmpdppgoaaemgdmhaa,  I've the feeling that the previous extension is loaded.
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
The new version (ilcmohdkjfcfekfmpdppgoaaemgdmhaa) reports in the management console as Rise Player 15.11.6.6958

The old version reports in the management console as Rise Player 15.10.7.9312

They also have slightly different icons so you can tell them apart visually, 
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Thanks. Indeed, I was able to get it.
But I stop for today. I'm unable to make it work. I'm lost.
(1) Once I try to boot on Ethernet, the extension does not start but if I <CTRL-ALT-S>, the Ethernet connection sems valid.
(2) If I boot over Wifi, the extension now starts but no that far. I get a message 'Witing for application window'

I'm become mad.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
OK. I've remove the Kiosk application from the test OU, rebooted the Chrome station, wait a bit and set back the new RiseVision extension. After sometimes, the Chromebox rebooted (with new Rise logo) and prompted for a new RiseVision ID. After I introduced the ID, I got the page.
But :
- After a few minutes, the Chromebox rebooted and now, the boot progress tay stuck to :" Waiting for application window". I rebooted several time without any success.
From the RiseVision back-end administration, the Player is in RED .....

- From the RiseVision back-end interface, the listed RisePlayer is Version: RisePlayerPackagedApp 15.11.6.6958 (the same has before). DO you use the same version numbering ? How to check one or the other.

I'm puzzled again. Here after the screenshot made from the Google domain.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Last details. I got the same issues from my company with an army of firewalls that from home.
Maybe something is wrong on that ChromeBox that I've reinstalled from a USB key.
I will try to get another untouched Chromebox to see if it helps.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
OK. Sorry bombing you with mail but it runs now ...
I've once again reinstall ChromeOS using another USB key even if the previous one did not report any isues.
Now :
1- My Ethernet issue is apparently over.
2- My RiseVision client is starting with : Chrome 45.0.2454.98 / RisePlayerPackagedApp 15.11.6.6958
3- Strangely, the Google console reports the ChromeOS in the OU as Unknown ....???

Next challenge is now to reboot to check the behavior.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Reboot is OK.
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
Thierry, we've been slowly deploying Chromeboxes in a managed domain and once or twice have gotten issues similar to yours. I'd strongly advise you to boot the player and let it run on a wired connection for a while before doing anything. Whenever we've gotten the "Waiting for application window" allowing the unit for run for 30-40 minutes and then rebooting has been the solution. Also the Google management console doesn't update instantaneously. Best advise is to be patient with them. They're smart little devices and issues often work themselves out. Software updates don't always push instantaneously either. 
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Hello Robert,
So glad that I'm not mad and someone already met the issue I got ;-)
You're right. I'm not patient enough and indeed, the synchronization of the OU parameters from the cloud to the station is not instantly done.
So, thanks for the rule. Be patient .... (by the way, Windows GPO and Windows DC propagation that work on similar principle are not also that instant as well).

 
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Thierry,

Sorry to hear about the issues you had! It looks to me like they have been resolved now, right? It was an issue with the installation of ChromeOS?
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Hi Blake,
I'm puzzled. I don't know exactly where the problem was coming from but I suspect maybe I did something wrong in the Ethernet TCP/IP network settings because I switched from the enterprise network (static IP address) to my home net (DHCP). I'm wonder if something was not wrong with the DNS servers. 
Anyway indeed,  after having re-install ChromeOS from scratch using a USB key (it is part of my tests as well), all works like a charm at least from home.
Sorry having bring confusion.

Just a last question. So far, what is the recommended Chrome OS version ? Is the new Rise player depending of a ChromeOS version? Is this version mentioned in a particular place in the documentation. It will be a very important information in our internal release management process.
Photo of Danny de Vreede

Danny de Vreede

  • 668 Points 500 badge 2x thumb
Dear Blake, with the choice for a new Chrome app, you have forced me to choose from two unwelcome scenario's: 1) Keep to the "old" app and do not profit from new changes in future 2) Start a huge project to visit to all my locations in order to reenter display id's. Most Chromeboxes are hidden behind large screens, no keyboard attached. Wow, can you imagine I am not very happy? Can you reconsider this choice? Rise' suggested policy was: do not auto update the player. So if you update the "old" player and this gives problems to customers, they have not set their test strategy well? BTW. My players do not have any problems. Thanks in advance Danny
Photo of Amin

Amin

  • 300 Points 250 badge 2x thumb
I agree with you Danny.  I am in the same boat. 
Photo of Dick Fotoples

Dick Fotoples

  • 3,142 Points 3k badge 2x thumb
Blake -

I am following directions and navigating to http://admin.google.com and it is telling me:

You need to use a Google Apps account to log into Google Admin Console. 

I have logged in a number of times and keep getting this error.  What is going on?

Thanks,  Dick
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
Dick if you're not using Chrome Device Management then you won't be able to log in. If you're using Chromeboxes I can't say enough how beneficial it is for the devices to be managed and not just set to Kiosk mode. 
Photo of Dick Fotoples

Dick Fotoples

  • 3,142 Points 3k badge 2x thumb
I don't understand, Robert.  I'm just trying to install the new app.  Is the rise player still in effect?  I get errors when trying to get that installed too.  I am just trying to get a new screen up and running.
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
The instructions provided on this community post are for people using managed Chrome devices. Per Rise Vision's recommendations, the Chrome App player should only be used with managed Chrome devices. If you're using an unmanaged Chrome device then these directions would not apply. Likewise if you're using a non-Chrome device. 
Photo of Dick Fotoples

Dick Fotoples

  • 3,142 Points 3k badge 2x thumb
Thanks for clarifying that.  What recourse do I have to get the player isntalled so I can get this screen going?
Photo of HSuarez

HSuarez

  • 11,896 Points 10k badge 2x thumb
Believe we sorted the above - let us know if you have further questions/feedback
(Edited)
Photo of Curt Grams

Curt Grams

  • 202 Points 100 badge 2x thumb
Do we still need to have admin settings on a managed device, stating that "at most" can run version 44 with this new update? Or can we change that to a newer version? We have Chrome version 46 at this time.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Curt,

It's recommended that you limit your Chrome version to a known stable version. At this time, that is Chrome 44.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
I'm more and more convinced of an issue with Chrome 46 that is behaving totally different from previous OS version at least in our enterprise network that is protected by a IP and application firewall for in/outbound traffic.

I'm still in evaluation for RiseVision and Chrome OS.

Chrome 44 
I've a set of Chromeboxes managed in the Google domain and they are running Chrome 44 and RisePlayerPackagedApp 15.10.7.9312. They work perfectly well.

Chrome 46
I've two chromeboxes in 46 one in the domaine and the other not. Currently, they run Chrome OS Version 46.0.2490.82 (64-bit).

Chrome 46 - RisePlayerPackagedApp 15.10.7.9312
This One is running RisePlayerPackagedApp 15.10.7.9312 and not managed. For some days, it  is unable to boot for some days over our Enterprise firewall. However, it I boot it over a Wifi connection without a firewall, it boots correctly.
Strange stuff as well is that if I connect over the enterprise firewall in interactive mode, I'm unable to access www.youtube.com or even Chrome Web store that stay stuck. Over the Wifi connection and no firewall, no problem at all. I've the feeling that if Chrome Web store is not available, RiseVision could refuse to load because it may not check for new releases.

Strange also is that if I run network diagnostic from Chrome OS (using the Chrome OS Diagnostic extension, I get errors about hangout not getting opened UDP port. I don't know if it is new or not and if such ports might be needed by RiseVision (see here after full report)

Chrome 46 - RisePlayerPackagedApp 15.11.6.6958 (new one)
Here, RiseVision worked sometimes and sudenly did not. I explain why

  1. I re installed Chrome OS from an USB key and attached it in a Google domain with the new RiseVsion extension as the only kiosk application.
    Great, new RiseVsion player started and showned the presentation correctly even if the new video gadget caching the videos.
    I made several reboot, test to unplug the network to check caching was working correctly.
    Fantastic. All works
  2. I did something I should not not.
    I rebooted and logged in interactively to make some checks.
    a) No surprised, Youtube and Chrome Web store not available across our enterprise network with firewalls.
    b) SURPRISE !!!!!!!
    When I rebooted, the older RiseVision extension was loaded .... I've no idea how it is possible.
    I matched it because the logo is a bit different. And guess ... unable to boot with a message 'Waiting for network'. If I stop with CTRL-ALT-S and connects, the network works perfectly well but Youtube and Chrome Web store are unavailable .

    And second surprise ....
    If I reboot using only Wifi, RiseVision now it starts. Note that when looking RiseVision backend 'Client' configuration, the heart beat is in Green and reports RisePlayerPackagedApp 15.11.6.6958 (the new extension).
    So, do I have the new or old extension? For sure, when rebooting, I get the old Rise logo.
    Would it be a cache issue with the image ?

    Not that if I put back the enterprise network instead of Wifi, it does not boot (and I precise that Chrome boxes in version 44 are working well using the same network). 

Conclusion

I'm happy I'm not mad as I though a few days ago. The behavior of the Chrome box since Chrome 46 is very very strange.
  1. Chrome 46, at least on Chrome OS, changes something to the way Youtube and Chrome Web store are reached. Over our enterprise Internet access across firewalls, they are not available while it works perfectly well for Chrome 44 using the some outbound access.
  2.  RisePlayerPackagedApp 15.11.6.6958 appears to work better even over Chrome 46.
    However, if you get the wrong idea to log in interactively on the Chrome box, something strange appears and it sounds like the old extension is then used for ever (not sure, maybe an issue with the boot logo). Anyway, using the enterprise network, no way to boot anylonger while using Wifi (no firewall), it works. 
Sorry for that long post but the behavior is a bit strange. The very last conclusion is that from Chrome 46 something has changed and I'm sure that some new TCP ports or background Web sites are used by Google preventing Rise to work correctly.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
OOps. Coming back to my long story ....

Finally, it appears that Chrome 46 and  RisePlayerPackagedApp 15.11.6.6958 over the enterprise network finally booted up but after 30 minutes staying on the Risevision extension startup page 'Waiting for network connection'. Furthermore, each of the videos played with the new video gadget are coming up very slowly. In comparison, booting using Wifi with no firewall  takes a few seconds and videos are played very rapidly.

I'm totally convinced that something has changed with Chrome 46 and the fact that the boot time is so long comes from new back-end HTTP request or TCP ports that are blocked by our firewall causing terrible timeouts.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Hello,
To be completed, I confirm there is something wrong or changed with Chrome 46.
My colleagues from another department can not get their Chromebox Hangout for Video booting. The behavior is the same. The Chrome extension starts but is hung.
I'm almost sure that Chrome 46  requires new TCP/UDP ports and/or needs to access new Web servers that are not opened on our firewall. Such new ports would be needed to access Chrome Web store in order to check if the Chrome extension does not have a new version.
Photo of Robert Schoneman

Robert Schoneman, Champion

  • 4,990 Points 4k badge 2x thumb
If you're running managed devices, I'd strongly suggest you open a support ticket with Google if you're having such issues. The problems you're having don't appear to have anything to do with Rise Vision. We're running Chrome 46 as a test with the new version of Rise's player and it's been stable. 

The two times we've had issues Google has been VERY supportive both over the phone and in email. 
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
You're right Robert. Issue not linked to RiseVision directly but it took me time to debug it. A ticket is opened both at Google and to our firewall service provider.
The lesson learnt also is that a strong release management policy for the Chrome OS is required.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Community,

I would like to take a moment to encourage your to update to the current version of the Rise Player Chrome App ( ilcmohdkjfcfekfmpdppgoaaemgdmhaa) if you are a user of the Rise Player CAP, and especially if you are a user of ChromeOS.

We are momentarily pushing a fix that will only apply the to current version of the Rise Player Chrome App. Having many Videos presented with the Video Widget is causing presentation crashes, and in some cases ChromeOS devices are shutting down.

Again, this fix will only apply to the newest version of the Rise Player Chrome App. 
Photo of Thierry Masson

Thierry Masson, Champion

  • 2,356 Points 2k badge 2x thumb
Thanks Blake.
I'm currently devoted to another project and less time for signage. I've a station on my desk using  ilcmohdkjfcfekfmpdppgoaaemgdmhaa and 2 others using the previous extension.
So far, all are running fine but I understand it is best to use the new extension.
I will keep you updated.
Thanks for your effort trying to fix the issues.