Your Privacy
We use cookies to give you a better experience in United Robotics Group
You can learn more about what kind of cookies we use, why, and how from our Privacy Policy. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings in our cookie banner to change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer. For more details, check out our Privacy Policy link below.
Strictly Necessary Cookies
These cookies are necessary for the website to function and cannot be switched off in our systems, but do not store any person information. They are usually set in response to your actions that triggers a request for services, such as setting your privacy preferences, logging in or filling forms. You can change your browser settings to alert you about these cookies, but some parts of the Website may not work.
View Cookies
com.intellij.diagnostic.PluginException: ID "com.softbank.robot.sdkplugin.sdk.manager.actions.ShowSdkManagerAction" is already taken by action "Robot SDK Manager (Robot SDK Manager)" (Plugin: Pepper SDK). Action "Robot SDK Manager (Robot SDK Manager)" (Plugin: Pepper SDK) cannot use the same ID [Plugin: com.softbank.robot.sdkplugin]...
2022-09-01 16:08:11 ERROR ActionManagerImpl:220 - JDK: 11.0.12; VM: OpenJDK 64-Bit Server VM; Vendor: Oracle Corporation
2022-09-01 16:08:11 ERROR ActionManagerImpl:223 - OS: Windows 10
2022-09-01 16:08:11 ERROR ActionManagerImpl:229 - Plugin to blame: Pepper SDK version: 1.5.2
2022-09-01 16:08:11 ERROR ActionManagerImpl:237 - Last Action:
2022-09-01 16:08:11 ERROR ActionManagerImpl:213 - ID "com.softbank.robot.sdkplugin.robot.emulator.launch.LaunchEmulatorAction" is already taken by action "Emulator (Launch emulator)" (Plugin: Pepper SDK). Action "Emulator (Launch emulator)" (Plugin: Pepper SDK) cannot use the same ID [Plugin: com.softbank.robot.sdkplugin]
com.intellij.diagnostic.PluginException: ID "com.softbank.robot.sdkplugin.robot.emulator.launch.LaunchEmulatorAction" is already taken by action "Emulator (Launch emulator)" (Plugin: Pepper SDK). Action "Emulator (Launch emulator)" (Plugin: Pepper SDK) cannot use the same ID [Plugin: com.softbank.robot.sdkplugin]
Attachments (1)
rdta.log
74.5 KB
2 Votes
7 Comments
Pierre Nocera posted over 1 year ago
I get the same errors on Ubuntu 22.04 / Android Studio BumbleBee 2021.1.1 patch 3
Is there at least a workaround ? downgrade the Plugin version ?
Couldn't the plugin simply be made opensource so we could fix it by ourselves ?
0 Votes
S. Scholz posted over 1 year ago
Is this problem still not solved yet? I have the same issue under windows 11.
0 Votes
Rbray2 posted almost 2 years ago
Hi Edgar,
Thank you for your reply! Funnily enough, I decided yesterday to do the same thing after seeing this post https://support.unitedrobotics.group/support/discussions/topics/80000657899. It's working pretty well on my Ubuntu 22.04 with minor bugs. Seems like they aren't really working on it, which is weird since it looks like it's been a problem for so long.
Best,
Rob
0 Votes
Edgar.baake posted almost 2 years ago
Hi Rob,
to be fair, I wouldn't be able to tell, but I can't imagine Aldebaran seriously working on this. My workaround eventually consisted of installing a Linux (Mint) partition where the Pepper SDK Emulator works like a charm. In case you're not a Linux guy - some distributions are really easy to handle nowadays and frankly, the hassle with setting up a small partition is negligible in comparison with the time I spent troubleshooting the original issue.
Best,
Edgar
0 Votes
Rbray2 posted about 2 years ago
Hi,
Has this been resolved yet? I have had the same issue for a while now.
Best,
Rob
2 Votes
Edgar.baake posted over 2 years ago
Hello Clement,
I appreciate your quick response, even though it doesn't quite reduce the initial frustration you adequately diagnosed above.
You are correct with your assessment of the situation, however you will understand that using pepper for development purposes is quite a nuisance and a quick emulation of fresh code is much more viable, particularly since working from home is very much en vogue these days.
I would love for Aldebaran to at least hint towards potential error causes. Since this issue does not affect everybody, I suppose there has to be a feasible workaround that does not involve hacking the pepper SDK.
Best,
Edgar
2 Votes
Clement Portales posted over 2 years ago Admin
Hello Edgar,
I understand your frustration, unfortunately there is currently no resources in Aldebaran to work on a fix. It is a known issue however and it will be looked into when time and resources allow it.
However, I understand that you have a Pepper available, would it be possible for you to use the real pepper as a workaround for the emulator problem ?
Best,
Clement
0 Votes
Login or Sign up to post a comment