Problem with Blackberry RIM Signature Tool - blackberry

I have some COD files that I have developed using the Widget toolkit for Visual Studio. These COD files need to be signed before I can use them on a device.
When I open the Signature Tool from within Eclipse (3.4.0) every COD file from the current workspace is shown in the list. If I hit the 'Add' button and select the COD file I want to sign from another location the COD file isn't being listed with all of the other files.
I tried running the Signature Tool from the command line and the same thing happens. I hit Add, select the COD file and then nothing happens. If I specify the COD file on the command line then I get an error saying that the Signature Tool can't find any COD files.
The only exception to this was today, just before I went for lunch. When I clicked Add and selected the COD file it appeared in the list and I could sign it as expected but every other time I've tried it doesn't work.
Any suggestions as to what is happening or any other approaches I can take?

We use the BlackBerry Ant Tools for signing from the command line and it works great. All it does it launch the actual RIM signing tool but it takes care of passing in the correct list of files and (optionally) your signing password - so it can be more or less automated. I haven't encountered problems with it other than the odd time when RIM's signing servers are down.

The issue was that the generated .csl and .cso file was not present in the same directory so the signature tool wasn't aware of which API's needed signed.

Related

Avoid Code Tempring in iOS

What are the different ways available so that We avoid code tempring in ios. Please suggest any good way that we can check at server level to avoid code tempring not in source code. And how we can check that server call from app is from authorize app.
iOS apps are most secured itself. It can not be tempered easily. While building your app no code file and XIB's kept as it is.
You can check it in these steps:
Right click on .ipa file and select Open With and then Archive Utility
Then it will create folder named Payload with .app file in it.
Now Right Click on .app file and select Show Package Contents
This will show you one folder with multiple files in it. Now try to open each file and read it. It will be in encrypted way.
For reference read this link

Error with GetChildNamed("xxxx")

I'm playing with IwUI RSS sdk sample. I made a change of adding a link label to feed page (2nd page). I made this change by copying the description CIwUILabel block and renaming it to say 'linkLabel' and accordingly added that as an element to the CIwUIElement 'Lables' just below Title element. This works fine in x86 marmalade emulator, GCC ARM Debug emulator.
But when I take this to BlackBerry device, it breaks with the error - "Element '' does not have child with name 'linkLabel'. Why it is saying element ''?
Does it mean that my edits in IwUIItems.ui are not getting into device build?
I guess your changes didn't get included in the .bin file. The .group file or .ui file doesn't get included in the GCC build, you need the corresponding .bin file, which you'll get after loading the .group file in x86 simulator.
Just delete the data-ram folder, clean your project, re-run the x86 simulator, make sure UI.group gets loaded before you quit.
optionally you can even delete the VS project folder to get a perfectly clean build. Double clicking on mkb will recreate the project again.
If anybody stumbles on this, please find the details below -
As #Creator said, my changes did not get into the deployment package but the reason it was running fine in the Marmalade simulator does not allow to believe this. The reason was that the changes were getting in the .bin file correctly. But the deploy tool was looking for that file in data folder. There was an old file available and that was getting into my deployment package.
So I have to copy .group.bin file from data-ram\data-gles1 to data folder after running the application in x86 debug mode. Then build the deployment package for BlackBerry 10
For WP8, we have to copy .group.bin file form data-ram\gles2-dx11 to data folder.

How to automatize iPhone app generation?

