HKWirelessSDK - Component already exists - audio

When launching my application on my iOS or Android device I get an error message stating that "X" component already exists. What is causing this issue?

Check to make sure you don't have any other instances of any apps with the SDK running in the background. There can only be one instance of the SDK running per device.

Related

Starting the Pepper Robot Emulator/Robot Viewer crashes Android Studio without error message

I installed the Pepper SDK according to the guide (https://qisdk.softbankrobotics.com/sdk/doc/pepper-sdk/ch1_gettingstarted/installation.html) multiple times now, but as i am starting the Robot Emulator for Pepper or trying to connect to the real robot, Android Studio just closes without any error.
I looked into the Windows Event Viewer and it says the problem is located in qi.dll in C:\Users[name]\AppData\Local\Temp\qi.dll.
The last message in the Event Log says
"QI_WRITABLE_PATH=D:\Softbank Robotics\RobotSDK\API 7/naoqi-config/
D:\Softbank Robotics\RobotSDK\API 7\tools/bin/naoqi-bin.exe --qi-listen-url tcp://127.0.0.1:9570" and the emulator loads to 0-17% before closing.
I already tried to reinstall pretty much everything and different versions, but nothing helped.
First, are you running it on a compatible system?
Given that you are on Windows 11, this troubleshooting section might apply to your case:
Connection to a real or virtual robot is impossible and log contains:
java.lang.UnsatisfiedLinkError: C:\Users\[yourUserName]\AppData\Local\Temp\qi.dll
The error may be caused by space character your session name [yourUserName].

Android Pepper Application: E/qi.path.sdklayout: Cannot create directory – Permission denied

Since quite a while, I've been trying to run an Android app for the humanoid robot Pepper on Mac OS 10.13.6. In the past, there occurred many issues when I was trying to run a virtual device in combination with the Pepper Emulator. When I tried to run the emulator with Android SDK version 30 or 29, I was always receiving an error message that there were "NO_CERTIFICATES" to permit the installation of the app. After trying the option to generate a signed bundle in Android Studio, no change was happening.
After downgrading to Android SDK version 23, it was finally possible to run the robot viewer while installing and starting the app on the virtual tablet device without any crash occurring. However the app didn't crash at this point, the following error message appeared in the log histroy:
E/qi.path.sdklayout: Cannot create directory '"/mnt/sdcard/.config/qimessaging"' error was: boost::filesystem::create_directories: Permission denied: "/mnt/sdcard/.config"
E/qi.os: Unable to create file: ''
As soon as I call the robot to execute an animation by clicking a button on the tablet interface, the app crashes and the following lines are printed to the log:
enter image description here
I thought that this error might be implied by the first error message. Therefore I tried to update the AndroidManifest.xml with this permission tag:
enter image description here
Unfortunately, this did not change anything. So I hope to receive some help from your community. Also I would be extremly happy to receive some advice from you, #dfinn. I've read that you got around several issues to run a Pepper application on your Mac, is this correct?
Thanks a lot for all your support!
The error E/qi.path.sdklayout: Cannot create directory – Permission denied has no visible consequence.
The real issue you have here is the one described in the backtrace, java.lang.IllegalStateException: Could not execute method for android:onClick.
It looks like something is wrong with an onClick callback in your Android code.

Xamarin.iOS ApplicationVerificationFailed: Failed to verify code signature of

why I am getting this error when I am trying to run my application in real device not simulator
ApplicationVerificationFailed: Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.ttjwEf/extracted/DSP.IOS.app : 0xe8008016 (The executable was signed with invalid entitlements.)
error MT1006: Could not install the application '/Users/macbookpro/Documents/gitProject/DSPMobileGit/DSP.Mobile/DSP.iOS/DSP.IOS/bin/iPhone/Debug/device-builds/iphone6.2-9.3.5/DSP.IOS.app' on the device 'Mohamed’s iPhone': Your code signing/provisioning profiles are not correctly configured. Probably you have an entitlement not supported by your current provisioning profile, or your device is not part of the current provisioning profile. Please check the iOS Device Log for details (error: 0xe8008016).
here steps I did to run my app
First I created project in Xcode with same bundle name and let Xcode handle Provisioning
when I tried to run in Visual studio it dosent work
Second I create manual provisioning with wild id but it dosent work
I note something each time I set my signing identity and provisioning profile , when I back to screen I find it back to none again
may be that is the reason
Using Visual Studio for Mac 2019
First, determine whether the problem is entitlements. Find tab "Deploying to Device", and look at the full message starting with
"ApplicationVerificationFailed: Failed to verify code signature of ..."
Look for:
... The executable was signed with invalid entitlements.
In that case, see https://stackoverflow.com/a/43055084/199364.
The below answer is for the other likely situation:
... no valid provisioning found for this device.
On newer versions of Visual Studio for Mac + Xamarin iOS (or Xamarin Forms, deploying to iOS):
Connect the phone to Mac via USB cable.
Popup on phone, select "Trust" this computer.
In VS, Open Info.plist.
Make sure the "Application" tab is selected at the bottom of the pane.
Select "Automatic Provisioning".
Follow the instructions.
When successful, you'll see (below "Automatic Provisioning" radio button):
Apple ID: your-apple-id-email
Team: your-company-name-or-your-developer-name
(Green checkmark) Ready to deploy app to connected device.
IMPORTANT:
Even if you have previously setup Automatic Provisioning for a different device, you still need to open Info.plist / Application tab after attaching this new device. (After doing this once per device, you can switch which device is attached, without repeating.)
If Xcode has never seen the device before, it can take MINUTES before Xcode has validated it and attached it. See following paragraph if you'd rather see Xcode giving you a message about what its doing (and spinning a busy indicator). Won't be any faster, but is more obvious that something useful might be happening. (On older Xcodes, people have reported delays up to 10-15 minutes.)
If having trouble getting it to see your phone, google for instructions to open XCode and add your phone as a device known to XCode (XCode menu Windows / Devices and Simulators / Devices tab). That is, it may be easier to first get it working under XCode, then go back to VS, disconnect and reconnect the cable to phone, try instructions above again.
Using Visual Studio (Windows) 2022
Personally, I always FIRST get the phone|tablet recognized using XCode, connecting it to Mac. See instructions above.
Then:
Connect device to PC.
Automatic Provisioning is found in YourApp.iOS / Properties / iOS Bundle Signing.
Select Team.
if it works => "Automatic provisioning completed successfully."
OPTIONAL:
Disconnect device from PC, connect it to Mac - should be listed under "Remote Devices" in VS on Windows.
TBD: Not sure why I failed to get it to be listed as a Local Device, when it was attached to PC.
I had the same issue in a Xamarin.iOS project. I found a workaround. The reason was the update from Xamarin.Swift4 package 4.0.0.1 to 4.0.0.2.
After I downgraded back to 4.0.0.1 the issue no more exist.
I created an issue report at github: https://github.com/Flash3001/Xamarin.SwiftSupport/issues/25

Is there a how to guide for testing livecode?

I have been trying for days to get a simple app any app made in livecode to display either on my tablet, smartphone or emulator. It just doesn't work. Here is what I have done:
I have installed my sdk and pointed livecode to it in preferences.
Picked 2.3 as my version
Check my google usb drivers and they are up to date.
I followed live code's step by step and no success. I am thinking that since I am running windows 7 not a Mac, maybe this cant be done. It seems all the developers run Mac's?
I even tried to make a .apk, It made the file but " There was a problem parsing the package" once I got it on my Galaxy tab. I made sure that I checked the box to allow programs to run on my tablet. So I am still stuck.
To see if the SDK is working correctly you could try to use the Android SDK emulator first.
Open the Android SDK Manager and select the menu Tools->Manage AVDs.
There you can create a virtual Android device and run it.
If the virtual device is running you can see the virtual device under "Development->Test Target in Livecode. Select it and either select "Test" under "Development" or press the "Test" button. Does this work?
That error message means that the operating system on your device is preventing the app from being installed. The most likely reason for this is that you haven't changed the "Allow installation of apps from Unknown Sources" setting on your Galaxy Tab. There are other reasons and solutions for this error message - to see them visit Panagiotis's excellent blog post on the LiveCode website, your error message is in the fifth example
https://livecode.com/how-to-deploy-apps-to-android-devices/

App Crashing while populating data in the database

My app is crashing while populating data in the database with this error message :
Detected an attempt to call a symbol in system libraries
that is not present on the iPhone:usleep$UNIX2003 called
from function -[FMDatabase executeQuery:arguments:]
in image My Project.
If you are encountering this problem running a simulator binary
within gdb, make sure you 'set start-with-shell off' first.
usleep$UNIX2003 is not supported on the iphone
Similar issue - detected an attempt to call a symbol in system libraries that is not present on the iPhone
What I had to do in the end was
completely uninstall the developer
tools from my machine. Then download
the latest versions of xcode & ios
SDK.
Everything works ok now.
Sadly I still don't exactly know what
the problem was but at least things
are running.

Resources