I am using phonegap and sencha touch to build mobile applications. I have successfully built Android and iOS application. When it comes to blackberry application, I am using the procedure given at phonegap docs. http://wiki.phonegap.com/w/page/31930982/Getting-Started-with-PhoneGap-BlackBerry-WebWorks
I can able build and deploy application on to the simulator. But when it comes to code signing it always getting failed.
When I run the command "ant build" the signature tools pops up and closes successfully, I even get 75 emails to my inbox.
Note: I have only sigtool.csk and sigtool.db. Is this the problem?
Any Suggestions?
Well at last I got the solution. If you get a code signing error which does not specify any details, just uninstall and reinstall Java, Blackberry web works and Ripple emulator in the same order. It works for me.
Related
I and my team have a really frustrating problem for weeks now.
Problem in short
The newest version of our flutter app wrapped again by Citrix MDX is not able to continue running beyond its native implemented Splash Screen. It does not crash.
How I got there
I shipped a Flutter app as an IPA file build with Flutter 1.17.5. The file itself can be installed on any iOS device and runs fine. The IPA-file-receiver tried the same and it runs fine too.
The IPA-receiver wraps&signs the app again with his provisioning profile and certificate using Citrix MDX (Version > 20.x). Only the local MDX tool via command-line (not the online) is able to wrap the app. The log file from the MDX tool does not contain any errors.
The wrapped-app can be installed on their iOS devices and run.
Result: The native Splash-Screen is shown and that's it. The app does not continue to show the first Flutter view nor does it crash or close itself.
Unfortunately, we have no OS logs from the running app and also we don't have the wrapped-app from the MDX tool.
What makes me wonder: ...is that the wrapped app from MDX works on iOS tablets after changing its orientation this will somehow trigger Flutter to load its first view.
What we already did
try-catch'ed the main-Method and provided a Flutter-Screen with some Error-Output capability. Result: The error screen showed that some plugin we are using via pubspec was missing. However, the MDX tool logs showed that the plugin was there. Worth mentioning: The error screen did not showed up in our latest test, the app was just somehow freezing in its native Splash-Screen again.
Searching for any changes since the last release that was running fine.
Is there anyone who has some idea worth trying out or some hint where you would start searching for the problem?
Help is much appreciated and sorry for not having some re-produceable steps.
I am working on Mobile app automation in VSTS using xamarin. Code was successfully executed on the local emulator, but while pushing to the appcenter from command line i am facing error Test Chunking failed.
I tried with admin privileges also, still i face issue can i know the solution.
Are there any further information? At the moment it sounds like the same problem that appeared at the official Xamarin forums.
https://forums.xamarin.com/discussion/68616/test-chunking-failed-format-of-the-executable-exe-or-library-dll-is-invalid
For me, what did the trick was to change the target framework of the Xamarin UI tests project to .Net Framework v4.6.1 (net461).
I have installed Blackberry on Windows7. I got all three .csi files from BB. I have done all the procedures and got a successful response from there. Then i right clicked my project and clicked on "sign with signature tool". After signing i loaded this project on Blackberry Bold Device.
Now My Device Shows the installed icon on screen but when i try to open this project it says that "attempts to access a secure api." how to resolve this problem.
For resolving this problem i have also Disabled my UAC. I am working on eclipse Helios.I installed Blackberry Plugin with this exe file. "BlackBerry_JDE_PluginFull_1.5.0_helios" is there a problem with this setup.
I am not able to launch a simple helloworld application on Device. I have tried all the help from internet but still i have not succeeded. plz help to resolve this critical issue.
You need to sign your application. Contact RIM for signing keys. Install them and sign your app before installing on actual device.
Check this link to obtain signing keys: https://www.blackberry.com/SignedKeys/
I have checked other questions around but no one seems to have exactly the same error. I'm using phonegap+jqm to create an application, initially tested on my android phone, now i'm trying to build-deploy to a blackberry. To build the app i used the phonegap starting guide, with:
ant blackberry load-device
I DID sign the application with the RIM provided keys. Still getting the error. Some help?
The problem was with the Signing Tool + JAVA SDK 1.7: it is a known issue that these two dont get along well.
Download and install the BlackBerry Signature Tool and run your compiled .cod file through it to check whether it is really signed or not.
I am new to that Blackberry development platform.
I installed eclipse plugin for blackberry successfully.
Now when creating the project its showing no jre click configure jre when clicked and configure and select whenever option its shows the same error then I go to that update site and install the sdk but after downloading its shows error like
An error occurred while collecting items to be installed
session context was:(profile=SDKProfile..
Please help me create my first BB app here.
Can't send more logs because I have 9 reputation and require 10 reputation for adding hyperlinks
Well, try this out
Remove BlackBerry plugin from Eclipse, shut eclipse down.
Next go to BlackBerry developer website (register, its free I think), get the correct SDK your handset has, install it.
Add the home directory of this SDK to your path.
Now launch Eclipse, go get the BlackBerry plugin and install it. Now try creating a BlackBerry project, it should work.
If it doesnt, try running one of the sample apps that get shipped with the SDK in Eclipse, say the "Hello World" app. If it works, modify it for your project.