Ok, we wish to do something along the lines of... this:
Someone enters our site, goes through some forms, registers an account, then a script is executed on the server.
This script will more or less do the following:
Create a folder within the root of our hosting.
Clone a repository which contains a "white-label" iPhone project, with all the code and associated files. The clone will be stored in the aforementioned folder.
Some configuration files will be added to said folder as well (JSON files).
Now, here's the tricky part... We don't know how to approach this:
The script needs to -somehow- be able to automatically generate a fully functioning, valid iPhone app (an .ipa file, I assume, feel free to correct me if I'm wrong) using the files provided in the folder where the repository clone was stored.
Important stuff to take into account:
The app files in the repository do not specify a customized name for the application (the one below the app icon in iPhones...). Instead, it comes with a generic name, which must NOT be present in the app once this "automated app generation process" finishes. Instead, it must use an application name contained in a configuration file (a JSON file, that is).
The "finished app" must have our distribution profile included, and it must be codesigned accordingly.
So basically, we wish to have a server script that ultimately automatizes the process one usually goes through when using Xcode to generate a finished iPhone application. This is because our current business project consists of a white-label app that is "customized" for each one of our clients, and we wish to be as time-effective as possible, avoiding manual processes when we can.
Any ideas? Could this be done? What would be needed?
I have used following terminal command for generating a build for one of my project hope it could be of any help to you
From terminal navigate to the folder where Projectname.xcodeproj file is present and then following command.
xcodebuild -project DummyCam.xcodeproj/ -configuration Release CONFIGURATION_BUILD_DIR="Path to directory where build will be copied" PROVISIONING_PROFILE="${DIST_PROVISONING_PROFILE}"

XCode 4.3.1 breaks validation of apps with directories added by reference. Any workaround?

I've discovered that Xcode 4.3.1 has a serious issue validating apps with resources within a directory tree inside an application bundle.
Apps can pass validation within the Xcode "Build for Archive" process - it only fails when the validation is run via Organizer, which is required to save for ad hoc or App Store submittal.
After spending hours trying to trace down the usual code signing entitlement issues, I eventually noticed the following line in the system console when the export fails:
3/10/12 2:32:48.450 PM [0x0-0x261261].com.apple.dt.Xcode: /Users/chris/Library/Developer/Xcode/Archives/2012-03-10/Coverage 3-10-12 2.32 PM.xcarchive/Products/Applications/Coverage.app/Tiles/T-Mobile-roam/4: Is a directory
The "Tiles" directory has been added to my project via "Create folder reference for any added folders".
I discovered that removing the Tiles directory allows the app to build and validate. Adding it back results in this code sign failure.
It seems that adding a multi-level directory tree completely screws up the validation process, and the error messages send developers on a wild goose chase trying to track down code signing and entitlement issues that really aren't an issue.
I never had any issues with prior releases of Xcode - this seems to be a new serious bug in Xcode 4.3.1.
Is there any workaround possible that will allow us to submit updates to our app?
Notes:
This thread seems related: https://devforums.apple.com/message/630800
This question touches on a similar issue as well:
Xcode 4.3: Codesign operation failed (Check that the identity you selected is valid)
I spent a day trying to isolate this bug, and I've finally nailed it.
The code signer in XCode 4.3.1 when validating for the App Store or saving for AdHoc distribution chokes whenever there is a subdirectory in your bundle that has the same name as its parent directory.
For example:
test/test/file.x -- FAIL
test/test2/file.x -- WORKS
This seems to be new in Xcode 4.3.1, and hopefully will be fixed soon.
UPDATE: I have heard back from Apple DTS support confirming the issue, and indicating that there is no known workaround yet other than renaming the directories in the bundle. ugh
Maybe I've found a workaround:
Open Organizer;
Right click on the archive you want to export and select "Reveal in Finder";
Right click on the xcarchive file and select "Show package content";
Go to Products/Applications;
Create a folder and name it Payload;
Drag the .app file into the folder (don't copy it, since it would invalidate the signing);
Zip the folder;
Rename the .zip file to .ipa
It worked for me.
Let me know if it's ok even for you.
I had the same problem. The solution was to remove files beginning by "._".
Be careful, these files are hidden even when you display hidden files !
In my case, I think that these files were generated by Photoshop.
I had the same problem and solved it like this:
There was a script (under Build Phases) which did try to "clean up" frameworks, by removing seemingly unneeded items, such as the Headers.
However, this destroyed the basic structure of the framework, which probably led to it not being detected properly any more, thus failing the signing or verify operation.
For example, the "Headers" folder and symlink should not be removed, only the *.h files inside the Headers folder!
So, check if your .framework folder contains the basic structure that looks like this:
mylib.framework/
mylib -> symlink to Versions/Current/mylib
Headers -> symlink to Versions/Current/Headers
Resources -> symlink to Versions/Current/Resources
Versions/
A/
Headers/
Resources/
mylib
Current -> symlink to A
We just ran into this where somehow, our .app was getting other .apps built into its bundle. Presumably code signing was choking on the nested app.

How to Upload COD file, RRC files and image files to BlackBerry AppWorld

I am trying to upload a BB app to its App World. Everything I read makes a reference to upload a COD file or some COD files.
When you get to this point when submiting the app, it gives two choices to do the upload. One is file by file and the other is to upload a .ZIP file.
My problem is that when I sign my app, it generates a JAR file where are all my images and classes and .COD files and .CRB files (languages RRC files).
What I do is to convert this JAR to ZIP file and upload the app .ZIP way but it gives me an error because of the name of CRB files that now turns to have some strange characters. They come from a resources_en.rrc to a resources_Ășen.crb
I am doing something wrong but I can't figure it out. What is the right way to do this or what am I doing wrong?
Thanks in advance!
For Eclipse:
The COD is in your workspace\ProjectName\deliverables\Standard\\YourProject.cod
All you need to upload the the App World is this COD file, don't need to do any converting of a JAR. Do, however, make sure you have signed the file by (in Eclipse) right clicking on the project -> BlackBerry -> Sign with Signature Tool
The COD file is produced by RIM's compiler (rapc) and is the file that is signed. If you are using JDE for development it should be in the top level directory of your workspace. I'm not familiar with where Eclipse puts it.

Resources