Hi All,
I was trying to install brightscript plugin on my mac. But once i create a project, and try to Run (Export), its showing me error:
[upload|cp5n7xQ3h4vQeqdFMgF81w==]
http://snag.gy/Vx4pf.jpg
Error in setting developer mode credentials
Either the username or the password is not valid
Reason: The developer password must not be null when creating an authentication class instance.
I downloaded eclipse from https://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/lunar
I also tried Eclipse IDE for Java developers https://www.eclipse.org/downloads/packages/eclipse-ide-java-developers/lunar
I am seeing the same error. I don’t see any place in the project settings to enter a dev password.
I think it’s the password and id of your development box
I recall that I had to reset it for one of my
Eclipse installations. In the export wizard you
Should see the username
On windows I dont remember getting any error like this. But now, I am not able to proceed to the export page bcz of this error. I know we can give dev id and password in Brightscript deployment wizard, and in this case due to this error I cant get there.
Is there somewhere else (like an xml file) where I can specify the dev id and password, from where the brightscript plugin and pull when it run for the first time?
I tried re-installing different versions of eclipse as documented. No luck!
I also faced the same issue on both windows and Mac platform with newly released Eclipse plugin.
I had to revert to previous installation.
How to revert to old plugin? I mean, when I install new software, and give the plugin url, doesnt it always install the latest version?
I had the whole zip package ( including Eclipse and Plugin ) backed up with prev installation. I deleted the new one on facing errors and reverted back to old one.
I think Roku should verify the issue being reported here and revert back to old BrightScript plugin meanwhile.
Alternatively you can use makefile to sideload the channel as described in the section 7.3 of this link
http://sdkdocs.roku.com/display/sdkdoc/Developer+Guide#DeveloperGuide-72ApplicationInstallerPage
You guys need to talk to malloys about that. Or forsake over-complications and go rogue, eclipse-free.
“EnTerr” wrote:
You guys need to talk to malloys about that. Or forsake over-complications and go rogue, eclipse-free.
He was or still is on vacation. Started out with eclipse from the beginning
Always used An IDE. Can’t even imagine coding the 2D API without it
Just too code intensive. Everything I need including graphics, my own Libs
XML, JSON , audio, video, editors are accessible through it right in the
Project manager. When I want to move to
Fire tv dev I just change perspectives. Until something better comes along
It is well worth the the minor bugs that can be worked out. However,
Releasing the 6/27 plugin without any info was probably not the best
Idea. It is a little more buggy but has some nice features
Hey guys,
I’m on vacation, but will be back and checking into this and other issues on Thursday.
In the meantime, it’s possible to rollback to the previous eclipse configuration (and therefore the previous plugin version) - just google “eclipse rollback update” and you’ll find various explanations on how to do so.
I just reinstalled the plugin and was able to successfully connect to my Roku and deploy a channel. I wonder if the developer password on the box you are deploying to has changed. If so, you should be prompted to enter the new password in the Deployment wizards screen. What happens if you change the developer password on the Roku and try again?
Thanks for your reply Malloys and RokuRob
I did try resetting the password however it still didn’t work.Also I was able to connect Application Installer using the same password.
I will give it a try one more time
Confirmed this a bug in the new plugin version (tracked back to a somewhat recent code refactoring that allowed support for a new feature - semi-silent deployment from a toolbar button or keystroke sequence).
The bug will only show itself if you’ve never run the export wizard before for the current instance of eclipse. Instances that have previously sucessfully run the export wizard at least once, should not experience this bug - hence RokuRob’s previous comment.
I’ve got a fix, and am just awaiting approval to do the check-in (once that’s done the same approver should be able to publish the new version of the plugin fairly quickly).
This fix is now live on our server.
Thank you Malloys, Joel, EnTerr and NewManLiving.
Seems like its fixed. Marking this discussion as solved.
