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.
Related
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].
I am trying to load the SDK for Vuzix through the SDK manager in Android Studio but for some reason it will not display the downloads in 'SDK platforms' and 'SDK tools'.
In the 'SDK update sites' tab next to the Vuzix link I added there is a red exclamation point that displays " cvc-elt.1.a cannot find the declaration of element 'sdk: sdk-addon' " when hovered over.
I am new to SDK's and have no idea what to do for this error. I've downloaded the android SDK's and sources for 26,25,24, and 23 thinking it could help but the error still shows up.
I still don't know what the error means but I solved it by connecting to my hotspot instead of my work network.
So my guess is it was a firewall issue or something, if anyone else has this error.
This means that the parser does not know the namespace. I tried it on Win7 and android studio 2.3.3 with the same result.
I tried it without the namespace or running android studio with oracle sdk. Both failed.
At the moment I try to run it on a virtual linux machine. Android Studio 2.3.3 will parse the addon xml file and download the files.
On Win7 I installed them manually, but they were not really integrated into to system and I stucked when I wanted to use the barcode SDK. maybe I am able some day to add simply this jar lib -
On a first look using linux seems to be the solution. But than I run into problems with the case sensitve file system. The vuzix SDK seems to need a linux system on a case insensitve file system.
*facepalm* and I am quite sure that i will fail at all. On linux a simple GUI compiles only against API 26 without errors.
I have universal project targeting Windows Store 8.1 and Windows Phone 8.1 platform.
The windows one works fine but I having trouble running the WP one on an emulator. I get the error message saying:
Microsoft Visual Studio Unable to activate Windows Store app
'numbers-here!App'. The Kiss.WindowsPhone.exe process started, but the
activation request failed with error 'Msg in polish that the app did
not start'.
If this was Windows I would check System Event Log and see the logs just before the error what DLL the system was trying to load and that helped a lot when I was debugging similar problem with Windows Store project, here I have no clue on how to check what exactly was being loaded.
The worst part is that I created package (appx) and checked the dll's being packed with exe, it seems that it includes dependencies that the app explicility uses yet something is still missing and this might be some 'hidden' dependency of one of the other dlls.
Any ideas how to debug such issues with emulator?
For me it was due to having WIC code in my App and/or calling CoCreateInstance in a windows phone environment ( on PC it works flawlessly though )
I ran into the same problem on Windows 10. Turns out, that there is no Kernel32.dll on Windows 10 phone!
Instead you need to link against OneCore.lib which provides the entire Win32 API subset that is supported in UWP. This "umbrella library" will load the correct dlls at runtime.
See also:
https://msdn.microsoft.com/en-us/library/windows/desktop/mt683763(v=vs.85).aspx
I am developing an iPad application with Xamarin.iOS and MVVMcross. So I have a PCL with my View-Model and my Model, and an iOS project with the view. I use Visual Studio.
Before, I used Xamarin.iOS 6.3.6 beta version, and when I tried to launch the app on the device, an .app file was created and getting it with my Ipad, I could launch the application (impossible to launch directly from Visual Studio).
Yesterday, I uploaded Xamarin.iOS to 6.4.1. On simulator, everything's okay. When I try to launch the application on device, now the app is directly installed but the build stop and the following error appear in the debug output :
Failed to load AOT module '<my PCL>' while running in aot-only mode: doesn't match assembly.
And if I click on my app icon on the device,a black screen appear and disappear immediately.
Does someone know why this error appear?
This looks like something was cached somewhere or not updated correctly.
Here are a few ideas to try:
Delete the app from the device.
Clean & Rebuild your app.
Build & install from Xamarin Studio on your Mac.
Copy the Debug configuration to a new configuration (DebugTest for instance), and run that configuration instead.
I regularly get the same issue here.
The workaround that I use is to switch the platform in the Visual Studio build Configuration Manager to "iPhoneSimulator", run a quick debug session on that, then switch the platform back to "iPhone", and the problem disappears for a while.
Unfortunately I have no intelligent reason as to why this works. It seems to be doing a better job of the "Clean and Rebuild".
After reading a similar bug, I found that clearing the mtbs folder on the OS X host which is located at $HOME/Library/Caches/Xamarin/mtbs/ fixes this problem for me.
I have to do it so frequently I just have a PuTTY session open on my Windows box to clear the folder. I do hope that Xamarin fixes this issue soon.
Make sure Linker Behaviour is set to Don't Link
Clean, rebuild, remove old version from app.
Worked for me at least.
This happened to me after I upgraded to XCode 5/iOS7. I noticed a warning that I hadn't installed XCode Command Line Tools. After I did that I rebuilt the application and it now runs.
I just had this problem and got it to work again by opening the Apple project properties and changing the provisioning profile identity from "Distribution" to "Developer".
My workaround on Mac is to
Close Solution in XS
Quit XS. Command-Q
Reopen it and reopen solution.
After that it usually works again.
I have a WPF 4.0 application that I have compiled for x86. When running on 64bit Win7, I need to start up an on-screen keyboard, located in %windows%/System32/osk.exe. Problem is I can't do it- I get an error 'Could not start On-Screen Keyboard'.
I found this thread:
Unable to launch onscreen keyboard (osk.exe) from a 32-bit process on Win7 x64 which sounds exactly like my problem.
I used all the relevant bits from that post, but the error persists. And even worse, I managed to get a 32 bit version of osk.exe and when I try to start THAT I just get a blank error box- no message at all, just a red 'X'.
So I can't compile my app for AnyCPU (3rd party interop libs), and have read that that might not solve the issue anyways. I have also read that one workaround is to disable virtualization using Wow64DisableWow64FsRedirection, but that this is unsafe. Seems like a lot of effort just to run a little app :(
What can I do to launch this little thing from my app?
Wrapping the offending app in a exe compiled with AnyCPU works fine and seems to be the least painful approach.