I imported the PaneManagerDemo sample project in my BB Eclipse workspace, and right-clicked on the project > Load Project(s) on Device. I get a Pane Manager Demo icon on my home screen - OK. It doesn't run, because I'm using a Curve 8330 (OS 4.5.0.138), and some of the classes used in the demo are not supported. How do I delete it from my handheld?
When I run:
javaloader dir
I see:
PaneManagerDemo 0.9 12232 Fri Apr 29 02:57:24 2011
The following commands:
javaloader info PaneManagerDemo
javaloader info PaneManagerDemo.cod
javaloader info PaneManagerDemo.jar
javaloader info PaneManagerDemo.jad
All produce the same output:
Name Version Size Created
--------------------------------------------- --------------- -------- ------------------------
PaneManagerDemo.jar unable to open file
--------------------------------------------- --------------- -------- ------------------------
The Pane Manager Demo app does not appear in my list of installed applications under Options > Advanced Options > Applications.
What can I do to get rid of the install of this demo and the associated home screen shortcut?
Have you tried using javaloader erase option e.g.
javaloader -usb erase -f [moduleName]
where [moduleName] is the name of the module (no extension) you want to delete from the list of installed Modules located at:
Options > Advanced Options > Applications > 'Modules' menu itemorOptions > Device > Application Management > 'Modules' menu item
Run "clean.bat" from the root simulator's installation directory. It will have effect of reinstalling the simulator from zero.
Arhimed's answer is great and will work. This can also be accomplished from within Eclipse: In Debug Configurations, select your simulator debug configuration, then go to the Memory tab and select "Reset the file system on startup" and "Reset NVRAM on startup." Then, next time you debug, the device will be wiped before re-installing your app(s) and debugging.
If you don't want to clean the device every single time you debug, make sure to go back into your Debug Configurations and clear those two checkboxes once you are happy with the state of the simulator.
Related
I am not used to work with kony platform and I have created simple app but I want to export it and run it as native iOS .xcocdeproj.
Kony Visualizer gives you different ways of building and viewing your app, depending on your needs. In Kony Visualizer Enterprise, you can build your app either from the Product menu, or from a command line. And you can view your built app either by previewing it on a mobile device, or by using device emulators and simulators that you configure. Please refer to this docs link to build for iOS using Kony Visualizer.
Please do this below steps.
once Kar file was build. go to your visualizer installation folder and go to plugins and then you can find com.kony.ios_8.2.28.v201811051627.jar file if you are using 8.2.28 version just for example.
Copy above file and rename it as zip file and unzip it.
once unzip was done inside you can find another zip file please unzip. ( ex: 8.2.28.zip)
you can see folder called VMAppWithKonylib.
now go open command-line tool and go to VMAppWithKonylib location.
now go to gen folder location inside your commandline. gen folder will inside VMAppWithKonylib.
7.now run this command - perl extract.pl konyappiphone.KAR
once extract done now go to VMAppWithKonylib and open project in xcode.
let me know if you are facing any more issues.
Hi I want to use camera in my react-native app.
For this I am following this:
https://github.com/react-native-community/react-native-camera
Its is running in Android in Windows Machine, but while am coming to iOS it is not running Mac OS.
The app is installed and loading app name and then it is crashed in iPhone.
Some times its showing an error like react-native-implementation.js: cannot read property 'bindings' of null (null)
For solving this issue, manually added this module to my project like below
Manual install iOS
npm install react-native-camera --save
In XCode, in the project navigator, right click Libraries ➜ Add Files to [your project's name]
Go to node_modules ➜ react-native-camera and add RNCamera.xcodeproj
Expand the RNCamera.xcodeproj ➜ Products folder
In XCode, in the project navigator, select your project.
Add libRNCamera.a to your project's Build Phases ➜ Link Binary With Libraries
Click RNCamera.xcodeproj in the project navigator and go the Build Settings tab.
Make sure 'All' is toggled on (instead of 'Basic').
In the Search Paths section, look for Header Search Paths and make sure it contains both $(SRCROOT)/../../react-native/React and $(SRCROOT)/../../../React - mark both as recursive.
My System configuration:
I am using the PyCharm Editor for implementing my react-native projects.
npm: 6.1.0
react-native-cli: 2.0.1
react-native: 0.56.0
macOS HighSierra 10.13.5
Xcode 9.4.1.
This Bug seems related to upgrading to react-native#0.56.0.
Unfortunately there is no general solution yet. It will probably be fixed in react-native#0.56.1.
You should follow https://github.com/facebook/react-native/issues/20074 and linked issues.
Meanwhile try to use an older version of react-native like 0.55.4.
I have just updated my AIR SDK from version 23 to 25.
When running the command mxmlc, the following error occurs:
Error: Unable to access jarfile /../lib/mxmlc-cli.jar
Solution 1:
Make sure you have downloaded the Flex SDK and not the AIR SDK.
In the download page, there's link specifying:
Flex users will need to download the original AIR SDK without the new compiler.
Solution 2:
When the Adobe AIR SDK is installed it is sometimes installing files with wrong permissions.
The mxmlc-cli.jar file your lib directory probably has a permissions issue.
Try giving this file full permission and making sure it's not read only and everything should work fine.
If you are using Windows, just right click the files and set up the proper permissions in the security tab, and make sure the file is not read only.
If you are using Unix / Linux, run the following:
$ su -
# cd [AIRSDK install directory]
# chmod -R go+rx *
If you are using Mac OS:
Click the mxmlc-cli.jar file or to select it.
From the File menu, select Get Info. One of the windows shown below
appears. Click the disclosure triangle next to Sharing & Permissions
to display the file's permissions.
Click the lock and authenticate with an administrator account. Use
the menus next to users and groups to change the permissions.
This is an old one, but I've faced this problem several times and the fix is really minor.
You have to edit mxmlc or compile.
In the file there is a row which should be changed to:
SCRIPT_HOME=`dirname "$0"`
The error comes from missing " " around the $0.
I have an apk file.
Now i need to fetch package-name as well as launcher activity from apk so that i can install apk and launch app from my test cases.
You can take a look at link
There are multiple ways in which we can obtain the package name of Android .apk file.
Here are the some quick ways to get the package name.
Step 1 : If its public app and available in https://play.google.com/store/apps , then search the app name and click on that particular app. you will get the package name as shown in below screenshot.
Step 2 : Install the app on your device and run the below command to get the list of packages and search for your app.
*(Make sure ADB configured in your path variable, click here to know how to configure adb)
-> adb shell pm list packages
Now the Step 3, where you can get the package name as well as launcher activity name - link
Step 3 : using the aapt command.
To get the aapt.exe , you have to navigate to android sdk folder then build-tools and goto some api version . for example(specific to my machine)
E:\Android\adt\sdk\build-tools\android-4.4W
open command prompt and run the below command
- aapt dump badging
for example : Let's take whatsapp application
- aapt dump badging E:\com.whatsapp.apk
output :
You can get the package name and launchable-activity with other details as highlighted in below :
Android Aapt provides this feature. Use below commands
a)package :
D:\Android\sdk\build-tools\23.0.2>aapt d badging Apk-path\apk-name.apk |grep package
b)launchable-activity:
aapt d badging Apk-path\apk-name.apk |grep launchable-activity
You can also use the following steps:
Connect device to your computer
Open any IDE Android studio or eclipse
Look at the logs of the device
Filter the logs by using your app name
open the app on your device and you would be able to see package name and launcher activity in the logs.
I am using the Jenkins Xcode plugin (https://wiki.jenkins-ci.org/display/JENKINS/Xcode+Plugin) to build an iOS application, however it hangs when running the following command on a project I have inherited from another developer:
$ /usr/bin/xcodebuild -list
It also hangs when I run this command manually from a terminal. Does anyone know what the cause may be? The warning displayed is also displayed on another project I have, but it does not hang in this case.
Running Xcode 6.1 on OS X 10.10
$ /usr/bin/xcodebuild -list
2014-11-12 04:47:21.234 xcodebuild[42642:1431240] [MT] DVTAssertions: Warning in /SourceCache/IDEFrameworks/IDEFrameworks-6604/IDEFoundation/SourceControl/Model/IDESourceControlManager.m:423
Details: Error Domain=com.apple.dt.IDESourceControlErrorDomain Code=-1 "Missing extension: public.vcs.subversion" UserInfo=0x7f9792309200 {NSLocalizedDescription=Missing extension: public.vcs.subversion}
Object: <IDESourceControlManager: 0x7f9792302860>
Method: -loadRepositories
Thread: <NSThread: 0x7f9790d2dbe0>{number = 1, name = main}
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.
Information about project "DOHSmokefree":
Targets:
DOHSmokefree
DOHSmokefreeTests
Build Configurations:
Debug
Release
If no build configuration is specified and -scheme is not passed then "Release" is used.
TLDR; My solution: Mark the schemes as shared in XCode if building them from the command line as a different user, or without ever opening XCode on the build machine.
I was having this same problem, intermittently on our CI server. I came across this question. The accepted answer with the problem being an issue and fixing the SVN version did not work for me as the SVN being used on the CI server was the default SVN and it was, as mentioned, working intermittently.
What I finally noticed is that, between a working version and a non-working version the schemes were not being listed. I had recently upgraded a library on the project and that got me to thinking about the schemes. After realizing that schemes are stored locally per user, unless shared, the fix for me was to go into the scheme manager and mark the schemes as shared.
The problem apparently being that the CI server user never actually opened the project in Xcode, thus causing the list command to hang because there were no available schemes for the user to build.
The times when it had intermittently worked were times after, logged in as the CI server user, I had opened the project in Xcode to test the build process, thus creating the necessary schemes. Wiping the CI server or refactoring/adding schemes would cause the build to break until the project was reopened in Xcode in desperation.
I had a similar issue when updating to Xcode 6.1 while using a newer version of subversion on the command line.
Disabling Source Control in Xcode Preferences should do the trick.
If that isn't an option you might try replacing the subversion implementation inside Xcode as I have done, using this technique: Use SVN 1.7 in XCode 4.3+
Basically that would be the following steps:
This assumes you already have SVN 1.7 installed to /opt/subversion, you can get it from WANdisco: http://www.wandisco.com/subversion/download#osx
Now open the Terminal and get an elevated shell using sudo -s.
Then, cd to inside the XCode.app package, to where the SVN binaries are.
Make a backup directory and move the old SVN files into it
bash-3.2# mkdir bup
bash-3.2# mv svn* bup/
Lastly, symbolically link the new files into the package:
bash-3.2# ln -s /opt/subversion/bin/svn* ./
That’s it!
I have the same problem on OS X 10.10 with XCode 6.4，just close XCode's Source Control to solved this issue:
run XCode
open Menu: XCode -> Preferences...
Click "Source Control" Tab and uncheck "Enable Source Control"