I was wondering if a share extension creates an .ipa file similarly to a regular target?
Thanks
No, it's packaged in your app's IPA and delivered to Apple as a single file with it (and everything else).
An IPA itself is a zip format file -- if you make a copy of one and rename it to .zip, you can unzip it and look at what it has.
At the top level it has a Payload folder with a .app file in it. That file is a package (you can right-click and show contents). In there, you'll find a PlugIns folder, which will have *.appex files. These are what your extension targets build.
So, the IPA's Payload/NAME.app/PlugIns/*.appex packages are the extensions.
Related
I've IPA which is uploaded on AppStore. On unzipping IPA I see two folders
Payload and Symbols.
Symbols folder contains many files with extension .symbol
Any idea what would be these symbol files? Can we use them for symbolication?
Yes, it is debug symbols. They contain a mapping between encoded names and locations in your compiled code and the original function names among other debug information. Each <UUID>.symbols file represents either the main binary of you app or a framework that your app is using. You can find out which is which using mdfind (see example).
See this about symbolication
I have a client which is delivering me an XCArchive file to be used as the base layer of a project. I am to extend the base classes and add customization. How can I use an XCArchive file in my project? Is there any way to convert or extract a precompiled library (.a) or attach as a framework somehow, add it as a target, ect...
Not sure where to begin on this one.
Ask for the whole project. Not just the archive file.
The archive does not contain app's source code
I was just wondering if app extension (f.e. stickers) affects containing app size in the App Store?
As far as I can see in the build package, there are resources, main executable file and executable file for the extension. So it probably won't affect final app size, but I'm not sure and cannot find any information in the internet.
Can anybody help me with this question?
Yes, the app extensions will affect the final ipa file size.
Build out your two .ipa files. One for the project without the app extension and one with the app extension. Compare those two file sizes to see the size difference.
To see the size of the .appex, rename your .ipa to .zip and double click the zip file to extract it. Open the extracted folder and control+click the .ios file. You can now look inside that folder and see what is changing.
What is the right way to get the final .jad & .cod files ready for distribution?
Currently I use a very poor, manual approach:
Package project & sign
Open explorer, navigate to the deliverables folder
Rename .cod files to .zip & extract them
Manually add the correct .cod files to the correct .jad file
This is wrong, but it works. What is the right way to do this? thx
Consider JadTool from BlackBerry Ant Tools
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.