i am Android developer, i just started to learn about Blackberry Application Development. i want to ask you something about Application and Signing keys.
I have downloaded 3 signed keys (*.csi) files. and i have installed it and added in first demo application to run app on real device. it is working and running fine in real device.
now i have created second demo application, it is also working well in simulator. but when i am trying to launch it in real device. it is loaded/installed successfully but when i am tapping on icon or trying to open application. it is not opening/running on device.
in second project, i tried by right click on project > Blackberry > Sign With Signature Tool. but it is signing only two files while in my first demo application it is signing 3 files.
also it is not generating .csl file in second application.
Please help me.. Thanks in Advance..
Ajay, will you describe your exect problem actually no of signing the file depends how many .cod file are there in your build ( You can check it by rename your .cod file and change its extension by zip and then extract it)
for more detail regarding the BlackBerry app signing process you can follow these steps.
http://supportforums.blackberry.com/t5/Testing-and-Deployment/BlackBerry-Applications-and-code-signing-Start-to-Finish/ta-p/445848
There are cod files which require signing and some others are optional. Once all the signatures are correctly added, then the *.cod and *.jad can be copied.
Now *.cod can be extracted by renaming the same to *.zip. By extracting the zip file along with the *.jad the same can be used to download to blackberry devices. If this is directly uploaded to blackberry device through USB, then *.cod, *.jad and *.alx can be copied and used , no need to extract the *.cod
Related
There is no any document for working with iXGuard.
How to download?
How to install?
How to working with it?
I have searched in website but not find any guid.
https://www.guardsquare.com/en/blog/ixguard-30-released
You need to request your quotation first before start using iXGuard, after you enroll they will give you access to guardsquare dashboard, And you can download iXGuard package (Documentation include on package)
Here is a small post be me - Getting Started with iXGuard — an obfuscation & app shrinking tool.
In this Tutorial, you’ll learn how to implement iXGuard in iOS project and how to strip down your app size by making use of iXGuard — an app shrinking and obfuscation tool. This is a step by step process tutorial for installing iXGuard. Let me know of any issues. I have briefly explained the process below.
It is not possible to write or explain the whole tutorial with images in the stackoveflow answer so a link is provided.
Installing iXGuard
Install iXGuard for your version of Xcode using the standard procedure of installing a package file.
Create an IPA using Xcode
1) Create a file for distribution with Product -> Archive in Xcode
2) Select the archive created in Organizer and select Distribute App.
3) Select iOS App Store then Next
4) Select Export and click Next.
5) Include bitcode for iOS content and Upload your app’s symbols to receive symbolicated reports from Apple After checking the items click Next
6) After setting the certificate related settings, export and save
Create ixguard.yml
a. The file may be different for each app. For details, please refer to the Configuration page of iXGuard.
b. From the folder where the exported ipa file is located to the terminal
ixguard.yml -o [Obfuscated IPA file name] [Generated IPA file name]
When you input the command, ixguard.yml default file is created.
Sample — ixguard.yml (This may vary from Project to Project
Apply iXGuard From the folder where the exported ipa file is located to the terminal ixguard. Please enter the following command in the terminal. config ixguard.yml -o [After obfuscation IPA] [File name] [Generated IPA file name] to apply iXGuard.
If there are no error’s in the operation, an obfuscated ipa file is created.
In the case of [warning] of the log in the terminal, the solution for each case is the same as that of the iXGuard manual
On the Troubleshooting -> Runtime Issues page. — Note: Appearance
Note: Result screen
Test your app
Test the function of the app by using methods such as TestFlight on the actual device.
In particular, tokens, authentication keys, etc. are required for logic-oriented testing.
Obfuscation verification
This part has been verified using the MachOView tool.
1) Perform step 2 to create an ipa file. Include bitcode for iOS content check - Release and create two obsolete ipa and two ipa files that are not obfuscated.
2) Change the extension of the corresponding ipa file to zip and unzip it.
3) There is a Payload folder in the unpacked folder, and check the application file with the app name in it.
4) Right-click on the application and select View Package.
5) Copy the executable file with the name of the app in the package and extract it to an arbitrary directory.
6) Open the executable extracted before obfuscation and executable extracted after obfuscation with MachOView app,
Check the name of the debris and confirm that obfuscation is applied.
Image for reference in tutorial. (Above: prior to obfuscation, below: after obfuscation)
Finally , deploy the app in the App Store –
Xcode -> Open Developer Tool -> Application Loader.
Application Loader is not available now. You can use Transporter app which is available in Mac app store.
We submit a .zip file on Blackberry app world for publishing. But they return it because they said that there is an error: Error starting MyApp: Module 'MyApp' attempts to access a secure API. I searched about this error and it all said that this error will appear if my app is not sign. But we are sure that is is signed because we sign it before building and submitting it to the Testers. What could be wrong? Another thing we use the .jad to install it on the devices, and if we open the .jad we could see all the signing there. Is it possible that the signing just happens on the .jad and not on the .cod files?
It turns out that having large sizes of .cod or the last .cod having 64kb and up in size causes the problem. I found some posts on Blackberry developers forum saying that when you have .cod like this, when you install the app via OTA and you use mobile network, some network truncates the .cod thus removing the signature. The solution for this problem is to add an image(approximately 10kb) on res and rebuild the application so that the an extra cod could be created and the sizes of other cods would be lessen. My cods that I submitted having this problem has 86kb and the last cod is 63kb, I added a 10kb image and rebuild the application. New cod was added and the sizes of other cods lessen. The size of my maximum cod is just 74kb, and the newly created cod is 25kb. This is the set of cods which was published successfully on app world.
References:
First link
Second link
Third link
So we develop apps for Blackberry OS7 & earlier as well as of recently, apps for BB10. The problem is that BB OS7 uses a different WebWorks SDK as opposed to BB10 & yet I am to install them both in the same directory as per the documentation.
The problem comes in when attempting to sign since the executable files for both SDK's have the same name.
Hence when I attempt to sign my BB 7 app using "bbwp" it throws an error. The error output is "Cannot Sign Application - failed to find signing key file: author.p12". This is obviously the BB10 "bbwp" executable file that's running.This is because both "bbwp" executable files are in the same location and both are named "bbwp".
How does one get around this?
Solved it! And quite a simple solution too!
All I did was to give a different folder name to one of the SDK's. When I ran the command to sign, I simply navigated to the new folder name, called the bbwp.exe and ran it against my project!
I've got an issue with how PhoneGap:Build is currently building iOS applications: splash screens are duplicated, greatly increasing the compiled file size of my applications.
Previously they had an issue wherein they were copying the wrong icon into the Android XHDPI icon folder for Android builds, and I was able to write a script that automated fixing this bug post-build since they seemed to show no interest in fixing the bug (almost a year now since the original bug report & while it seems it might be fixed presently, they haven't commented lately).
I know that I can rename an IPA to a ZIP, unzip it, and browse its contents. I could automate the following steps easily:
Rename
Unzip
Find & remove originals for splash screen images via config.xml file
Re-zip (& rename?)
...But I'm not sure where I'd have to go from there. I've found a few threads that discuss using Xcode to run different utilities, perform signing, etc; but they all seem to assume you've got an xcode project locally, which I don't. (I use PhoneGap & PhoneGap:Build specifically to avoid those headaches.)
I'll have access to all of the same key files that are uploaded to PhoneGap:Build for the original signing process, and I know all of the necessary passwords. I have Xcode installed (just not a local xcode project)...
Is it possible to re-assemble a "fixed" zip into a signed IPA for dev/release distribution using command line utilities & without creating a local Xcode project? If so, how?
Yes, this is possible.
You can export an IPA, unzip it, delete the duplicate file (assuming your code doesn't reference it), then re-sign the app and zip the IPA back up.
You'll find examples on how to use the commandline tool "codesign" to resign a .app directory on stackoverflow!
From what little is available on the Internet for signing BB apps, I can guess that we just need the .cod file for signing an app and don't need the source code.
Can someone please confirm this?
Your .cod file is generated automatically when you compile your code. You'll only need to sign it if you use any of the controlled API's: Runtime API, Blackberry Apps API and Crypto API.
You then register with Blackberry (which is free, but requires a credit card), they issue you with a signing key which you then use to sign all future cod files.
I use Eclipse with Blackberry JDE plugin and by navigating to the Blackberry -> Request Signatures.. dialog you will see if any of your .cod files need signed.
I wrote an article in Feb 2009 about this and it seems to have helped quite a few people:
BlackBerry Code Signing Help, Part II
Slight correction to #Fermin. If you don't have the source code, you need the .cod file and the .csl file (and optionally the .cso file) - all of which are generated by RAPC (usually invoked through the JDE, or the Eclipse Plug-In).
The .cod is what will be loaded onto the device, the .csl and .cso are files for the BlackBerry signature tool that tell it which signatures are needed (respectively, they list the required and optional keys needed for your app). If you don't have those 2 files, the signature tool will think no signatures are needed and won't sign the .cod, which will then fail to run on your device.
If no .csl file was generated, it means that there are no required signatures for your .cod, and you can run on the device without signing.
EDIT: Also the code signing keys are only $20 USD, and it's a quick process.