I have installed Pepper SDK with Android Studio 2.1.2 but when I launch emulator, it gives error Robot SDK 0.9 is not complete. My Java version is 8 update 131. I have followed the steps perfectly as mentioned in the link https://android.aldebaran.com/doc/installation.html but still it does not work.
There is one more thread on Stack Overflow with the same question (link: Robot SDK 0.9 is not complete. Please download it again or re-create the robot application) but nobody has answered it yet.
Related
I've spent the weekend and have still failed to get a "Hello, World" working.
Visual Studio:
2022 Version 17.0.4
2022 Preview Version 17.1.0 Preview 1.1
uno-check says everything is fine:
Here are my runtimes:
Neither WUX or MUX (UWP or Desktop) flavors of WinUI work. Android emulators coming up but the Hello World not deploying. Local Android device detected, but not deploying. Linux (Skia.GTK) not working.
WASM IS able to display the text "Hello, World".
Wow! I was jazzed after watching every minute of the recent version 4 release conference. But if it is this difficult to just get the thing running ... ?
I'm determined to get it working ... but it appears to be a major unproductive project to do so. Am I the only one in the world having difficulty?
Mark
Ok, I was able to get WinUI (Desktop), WASM, Skia (WPF for Windows 7), Skia (GTK for Linux), and Android working with "Hello, World". Let me share what I learned and hopefully spare others this painful experience I've had.
Of course, before doing the following steps you'll want to install and run unocheck, so follow the documentation to do so and make sure all issues are resolved.
Once you pass unocheck, then:
First, forget about using .NET 6! They aren't ready.
This is what cost me most of my time. Uno 4 may advertise as .NET 6 compatible and they're getting close ... but they are not there yet.
Forget about using project templates within Visual Studio. Amazingly, even after releasing version 4.0 they haven't completed a template for the most important project that developers want: WinUI 3 Desktop. So, for now, just focus on using the CLI to install and invoke templates.
Open the cmd prompt and install templates with the following command:
dotnet new -i Uno.ProjectTemplates.Dotnet
This will install several templates. If you want to create a cross-platform application based on WinUI 3 Desktop (Win32) version, then:
First create the containing folder (like C:\Users\Mark\Code). Then, using the command prompt, navigate to this folder and from within this folder enter the following command:
dotnet new unoapp-winui -o SolutionName
This will produce a .NET 5 solution with a packaged WinUI 3 Desktop as the main development head. The WinUI 3 head will have a dependency on the latest WindowsAppSDK ver. 1.0 (formerly Project Reunion).
DO NOT USE THE COMMAND:
dotnet new unoapp-winui-net6 -o SolutionName
This will produce a .NET 6 solution that will be screwed up and won't work.
Hopefully, they'll have all this corrected in the coming weeks. I would just wait until NVentive releases updated Templates for Visual Studio that support WinUI 3 for .NET 6. Then it will be easy to upgrade your solution from .NET 5 to .NET 6.
When you run the dotnet new unoapp-winui -o SolutionName command, you will notice that several of the projects fail to "restore" properly:
To solve this, use the command prompt to navigate into each of the failed projects and enter the command:
dotnet restore
Now you're ready to use Visual Studio to launch your solution. Select the WinUI 3 Packaging Project as your startup project and attempt to run "Hello, World".
4. You may get this error:
Error MSB3270 There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference ..."
If so, open your build configuration and check whether your packaging and main WinUI 3 project use different CPU targets as shown here (BFRLE is the name of my solution):
I fixed this by changing the target platform of BFRLE.Windows.Desktop to x64 to match the packaging project. While you're in the configuration manager be sure that the Android project is deployed (otherwise it won't deploy during debugging).
Next, make sure that you install the GTK+3 runtime on your computer. you can do so here:
https://github.com/tschoonj/GTK-for-Windows-Runtime-Environment-Installer/releases
The absence of this runtime is NOT checked for in unocheck.
I also installed WSL.
At this point you ought to be able to run "Hello, World" as a local WinUI 3 Desktop app, as an IIS Express-hosted WASM app, as a Skia.WPF.Host app, and as a Skia.Gtk app. I didn't try to run the MacOS or iOS flavors since these require physical hardware. I did try to connect my old Android phone (Galaxy Note 5, OS 7 API 24). To get a phone recognized of course you have to enable Developer Mode and enable USB Debugging (see online docs). To get my phone recognized ... had to disable Fast Deployment. Even after this got my phone communicating, I was not able to successfully deploy to this old phone (I suspect I need to update my phone).
In order to use a virtual Android emulator you need to go to the project properties of the Android project and ENABLE Fast Deployment and Incremental Android Packaging as shown below:
You can accelerate your virtual Android emulator by enabling settings in Windows and your BIOS as explained here:
https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows
The steps above finally got things working for me. It didn't matter whether I was using VS 2022 or VS 2022 preview -- so that's one less thing you have to worry about.
Now on to the more interesting problems of getting a real application to run cross-platform.
Has anyone installed the latest concierge with the RedWeb SDK?
Since installing I can no longer save and have the program automatically compile the code. It will compile and then loops. Normally you save your file and it automatically compiles and responds with the ready and the localhost, etc... I have to kill the terminal session in VSC and restart a terminal session and do ngv run and it will work.
Note: This is the Concierge version released this week. We are developing specifically for RedWeb and not the desktop version which has a different SDK. Just curious if anyone is experience this with SabreRedWeb-SDK-21.5.5
I had issues with that version also. Sabre has just finalized version 21.6 SDK and it should be on the website soon. The newer version worked fine with all my testing so far.
Dotnet core runtime is slow to start on Raspberry Pi 2
Raspberry Pi 2 was set up using the Lite (Raspbian 10, Buster) tar file from Raspbian site.
I installed openssh, php7.1, dotnet runtime and mono. I already have a RabbitMQ server running on a separate linux box.
I am using the Getting Started Example #1 (hello-world) send code found on the RabbitMQ site, https://www.rabbitmq.com/getstarted.html
On my Raspberry Pi 2 I have installed the following
PHP 7.1 for testing the PHP Send code on the CLI
dotnet 2.2 core for testing the C# Send code (as Console App)
mono for testing the C# Send code as Framework 4.7.2 (as Console App)
Added to the example tutorial code I added the Stopwatch so I could measure elapsed time.
The Results are below
dotnet - Elapsed Time = 00:00:07.1991475
mono - Elapsed Time = 00:00:04.3602941
php - Elapsed Time = 00:00:00.1396138
I was under the impression that coding in Dotnet core would be faster than Framework (using mono).
So I thought it could be the RabbitMQ library (NuGet - RabbitMq.Client)
So decided to create two new projects with just the Hello World in the console.write.
The results were very similar.
dotnet - 7 sec
mono - 4 sec
php - 0 sec
I was hoping to write my application in C# but unless I can get the performance issue resolved it looks like PHP is the way to go for my project.
Is there anything I can try to improve the performance?
After a lot of searching I have found similar problems but the articles were old and referred to dotnet core 2.1 in early releases. I kinda hoped that by dotnet core 2.2 release the Arm CPU supported would have been better. Especially with the push on IoT.
The Arm CPU I'm running in my Raspberry Pi 2 is ARMv7 rev 5 (v71).
I tried a Raspberry Pi 1, 2 & 3 and sadly the same results.
Except on a Raspberry Pi 1 you can't install dotnet (not supported on ARMv6 CPU) so only mono and PHP were tested on that.
Any ideas....
To improve startup times there are a few things you can do according to the guidance and my experience.
If possible for your app migrate to dotnetcore3.0, which seems to have significant performance and startup benefits.
Enable TieredCompilation in your csproj. As described here https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#tiered-compilation
<PropertyGroup>
<TieredCompilationQuickJit>true</TieredCompilationQuickJit>
<TieredCompilation>true</TieredCompilation>
</PropertyGroup>
Use ReadyToRun images, by enabling this in your csproj. As described here https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#tiered-compilation
In csproj.
Consider also using the Trimming feature to reduce binary sizes when publishing a single-exe. This reduces the amount of data needed to be read from disk to execute your app.
This issue has been discussed also in context of Amazon Lambda, that cold start times are quite high.
So far it seems the best ways are reducing dll sizes, using ReadyToRun to reduce JIT times and TieredCompilation. These changes have worked for us remarkably, when combined with dotnetcore3.0.
There is some guidance provided by Scott Hanselman here https://www.hanselman.com/blog/MakingATinyNETCore30EntirelySelfcontainedSingleExecutable.aspx
I'm running Xcode 4.1 (4B110) ad trying to upgrade to version 4.2 so I can test stuff on my iOS 5 iPhone and iPad. Trouble is the appstore says it is installed. Clearly it isn't. I've got an old version of 3.2.5 or something like that and this 4.1 version.
Anyone got any ideas. I just spoke to someone at Apple developer hotline who said:
"It might be a problem, I don't know. I can't even get to your details because we have no systems... Try again on Monday!"
So a nice quiet weekend for me unless anyone can help.
Ta.
Rob.
UPDATE:
Suddenly the appstore told me I had one update available... for Xcode 4.2
So now it's almost finished downloading (1.8G) for the second time and still nothing installed.
All installed fine once the download actually happened and downloaded twice for some reason (I think it did that last time as well).
In your application folder, you will find Xcode installer, run this and you will be fine!
Edit: I think it is called "Install xCode"
My further problem was that I already had "Install Xcode.app" (version 4.1.1) in my Applications folder, which prevented me from downloading the version 4.2 from Mac App Store. I deleted my existing Install Xcode.app, then I was able to download Install Xcode.app (ver 4.2), then I was able to update to Xcode 4.2
I created an empty Single View application using Xcode 4.2 on OSX Lion 10.7.2 targeting iPhone 5. The project built happily however when launching the simulator I receive the following error message:
iOS Simulator could not find the SDK. The SDK may need to be reinstalled.
I then tried targeting the iPad with the same results. I removed Xcode using the terminal and downloaded a fresh copy from the AppStore. The clean installation generates the exact same error.
It seems that the SDK is not being deployed during installation. Any advice or tips on how I can correctly install the iOS 5 SDK for the simulator to work?
Update
I downloaded the iOS 4.3 simulator which was not installed. The simulator works perfectly if I select the 4.3 SDK but for some reason is not recognizing the folder containing the 5.0 SDK.
Update
I reformatted the MacBook, reloaded a clean OSX Lion without restoring any backups and installed Xcode. Running the simulator directly after the installed worked, however after a reboot and relaunching Xcode the error came back. The SDK itself seems to have been corrupted. Will try and reinstall Xcode again.
After some testing it turns out the problem is caused by a 3rd Party Software. Recently the developer of TotalFinder removed the Asepsis portion of the system and created a separate application for the handling of DS_Store files.
Unfortunately, this breaks the iOS Simulator once installed, and even after uninstalling Asepsis, I needed to rebuild my whole machine to get rid of the error.
Update
BinaryAge is aware of the issue with regards to Xcode 4.2 and it is now listed on the know issues page and a warning banner displayed on the download link.
Final Update
It seems BinaryAge has changed the way Asepsis works and this is no longer an issue with the latest versions.
Did you try "File -> Reset Content and Settings ..." in the simulator ? I also encountered the similar problem, but it worked after I reset the simulator! In fact, I also found it worked after I removed all the existing projects and created new ones, but it occurred again after I restart xcode. Fortunately the "Reset" always works for me and I hope it can be helpful for your case.