How do I find the developer ID of my application

For sideloaded applications, the developer id is simply "dev".
You will generate a real (unique) developer id when you run genkey before packaging.

--Mark

Hi Mark,

Thanks for your quick response.

I modified my server configuration to write the value of the "x-roku-reserved-dev-id" HTTP header to the access log. I just had a look and the id is a long alphanumeric string that begins with "34c6fceca...." It doesn't appear to be set to "dev" as you suggest.

To package it, I am using the zip command to create a zip file of my application, going to the development application installer page (in my browser) and uploading the zip file there. I am running my application on a Roku LT (software version 5.1) if that helps.

Any ideas?

Thanks

I believe the dev ID is listed at the top of the Packager page on your Roku. It was generated when you ran genkey.

At the top of the page it says, "Packager (no dev key)". I've never run genkey.

Well then your next step is to telnet to device on port 8080 and run genkey. Be sure to save the resulting output somewhere where you will not lose it.

- Joel

Correction to my earlier posting: for a sideloaded channel, the developer id is the SHA-1 hash of the string "dev", not "dev" itself: "34c6fceca75e456f25e7e99531e2425c6c1de443".

--Mark

Thanks Mark. That's the value I am seeing in the server log. Good to know. I'll run genkey and use that id from now on.

Be aware that just generating a key will not change the "dev" developer id of your sideloaded channel. The generated key is used only if you run a packaged channel, which requires you to upload the package to the Channel Store and install the channel.

--Mark

Mark,
What is the value of genkey that is used in x-roku-reserved-dev-id based on?
Is it unique by device? Or is there some algorithm that would keep the x-roku-reserved-dev-id the same no matter which Roku packaged the channel?

I ask because, we don't want the x-roku-reserved-dev-id changing because of something as simple as our having packaged the channel on a different device (and we didn't know).
Thanks,
Jason

If you have stored your dev password created by Genkey somewhere safe, and a package that was created with that key, you should be able to use those to rekey any device for your dev ID and package on that device, and the dev ID should not change.

If you run GenKey again, that will create a new, different DevID.

- Joel