How to open an IOS project with no ".xcodeproject" file? - ios

I recently received an application developed by a third party which was packaged in a ".jpa" archive. I changed the file extension to ".zip" and was able to extract the contents.
There are a lot of iOS app type files in the extracted folder (plists, nibs, including "MainController.nib", a bunch of .png files - and one "mom" file.
I'm used to seeing an "xcodeproj" file somewhere, but it's been a few years since I developed an iPhone app. I don't really see any code or delegates or header files etc.
I'm currently running Xcode 6.11. How do I open this app?

Related

how to save file from an iOS react native app to Files folder

I created a pdf file in my react native app for iOS devices, and also I can open the file in my application because it saved in Documents directory of internal storage of my application, but I want to save the file to Files folder in iOS and open it with other applications, how can I do it?
thank for your attention.
For IOS you should open share options and save the file to the Files folder. For this you can use 'react-native-share' library. If you are using Expo, use 'expo-share'. Please check below documentation.
https://www.npmjs.com/package/react-native-sharing
https://docs.expo.dev/versions/latest/sdk/sharing/

iOS Today Widget share source file with main application

I've added a Today Extention Widget Project in my Xcode workspace and I want to use some source file from the main app, so I've flagged the "target membership" on this files. The problem is that the Xcode linker fail with duplicate symbol error when compiling the main app. So what is the correct way to share source file between main app and widget?
You can use Frameworks to share code/files between your Host App and App Extension.
You can create an embedded framework to share code between your app
extension and its containing app. For example, if you develop an image
filter for use in your Photo Editing extension as well as in its
containing app, put the filter’s code in a framework and embed the
framework in both targets.
For more on sharing scenarios between Host App and App Extension refer to: https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/ExtensionScenarios.html#//apple_ref/doc/uid/TP40014214-CH21-SW1

Dropbox UIDocumentPicker plugin cannot open OS X file packages

On my OS X machine I have placed a document which actually is a file package (aka document bundle) into my dropbox. When I try to open that file package on my iOS device using the UIDpocumentPicker plugin the file package appears as a folder. On the other hand it appears as a file package in the iOS DropBox App itself. It also appears as a file in iCloud drive.
Why is there a different behavior? I would expect both dropbox interfaces to display the file package as a file and be able to open it like I can open out from iCloud drive.
(Dropbox App-Version 4.2.5 on iOS 9.2)
Anyone else having this issue and any idea on what one could do?
Packages are effectively folders, not files. Different interfaces may not display them the same way though. E.g., sometimes you'll see a special icon indicating it's a package, and sometimes just the normal folder icon will be used.
In any case, packages/folders aren't currently supported in the Dropbox iOS app UIDocumentPicker. We'll consider this a feature request though.

sqlite file gets picked up by the xcode simulator but not the ios device

I had a sqlite file which was working fine on the simulator and the device.
Under my app folder on the mac, I can also see the file - coredata.sqlite.
I created a new coredata.sqlite. After this, I had to copy it over to the paths which were different for different targets (iphone 5 vs 6 vs 6+) and looked along the lines of :
.../Library/Developer/CoreSimulator/Devices/26292D7B-5001-497E-B23B-99455953F5F4/data/Containers/Data/Application/64849BCC-B86B-45DE-818F-3E67346C4893/Documents/
Just copying over the new sqlite to the apps folder where the old sqlite was present did not work. Copying it to the above mentioned folders fixed it for the simulator.
Now, when I connect to my ios device though, it cant find the new sqlite. If I copy back the old sqlite to the apps folder, it still works but copying the new one to the apps folder, the various destinations for the simulator etc has no effect on the ios device.
Displaying the path where it is looking at shows :
/var/mobile/Containers/Data/Application/80302FBA-6D45-4843-A891-E10A7ED4D445/Documents/CoreData.sqlite
Any help on where the device is picking the sqlite from? Since it works on the simulator and the older one works on the device also, the code seems ok. What can I do to get it to pick my new sqlite?
Device will pick the files from mainBundle. While doing database related functionality we copy the db files from mainBundle to DocumentDirectory, so that it becomes editable.
What you did was that you manually copied the sqlite file to the app data document folder. You should actually add the file to specific target and then it will copy the file during build process.
Your new coredata.sqlite file is not attached to any target. Check inside build phases and see if it is there, otherwise add it. Also you should not have two files with same name inside the bundle, so remove the previous file from target.

What "source code files" are needed to turnover (continue develop of) an iOS application?

I am working with a developer on an iOS app and upon completion, all source code, files, etc. should be turned over to me so that I can continue development in the future with another developer if necessary. I need help understanding exactly which files I should receive.
Should I be ok with .ipa file? Or maybe .app file? Or the Xcode project file? What will ensure that I have all I need to continue development in the future?
You will receive the project folder, which contains a .xcodeproj file and other files such as images assets. You can download a demo project from here.
You won't receive an .ipa file because the .ipa files are the ones you download from the App Store (they have been archived), hence no one can see their code so people can't steal it.

Resources