Submitted a channel update, wrong channel was published.

ghostbust... my bad, call developer@roku.com

Most unusual. The channel# is 143924.
Per web store, vanity code=IPCAMVIEWBASIC, name="IP Camera Viewer - Basic", version=2.1
When installed though, it identifies itself as "IP Camera Viewer Pro", version="1.112.0"
In the latter case i think it takes these from the manifest, the former is from the dev.portal.

There seem to be some buglets around "easy add". What's the "highest" Roku you tested that on - Roku2, Roku3?
Also, it doesn't say there to which URL to go (i presume the Roku one but port 7000 aint it)

"EnTerr" wrote:

There seem to be some buglets around "easy add". What's the "highest" Roku you tested that on - Roku2, Roku3?
Also, it doesn't say there to which URL to go (i presume the Roku one but port 7000 aint it)

The "easy add" bug is fixed in my code and will be pushed with next update. The problem was that I was getting the Roku IP from eth0, so it won't show the IP:port if the Roku is connected over Wifi. I do the tests on a Roku 3 and a Roku Ultra. The port is 12345.

"ioan" wrote:
The "easy add" bug is fixed in my code and will be pushed with next update. The problem was that I was getting the Roku IP from eth0, so it won't show the IP:port if the Roku is connected over Wifi.

This should do it (arguably) right:

IPs = createObject("roDeviceInfo").getIpAddrs()
if IPs.count() > 0 then ip = IPs.items()[0].value else ip = invalid

I do the tests on a Roku 3 and a Roku Ultra. The port is 12345.

Try "easy add" on the Ultra in 1080p mode, i think the image will overlap the text. Let me guess, you have manifested something like "ui_resolutions=hd,fhd"? The quickest fix would be to un-manifest ui_resolutions or changing that to "ui_resolutions=hd".

On a stylistic note, seems to me better would be if in the edit screen there are no separate "* Edit blah" buttons next to the fields but instead the cursor walks the fields directly and pressing OK atop one goes into entry edit screen.

On a personal note, i tried the app with a D-link DCS-5010L and it didn't work, even as access on that is as easy as http://<IP>:80/image.jpg (i left the MJPEG and PTZ links empty). Could Dlink's use of http basic authentication be the issue here?

PS. oh, and one more thing - the notification "Apologogies... | We found a bug in the previous version fo the application... " is annoying. Why does it keep showing up over and over again? I'd expect this to be a one-time thing (how - e.g. make a note in the registry it's not the first launch)

"ioan" wrote:
The problem was that I was getting the Roku IP from eth0, so it won't show the IP:port if the Roku is connected over Wifi.

To get the Roku's IP address used by the connection (whether wireless or wired), do this:

ipAddress = CreateObject("roDeviceInfo").GetConnectionInfo().ip

"ioan" wrote:
On Monday I submitted updates to IP Camera Viewer Basic and Pro. Today they were published but now both Basic and Pro channel install the Pro channel. I downloaded the packages from the developer console to make sure I didn't submit same one by mistake, and I did not. The package submitted to update the Basic channel contains the Basic channel and the Pro ... the Pro. I wonder how did this happen... Who should I contact to fix the problem?

Thanks.

Make sure that in your manifest file, the title for the pro channel includes "Pro", and for the basic channel includes "Basic".

Make sure that each time you submit a new package to the channel store (pro or basic), you increase the *_version fields in the manifest file appropriately.

Make sure that when you submit a new package build with the Developer Dashboard, the Channel Version on the Package Upload page matches the manifest file's major_version and minor_version.

Make sure that you always sign your submitted packages with the same developer key.

Make sure you keep the developer key, especially the password, somewhere safe where you'll never lose or forget it, as you can't recover a lost password.

"EnTerr" wrote:

Try "easy add" on the Ultra in 1080p mode, i think the image will overlap the text. Let me guess, you have manifested something like "ui_resolutions=hd,fhd"? The quickest fix would be to un-manifest ui_resolutions or changing that to "ui_resolutions=hd".

I tried "ui_resolutions=hd,fhd", "ui_resolutions=hd" and "ui_resolutions=fhd". All look fine. I'm recalculating the position and size for all elements to look good on any resolution. I know that the image for "easy add" in HD doesn't fit on the screen... I was too lazy to fix it 🙂 Let me know if you saw a problem where the text overlaps, because I can't reproduce it.

