I’m developing a command line utility which needs microphone and camera access but in Mojave the permission request is not requested.
I think the problem is due to the fact that for accessing this devices a bundle with an info.plist describing the need for device usage is needed.
Am I missing something or there is an alternative method?
I need to run command line util only on my mac, maybe in the background, no app store or enterprise distribution.
Related
I have installed Desktop App Converter from the Windows store.
When I try to run the app (literally just launch it), I get the message:
[Window Title]
C:\Program Files\WindowsApps\Microsoft.DesktopAppConverter_2.0.2.0_x64__8wekyb3d8bbwe\DACTileLauncher.exe
[Content]
C:\Program Files\WindowsApps\Microsoft.DesktopAppConverter_2.0.2.0_x64__8wekyb3d8bbwe\DACTileLauncher.exe
The data area passed to a system call is too small.
I have tried running the Troubleshooter for Windows Apps, it tells me that "Windows Store cache and licenses may be corrupt" and tries to fix them, but running the troubleshooter a second time gives the same issue.
Each time I try to run the Desktop App Converter, I get 2 errors in Event Viewer:
%1: Cannot create the Desktop AppX container for package %2 because an error was encountered configuring the runtime.
%4: Cannot create the process for package %1 because an error was encountered while configuring runtime. %5
... both from AppModel-runtime
Any ideas how I can troubleshoot from here?
If you have problems with the Microsoft DAC you try this new converter, it is much easier to use, it has a GUI (no command line), built-in support for digital signing and allows you to customize the list of files that get inside your AppX.
Also, you can generate AppX packages for applications which do not (cannot) install silently.
It runs on Windows 7 too, not just Windows 10 (recommended).
I have developed an BB 10 app, It is working well in the simulator.The same app is not working in the device.I want to know , why it is crashing in device.
Is there any way to know the reason for crashing after installing in the device, so that i can fix it.
I have created a log file in the Device Documents
Is there any signal / listener OR try and catch mechanism, to write that exception into the log file?
my bar-descriptor.xml is like this, Please find.
<!-- Request permission to execute native code. Required for native applications. -->
<permission system="true">run_native</permission>
<permission>read_device_identifying_information</permission>
<permission>access_pimdomain_messages</permission>
<permission>access_internet</permission>
<permission system="true">_sys_use_consumer_push</permission>
<permission>access_sms_mms</permission>
<permission>post_notification</permission>
<permission>access_shared</permission>
<permission>bbm_connect</permission>
<env var="LD_LIBRARY_PATH" value="app/native/lib:/usr/lib/qt4/lib"/>
Please help,
Thanks!!!
You haven't given much to go on but here are some things to check right off the bat:
If the application isn't signed, and you don't have a debug token, or the token has expired or development mode has expired on the device the application will exit from the splash screen.
If you aren't requesting all necessary permissions in you app-descriptor.xml file your application may be getting unexpected results that cause the crash.
If you have a higher OS version on the simulator than the device, you may be using QML that isn't recognized by the device QML compiler which will cause a crash when the returned QML document is null. This is usually logged to the console.
If it isn't one of those, use the IDE run the application on the device and see if there is anything useful logged to the console. If not, set the IDE into debug mode to run the program under the debugger on the device. It will halt execution where the application is aborting. This may be deep in a system library but you may be able to step up the call stack to your code to find out the location of the problem.
My application is a cloud based app.Back-end Mysql. middle-ware is Jboss.
I didn't deployed the data into cloud.but i want to run app on device,Does it can access the data base from my pc.
The setting "on device" in Flash Builder run configurations only does one thing: It runs the app on the device you are building for. As in: "Right now, deploy the app to my device, so I can see how it performs when it doesn't have PC hardware to run on".
I haven't deployed to Android, so I don't know for sure what goes on there, but for iOS devices, this means compiling and packaging for LLVM execution and creating a deployable .ipa package.
There are restrictions that apply for iOS: You can't load and run Flash/Flex executable code in SWF format, to name the most important one. But Regardless of what device you are deploying to, a simple compilation setting won't create a local database to replace an external server - how could it, when its setup, characteristics and database schema aren't included anywhere in your code? And it won't disable internet connections.
Since you are probably using the internet to access your enterprise middleware, you should not run into problems. Why don't you just give it a try?
I am new to Qt, and trying to use QtMobility to send message. I am using example in this link:
http://doc.qt.nokia.com/qtmobility/writemessage.html
I am able to compile the source code, and it can be tested on the simulator. But when I deploy it to E72, the program failed. Because it can't found any available accounts. The problem lies in this code:
// Find the list of available accounts and add them to combo box
foreach (const QMessageAccountId &id, manager.queryAccounts()) {
QMessageAccount account(id);
...
}
if (accountDetails.isEmpty()) {
QMessageBox::warning(0, tr("Cannot send"), tr("No accounts are available to send with!"));
QCoreApplication::instance()->quit();
} else {
accountCombo->setCurrentIndex(0);
}
The code enter the (accountDetails.isEmpty()) on the device, but it is okay when at simulator. So the manager.queryAccounts() return an empty list.
What exactly is account? in simulator it is SMS and MMS. But why in the device is empty? The code doesn't initialize the manager so I can't trace how it is work. Oh, btw, manager is a QMessageManager instantiation. What should I do so it is work in the device?
I am using Nokia Qt SDK with QtMobility version 1.0.2, if that's helping.
Okay, I got the answer. The problem isn't with the application or the qt. But the certification. The QMessageManager somehow need to access the OS. It is described at the *.pro file, at the symbian:TARGET.CAPABILITY. That's called capabilities. And some capabilities can't be self-signed which is the default at the Project Setting. It is need to be signed.
I used Open Signed here: https://www.symbiansigned.com/app/page/public/openSignedOnline.do to get the file signed. After the file signed, install the signed file to the device, and the program can access the OS, and the QMessageManager's queryAccounts() won't return an empty result.
that's it. And the message can be sent.
I think it is kind of annoying when I need to test it to the device I need to signed it first. And the offline need a license which is not free, while I am just learning. *sigh
EDITED:
Somehow I am able to run it with self-signed. But I don't know exactly how it can be. What am I doing:
run the self-signed application with QtCreator. error: can't copy from computer to device
restart device
run the self-signed application with QtCreator. error: general OS related
Install application manually with PC Suite. Many warning.
And I forgot what's next
- try run with QtCreator. works fine.
- or uninstall with PC Suite first.
I'm trying to use Adobe AIR 2's NativeProcess API to emulate the ApplicationUpdater but I'm encountering problems when I try to run the downloaded AppUpdater.exe file on computers with UAC (User Account Control) enabled.
When run without UAC enabled, the AppUpdater opens as usual and displays the standard Adobe replace dialog box. With UAC enabled, nothing happens at all.
Having run a few traces, it seems the problem arises when I call NativeProcess.start() - the code seems to stop running at this point, and does not run the following lines which exit the application in preparation for the AppUpdater to run.
I have added listeners for all of the possible events and error events that can be thrown, and added logging in each of them, but none of these are producing any output.
This issue only seems to affect installation executables (ones which windows warns will change settings on your computer). Calling java.exe -jar .... on the same computers in the same application works correctly.
I'm at a loss, so any help would be amazing!
After speaking to Adobe directly, I discovered that NativeProcess uses a windows API which is unable to elevate privileges which is why the installers wouldn't work. The workaround was to use File.openWithDefaultApplication which uses a different API that can elevate privileges, but this only works in a native-packaged AIR app (which was just fine for our app since it was already packaged in a native installer :))
adobe answer was http://kb2.adobe.com/cps/404/kb404888.html
but for real steps you should determine the application user privileges and determine UAC enabled, if yes - then warn end-user about it.
I'm expecting that you could do nothing with windows-thing from Adobe Air.