Hi friends I am new to blackberry10 development. I am developing an application using HTML 5. I can run the application in Ripple Emulator. And with this i have created the bar file. But how can I install this application into my device. When I try this with command promt it show error as
Info: Sending request: Install and Launch
Info: Action: Install and Launch
Info: File size: 1118370
Info: Installing sampleapp.testRel_sampleapp__42572c37...
Info: Processing 1118370 bytes
actual_dname::
actual_id::
actual_version::
result::failure 881 required signatures missing (RDK, AUTHOR)
I suppose you already have the signing keys set up, because you have the Dev Alpha.
Create a debug token with
blackberry-debugtokenrequest -storepass *yourkeypass* -devicepin *yourpin* d:\*yourfile*.bar
upload it to the device with
blackberry-deploy -installDebugToken d:\*yourfile*.bar -device *yourdeviceip* -password *yourdevicepass*
After this, place yourfile.bar in the main sdk folder, together with bbwp, and rename it as debugtoken.bar
Enable remote web debugging and now it works!
I went through the same issues when I wrote my first WebWorks app. Followed all the instructions in the guides and still had the same problem. Looked like the app is not deployed /launched in a debug mode.
So here is my solution:
Under the Ripple, on the right-hand side, there is the "Build" tab (or toolbox) - choose "Settings". A dialog will pop-up. There check the check-box "Enable Remote Web Inspector" and close the dialog.
Now just hit the "Package & Launch" button.
Should work.
Related
I've developed SOL, an open-source macOS launcher.
Inside of SOL, I added the ability to run AppleScript commands, one of these commands allows me to lock the computer:
{
iconImage: Assets.LockIcon,
name: 'Lock',
type: ItemType.CONFIGURATION,
callback: () => {
solNative.executeAppleScript(
`tell application "System Events" to keystroke "q" using {control down, command down}`,
)
},
},
I have also added the correct entitlements for the hardened runtime (it is distributed only via DeveloperID and not via app store, so hardened runtime is the only capability needed)
<key>com.apple.security.temporary-exception.apple-events</key>
<array>
<string>com.apple.systemevents</string>
<string>com.apple.systempreferences</string>
</array>
The problem is: when I run the app via XCode it works fine, but once the app is packaged and distributed via DeveloperID signed binary, then the lock AppleScript stops working.
Looking at System Preferences I can see the app is still registered and has automation access:
Why does the script stop working? If I remove the permission and re-add it then it starts working again. Does it have to do with the binary? Or is there some permission model I am missing? I had a similar problem with folder access with a different app, so could it be something similar (a security feature I'm not aware of?)
EDIT 1:
Looking through the console.app logs there is also no error message.
EDIT 2:
I just managed to reproduce the issue while attached to XCode and log the output of calling the AppleScript:
Optional({
NSAppleScriptErrorAppName = "System Events";
NSAppleScriptErrorBriefMessage = "Sol is not allowed to send keystrokes.";
NSAppleScriptErrorMessage = "System Events got an error: Sol is not allowed to send keystrokes.";
NSAppleScriptErrorNumber = 1002;
NSAppleScriptErrorRange = "NSRange: {36, 48}";
})
But the app does have accessibility permissions but this still happens? 🥴
EDIT 3:
I just tried removing the app from the accessibility panel and re-adding it, and now the script works again. I killed the app and started it again, and it still works. So my guess right now, is that it has something to do with the binary. Maybe if I replace it with a new version then the accessibility setting doesn't work anymore?
After much gathering at hints all over the internet, I've come to the conclusion that the problem lies in having different binaries.
It makes sense that macOS does some binary check to make sure the application has not been swaped. I had therefore two binaries in my machine a "release" one, which was DeveloperID signed. And the XCode debug one, which uses a development certificate. So both are different and therefore do not pass the binary check.
The brute force solution is not to have a release version installed in my machine. Another solution would be to have the debug binary have a different bundle ID (com.ospfranco.sol), so that macOS allows both the release binary and the debug binary to have accessibility access.
Hello and thanks for helping me solve my problem! I ask for an easier way, as I am trying to figure it out without success in this tutorial https://developer.android.com/guide/app-bundle. So far, I only worked with the Google Play Console itself, did not create an application in a third-party service. I first tried to download the Android App Bundle using Android Studio as described in this article https://medium.com/androiddevelopers/building-your-first-app-bundle-bbcd228bf631, but the first step describes pressing buttons that are not on Android Studio Panel "In Android Studio, select“ Build => Generate Signed Bundle / APK ”and follow the dialog." I do not see the options I need in the Android Studio panel (I attach a screenshot)enter image description here
, where do I need to click to create an Android App Bundle? Then I tried to create the Android App Bundle from this tutorial using the command line https://developer.android.com/studio/build/building-cmdline, I installed Grable manually as described in this tutorial https://docs.gradle.org/current/userguide/installation.html#installation unpacked and configured the system environment, as well as installed and unpacked JDK 17 for Windows/x64 (also on disk C but in a different non-Grable folder), but verifying the Grable installation when typing gradle -v in Windows PowerShell throws an error, and these instructions https://docs.gradle.org/current/userguide/troubleshooting.html#sec:troubleshooting_installation does not offer a solution what is displayed in my Windows PowerShell enter image description here
(The sentence highlighted in red from the screenshot in English looks like this "grable: The name grable is not recognized as the name of a cmdlet, function, script file or executable program. Check the spelling of the name, as well as the presence and correctness of the path, and then try again."), and when I enter gradle -v into the command line, it says "Grable is not an internal or external command, an executable program or a batch file.", I face the same problem if I enter into command line ./gradlew bundleRelease as suggested in this tutorial https://medium.com/androiddevelopers/building-your-first-app-bundle-bbcd228bf631. I'm stumped, what am I doing wrong, and what method is easier for me to create an Android App Bundle? Thanks again for the help in solving my problem and I apologize in advance if I have provided little information necessary to solve my problem.
I'm trying to install SOAP on server. This is what I did:
Got into WHM Module Installers
Installed SOAP 0.13.0
Confirmed it was there; looked in FTP and I see the SOAP directory created
Restarted server Added phpinfo on server and went to it on browser
Also added extension = php_soap.so on php settings Didn't see SOAP on phpinfo
Am I missing something?
Thanks,
Problem solved. After installing the application on module installers in WHM, need to go to EasyApache and add SOAP in the exhaustive list and build it.
In addition to the answer submitted by #kakenx , follow the steps to enable extension with EasyApache
Login to WHM control panel
Select EasyApache from left nav
On EasyApache, click on the gear icon on default profile under Previously Saved Config section.
Add SOAP extension in Exhaustive Options List.
Click Save and Build
Click Recompile and wait for the compilation process
After done with everything, restart Apache
Reference Link
What #saiid mentioned worked 100% been looking and doing SUDO's for over 2 hours turns out its just a whm easyapche setting...
just in 2022 its
whm -> easyapche4 -> Currently Installed Packages (Click customize)
-> PHP Extensions (search soap)
enable both php74-php-soap & php80-php-soap
next then follow steps to provision.
boom bobs your uncle works like a charm. |
Edit
no restard required can if you using woocommerce youll notice its enabled under status
This is the error I am getting after starting SDK manager and also while updating or downloading packages(Download interrupted: Unknown Host dl-ssl.google.com). My ADT is also updated to Build: v22.6.2-1085508. I have read all the post regarding this and tried
Using https instead of http while using Help>install new software (getting error could not find https://dl-ssl.google.com/android/eclipse/)
No proxy.
Run SDK with admin privilege.
No firewall blocking .
I am not able to post the image because I am a new user , so i m copying the error and posting it , please don't mind .
This is type of error with many links like this ..
Failed to fetch URL https://dl-ssl.google.com/android/repository/sys-img/android-wear/android-wear-sys-img.xml, reason: IO Unknown Host dl-ssl.google.com
Done loading packages.
Also I have read many answers on this site and other but nothing has helped so far.
Please help me .
Thank you
This might be because of Android SDK Manager not being able to connect to Google server. This article helped me a lot:
Tools > Options... and check Force https://... sources to be fetched using http://...
Just wanted to add how I solved this problem if anyone comes here looking for an answer.
Comodo firewall runs in background even if you disable the firewall and that causes problem with SDK . I had the same problem.
Steps I took to resolve my problem:
run comodo settings
defense+
list active processes
add adb.exe to trusted processes
restart server: run "adb kill-server" "adb start-server"
For Comodo 6.x
Open Comodo
Click Tasks Icon at right top
Click Advanced Tasks
Click Open Advanced Settings
Select Security Settings --> File Rating --> Trusted files from left panel
Click on the upward arrow icon at the bottom
I was also getting same error : Unknown Host Errors while installing ADT plugin in eclipse
Go to Setting -> Default setting -> select "Android SDK" from left side Panel. Select required components Which you want to install. - >Apply -> Ok.
Please let me know if still you are facing issue.
Regard,
Pappu.
I tried working the Hello World application and the emulator freezes after it flashes the Android start screen. The home page is not shown. The last display on the console is
Waiting for HOME ('android.process.acore') to be launched...
I tried reinstalling Eclipse and Android again. It still did not work. Also the console does not show any errors. The log cat has the following errors:
06-18 20:39:11.543: ERROR/flash_image(544): can't find recovery partition
06-18 20:39:11.843: ERROR/vold(538): Error opening switch name path '/sys/class/switch/test2' (No such file or directory)
06-18 20:39:11.843: ERROR/vold(538): Error bootstrapping switch '/sys/class/switch/test2' (m)
06-18 20:39:11.843: ERROR/vold(538): Error opening switch name path '/sys/class/switch/test' (No such file or directory)
06-18 20:39:11.843: ERROR/vold(538): Error bootstrapping switch '/sys/class/switch/test' (m)
06-18 20:46:31.842: ERROR/MemoryHeapBase(578): error opening /dev/pmem: No such file or directory
06-18 20:46:31.892: ERROR/SurfaceFlinger(578): Couldn't open /sys/power/wait_for_fb_sleep or /sys/power/wait_for_fb_wake
06-18 20:46:32.313: ERROR/GLLogger(578): couldn't load library (Cannot find library)
06-18 20:46:33.634: ERROR/GLLogger(578): couldn't load library (Cannot find library)
The solution which worked for me is, when you get the message:
Waiting for HOME ('android.process.acore') to be launched...
Wait for few seconds and then right click on the project and click run as Android application once again.
I faced the same problem. However, it worked after i went to Project->Clean...
Don't know why it happened though.
Hope this helps
I get this problem all the time and have lost many hours of potential productivity and education while I try to fix it. The only thing that works for me is the combination of three other good answers:
Project -> Clean
Delete all the AVDs and create new ones
If an attempt to run still hangs too long on 'Waiting for HOME' (over two minutes) or the emulator keeps rebooting every minute or so, try Run as Android App several times, choosing the same existing emulator instance (I always choose runs manually).
It's odd that no one has a clue why this problem comes up, what causes it or what is going on internally. The only clue I can supply is that DDMS shows a few lines like "Class not found for preloading: libcore.base.CollectionUtils" during the 'Waiting for HOME' pause.
What worked for me was to delete the AVD from the AVD manager and create a new one. Then go to
Run >Run Configurations, select the target tab and choose the new AVD.
Following steps worked for me:
1. Goto Project -> Clean.
2. Delete your previous AVD and create a new one.
This problem occurs because while creating the AVD manager in the "Create new Android virtual device(AVD)" dialog window ,"Snapshot" was marked as "Enabled" by me.
Solution:
Create a new AVD manager with the "Enabled" checkbox not checked and then try running the project with the newly created AVD manager as "Target" , the problem will not occur anymore
I solved this issue by creating a new virtual device and launching it from the AVD manager. The device takes a few minutes to start, you just have to wait. Then you can run your application on the already started device.
Options:
Click on the HOME Button on the Emulator. Wait for may be 2
seconds....
This always works for me!!!
or
Go with Shreya's suggestion (one with most suggestions and edited by
Gray).
I had only 12 Mb for the SD Card in the AVD device.
Increasing it to 2 Gb solved the issue.
SOLUTION:
Run the emulator from the command line:
sdk/tools> ./emulator-x86 -avd <DeviceName> -partition-size 1024 -gpu on
Then I launched the app from the command line as well (using built-in Cordova/PhoneGap tools):
myapp/cordova> ./run
BACKGROUND
I believe this is some sort of hardware compatibility issue. I came across this problem when following the PhoneGap 2.4.0 Getting Started Instructions. I followed their advice to install the Intel Hardware Accelerated Execution Manager, and I think this is the source of my trouble. Eclipse uses the emulator64-x86 program (in the sdk/tools folder) to launch the emulator. I could not find any way inside of Eclipse to change this but I found by following the "Tips & Tricks" section of the Intel HAXM web page that I could get the emulator to run successfully from the command line by using the emulator-x86 program instead. I'm not sure why the emulator64-x86 program doesn't work on my system. I confirmed at the Apple website that I do have a 64-bit processor.
My system:
OSX 10.6.8
2x2.26 GHx Quad-core Intel Xeon
6 GB RAM
ADT v21.1.0-569685
Eclipse 3.8.0
My AVD:
Device: Nexus One
Target: Android 4.2.2 - API Level 17
CPU: Intel Atom (x86)
RAM: 512
Internal Storage: 256
SD Card: 128
I created a new device. Deleted the previous one.
None of these solutions worked for me. Instead, what worked was to go to a command line tool (or terminal in Mac), CD into the SDK/platform-tools directory, and then run this:
adb kill-server
then run this:
adb start-server
After I did this everything worked again. Why? Who knows.
On my MAC the path to the platform-tools folder was $HOME/Installations/adt-bundle-mac-x86_64-20130522/sdk/platform-tools
It will probably be somewhere else on your machine.
I also found this page that presents some helpful steps:
http://android.okhelp.cz/android-emulator-wont-run-application-started-from-eclipse/
What worked for me was enabling the checkbox "Use Host GPU" when creating or editing the AVD (Android Virtual Device). This checkbox was not enabled by default.
It worked for me when I selected 'Use Host GPU' option under 'Emulation Options:'.
You can find the option under Edit window of the virtual device.
I increased the virtual device SD card size from 500MB to 2GiB, the problem solved.
Following steps worked for me: 1. Goto Project -> Clean. 2. Delete your previous AVD and create a new one.
I noticed this is an old post. However I just ran into the same problem and found a solution. A) Make sure you have the CPU/ABI is atom
B)Ram is 2048
C)VM Heap is 256
D)Internal Storage is 200
E)Make sure to check the Use Host GPU
F)Device is Nexus 5 (My personal choice)
G)Android 4.4.2 API Level 19