"EnTerr" wrote:

On a stylistic note, seems to me better would be if in the edit screen there are no separate "* Edit blah" buttons next to the fields but instead the cursor walks the fields directly and pressing OK atop one goes into entry edit screen.

Can I focus on a Text field? I didn't know I could do that...

"EnTerr" wrote:

On a personal note, i tried the app with a D-link DCS-5010L and it didn't work, even as access on that is as easy as http://<IP>:80/image.jpg (i left the MJPEG and PTZ links empty). Could Dlink's use of http basic authentication be the issue here?

Yes, the problem probably is with the basic authentication. Probably D-Link cameras sends back a "realm" attribute that my application doesn't handle yet. I have the algorithm to handle the "realm" attribute working on the PC, I just have to port it to BS.

"EnTerr" wrote:

PS. oh, and one more thing - the notification "Apologogies... | We found a bug in the previous version fo the application... " is annoying. Why does it keep showing up over and over again? I'd expect this to be a one-time thing (how - e.g. make a note in the registry it's not the first launch)

Yeah, I agree, it should have been a flag in the registry that the message was showed once.
Anyway, it shows in the beginning only if you don't have any cameras added. As soon as you add a camera (aka really use the application) the message goes away. I'll get rid of the message in the next update.

By the way, is there a limit on how often I can submit updates to my channels?

"belltown" wrote:

ipAddress = CreateObject("roDeviceInfo").GetConnectionInfo().ip

I was using something along the lines of what EnTerr posted but this is the more elegant. Thank you.

"belltown" wrote:

Make sure that when you submit a new package build with the Developer Dashboard, the Channel Version on the Package Upload page matches the manifest file's major_version and minor_version.

I didn't know they have to match. I'll make sure from now on to match the package version with the Package Upload page version.

"belltown" wrote:

Make sure that you always sign your submitted packages with the same developer key.

Make sure you keep the developer key, especially the password, somewhere safe where you'll never lose or forget it, as you can't recover a lost password.

Yeap, I learned this one the hard way.

"ioan" wrote:

"belltown" wrote:

Make sure that when you submit a new package build with the Developer Dashboard, the Channel Version on the Package Upload page matches the manifest file's major_version and minor_version.

I didn't know they have to match. I'll make sure from now on to match the package version with the Package Upload page version.

That is stated here: https://github.com/rokudev/docs/blob/master/publish/channel-store/publishing.md#update-an-existing-channel:

Be sure to increment the channel’s major, minor, and build versions in the manifest as well as the Channel Version on this page for each new package submitted.

"ioan" wrote:
I tried "ui_resolutions=hd,fhd", "ui_resolutions=hd" and "ui_resolutions=fhd". All look fine. I'm recalculating the position and size for all elements to look good on any resolution. I know that the image for "easy add" in HD doesn't fit on the screen... I was too lazy to fix it 🙂 Let me know if you saw a problem where the text overlaps, because I can't reproduce it.

The value you should use for ui_resolutions should represent the canvas size that your code is drawing to. It has nothing whatsoever to do with what resolution it will run on. So, if your code assumes a canvas size of 1280x720, then use: ui_resolutions=hd. However, if your code computes sizes and coordinates automatically based on the values of ifDeviceInfo.GetUIResolution() then it may not matter what value you use.

If you have a specific image that is a particular size, assuming it was made to fit within a specific screen canvas size, then you may find it helpful to specify the associated ui_resolutions value (otherwise you'd have to specify multiple image sizes).

When your code runs on any device that is NOT listed in your ui_resolutions list, then the UI will scale AUTOMATICALLY for that device. This automatic scaling ONLY happens for a resolution you do NOT specify. If you specify fhd,hd for example, and you draw a 640x360 image that was designed to take up half the width and height on an HD canvas, the image will render correctly on the hd device (because it was sized for a resolution you specified), will also render somewhat okay on an SD device (because it will be automatically scaled, since you didn't specify sd), but will NOT render correctly on the FHD device (because it won't automatically scale if you specified fhd and it's running on an FHD device -- so you'd either need a separate image sized for FHD dimensions, or only specify ui_resolutions=hd).