Developers

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
almiki
Channel Surfer

ECP "install" command returning HTTP 401 error now?

Jump to solution

I have an app focused on casting from a mobile device to Roku. On the mobile app, when the user chooses the Roku device, I query the installed apps, and if my app is installed I send the "launch" ECP command; if not installed, I send the "install" command, which used to bring up the store page to install the app.

I don't know when this changed, but "install" no longer works, tested on multiple devices. Now I'm just getting 401 Unauthorized responses. Is this expected behavior now? Can we not launch the install page anymore via ECP? Is there some setting on the Roku device? Or is there any other approach that can let the user avoid having to manually search and install the app?

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
almiki
Channel Surfer

Re: ECP "install" command returning HTTP 401 error now?

Jump to solution

Alright I found my solution. Instead of doing:

/install/<myAppId>

I can do:

/launch/11?contentID=<myAppId>

Where 11 is the ID for the Roku Store app. This works exactly how I remember the /install method working.

View solution in original post

1 REPLY 1
almiki
Channel Surfer

Re: ECP "install" command returning HTTP 401 error now?

Jump to solution

Alright I found my solution. Instead of doing:

/install/<myAppId>

I can do:

/launch/11?contentID=<myAppId>

Where 11 is the ID for the Roku Store app. This works exactly how I remember the /install method working.

Community is Being Upgraded!

We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. Read more here.

Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 19th and you may notice reduced functionality. In the meantime, for additional assistance, visit our Support Site.

We're sorry for this disruption — we’re excited to share what’s next!