I've recently updated from Titanium w/3.5.0.GA SDK to Appcelerator Studio w/5.2.0SDK and can no longer build and run the appc (5.1.0 CLI) generated projects in XCode (7.2.1) without losing the ability to display my custom font resources (app/assets/fonts).
When building a project for iOS in studio (latest 4.4.0) and deploying to connected iPhone 6 (running 9.2) all fonts appear correctly in app. However when building and running the <projectname>.xcodeproject that is generated by appc during this process the same fonts do not show?
Is this related to https://jira.appcelerator.org/browse/TIMOB-19818 ? Is there any fix on the horizon if so?
I have always relied on modifying the generated projects to include other asset catalogs and manually alter the build and version numbers prior to appstore submission so am very curious to find a solution to this issue - all help much appreciated!
FYI - for reference, I've tried to build the same project generated in Titanium studio w/3.5.0.GA within the Latest XCode (7.2.1) as above and the fonts still work correctly so this issue seems to be with Appcelerator Studio with CLI 5.1.0 and SDK 5.2.0 combination.
You can follow this below two steps. This is a workaround, might work for you.
Step 1: Grab resource files from debug ipa:
a. Build a debug version for your iPhone device.
b. After the app has successfully launched on your iPhone, navigate to the ipa file in the debug build folder. Click right on the file (or cmd-click) and choose to uncompress the file
c. In the extracted archive find the payload file. Also right click on the file (or cmd-click) and choose to show its contents.
d. You should now see your resource files and folders. Select all the required files and folders and copy them in some new folder.
Step 2: Add files to XCode project
a. Open the build XCode project with XCode
b. In the left column right click (or cmd-click) on your project
c. Choose "Add Files to [project name]"
d. In the file dialog multiselect your files and folders you copied from the debug ipa in step 1
e. That's it. Now archive your product and submit it.
Related
I have created an XCode 8 Extension (For Deleting Lines, Like Sublime and Android Studio). I have code-signed it and it works as expected in the Gray Xcode Test thing.
I haven't seen a single instruction on how to get it to run with "Regular" XCode? What should I do to be able to use my extension whenever I start XCode?
After somehow getting this to work (once) by restarting my computer, I have finally found some working instructions on how to use an Extension with XCode 8. These are the steps:
Enable target signing for both the Application and the Source Code Extension using your developer ID.
Product > Archive.
Right click archive > Show in Finder.
Right click archive > Show Package Contents.
Open Products, Applications.
Drag "YourExtension".app to your Applications folder.
Go to System Preferences -> Extensions -> Xcode Source Editor and enable this extension.
Restart XCode if necessary
I downloaded FlickrKit and open its sample project file. But cannot run coz of following error. Changing the 'Deployment Target' didn't work. Please, help !
According to the error, the project was probably made in a newer version of Xcode than the one currently on your machine. Update your software and if it still doesn't work, I'd assume it was made with the newest developer only version, Xcode 5.
If this is the case you must purchase a developer account at the: iPhone Developer Center and download Xcode 5. If you do not want to do that, you cannot use the project.
Its easier than that to recover your existing project. Open the project file on Xcode 5. Then:
Open file inspector for each xib
On "Interface Builder Documents" section change "Open with" to Xcode
4.6 (if it's 5.0). Adjust any other obviously incompatible parameters
Save, Close the project and open with the old Xcode.
I am creating an IOS app with cordova 2.1.0.
I installed cordova 2.1.0, by following the steps mentioned in http://docs.phonegap.com/en/2.1.0/guide_getting-started_ios_index.md.html#Getting%20Started%20with%20iO
Now i made changes to files like AppDelegate.m, AppDelegate.h, etc. and www folder. When i see the physical folder structure in the project, the CordovaLib.xcodeproj does'nt get included in the project. Why is this happening? Why is it not getting included in the project. Every user will not download cordova and follow the steps.
Any help will be appreciated.
Thanks.
What do you mean by "user will not download". The developer (you) have to downlod it nd create the app. Cordova is packaged within your *.ip file.
If the cordov project is not oincluded, you will be unabvle to build. If you cn build it, it is included.
If you don't want to handle the complete xcode project stuff, use build.phonegap.com
of course i did research before posting my question.
I looked at
How to "add existing frameworks" in Xcode 4?
Adding Framework in Xcode 4
Adding an OpenGL framework in Xcode 4
XCode 4 adding dylib
but whole thing is becoming wrong.
My goal: Add (CorePlot) framework to XCode Mac project (not an iPhone one)
My environment: OSX Lion 10.7, SDK Lion, XCode 4.1 (4B110)
My steps:
Opened XCode, created new project
Downloaded CorePlot into my libraries directory (like ~/Applications/LIBS)
Opened project preferences, via (+) opened dialog to add framework
Add existing framework (+ copy files to dest. group if needed)
Selected directory was ~/Applications/LIBS/CorePlot/Binaries/MacOS/CorePlot.framework/
DnD CorePlot to Frameworks Group
Added CorePlot to Build Phases > Link Binary with Libraries
and ran my project
what I got is this error message:
dyld: Library not loaded: #loader_path/../Frameworks/CorePlot.framework/Versions/A/CorePlot
Referenced from: /Users/username/Library/Developer/Xcode/DerivedData/metralight-hjuvuwlhgohrtdeepvcymnsaxomc/Build/Products/Debug/metralight.app/Contents/MacOS/metralight
Reason: image not found
And in fact, when I looked into given directory (app bundle) there was no directory Frameworks and so the linking cannot be successful
I have searched one more, and found, that I can create Build Rule and copy files into final binary bundle via some script, but is this only way how to do this?
Isn't there some option to just turn on/off copying linked frameworks to final bundle?
Note that CorePlot target '.framework' has Dynamic Library Install Name set to #loader_path/../Frameworks/CorePlot.framework/Versions/A/CorePlot, so it is looking in right place in final binary bundle
After adding framework via "Add existing framework"
Go to Project Settings > Build Phases
In right bottom corner click Add buid phase > Copy Files
Select Destination > Frameworks
Drag&Drop framework to files list
And that's it.
Another important detail here - you must have the "Runtime search path" to be defined in the projects, it's empty by default.
Something like this:
LD_RUNPATH_SEARCH_PATHS = #loader_path/../Frameworks
I've created a new App and want to test it in a release version. So I copied the Growl Framework to my project folder and added into XCode.
Then I copied the new files in the target in my project and copied the Growl.framework to the new "Copy Files" Framework folder in "Targets". When I debug my project, it's all right, but if I change the version to "Release" and then Build, there is the Red "1" on my XCode icon in the Dock. I dont know why this error comes; I've searched in Google but I can't find anything.
Can anyone Help me please?! Here is the Picture of my Copied Files:
XCode http://b1.s3.quickshareit.com/bild15ead2.png
Try ordering the Copy Files phase above the link phase.
When i debug my Project, its all right, but if i change the Version to "Release" and than Build -> there is the Red "1" on my XCode icon in the Dock,
Well, what does the error say?
alt text http://b2.s3.quickshareit.com/bild23a027.png
"malformed object: Unknown load command 5"
This usually indicates that you have a binary that was built on a later version of Mac OS X (e.g. SnowLeopard) and you're trying to link it on an earlier version of Mac OS X (e.g. 10.5 Leopard).
Ensure you have a correct version of the Growl framework for your development environment and OS.