How can develop and submit iOS app with custom dylib - ios

I think it's quite crazy but can I develop and submit an iOS app with custom dylib (also programmed by me).
I read instructions from Apple developer site about how to create dynamic library which is linked at runtime
https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/DynamicLibraries/000-Introduction/Introduction.html#//apple_ref/doc/uid/TP40001908-SW1
I developed a custom dylib framework, and use it in an ios app. And I want to submit the app to Apple Store. I read somewhere that from ios 8, develop dynamic library is legible.
But I have a question, if I submit my app, users download it to their ios devices, how can these devices load and run my custom dylib (is integrated with my app)

Well, as you said that dynamic framework just supports iOS 8 and above.
So your iOS application minimum target should be 8 so you can submit your application to the App Store. And users with iOS 8 can download your app.
There are another choice by making a static framework if you would like to support iOS lower than 8.

Related

Check Build SDK Version

With the new App Requirements and Guidelines from Apple, one of them is that Apps for iPhone or iPad must be built with the iOS 13 SDK or later.
My company has several apps on iTunes, and I was wondering if there is some way to see what SDK version a build was built with, either in iTunes or in the Organiser in Xcode.
Otherwise I guess the only option is to rebuild and upload apps that we haven't build for a while, but I'm not sure.
The requirement to use the iOS 13 SDK only applies to new submissions. Apps already on the App Store don't need to be updated.
If you submit a new version containing enhancements or bug fixes, then you need to use the iOS 13 SDK.
You do not need to submit an otherwise unchanged app simply to use the iOS 13 SDK.

Migrate to xcode 9 for swift 2.3 apps

I have an app launched in appstore built on Swift 2.3 using Xcode 8, now apple made Xcode 9 mandatory for new and app updates to store
Is it must to migrate to Xcode 9? have any one submitted swift 2.3 apps to appstore in July?
I think you need to migrate to XCode 9. All iOS app updates submitted to the App Store must be built with the iOS 11 SDK.
iOS 11 delivers innovative features and the redesigned App Store to hundreds of
millions of customers around the world. Your apps can deliver more intelligent,
unified, and immersive experiences with Core ML, ARKit, new camera APIs, new
SiriKit domains, Apple Music integration, drag and drop for iPad, and more.
Starting July 2018, all iOS app updates submitted to the App Store must be
built with the iOS 11 SDK and must support the Super Retina display of
iPhone X.
Reference Upcoming iOS 11 App Update Requirements
If your app is in swift 2.x syntax and now you need to upload you must need to convert first to swift syntax 3 (using xcode 8.x) and then you can open it in xcode 9.x to upload your app
if your app is already live it may be give error or warning like below screenshot

Will I be able to submit iOS PhoneGap Build apps after February 1?

From February 1, apple is changing the rules for submitting apps to the app store. All apps will have to be build using iOS 7 SDK and will have to be compiled with xcode.
I am afraid that this might mean that all my projects built with Adobe Phonegap Build will be useless (ones that use Phonegap build plugins that are not locally available).
I am aware of THIS question.
However that question only talks about PhoneGap (cordova), and not PhoneGap Build specifically.
With Phonegap (cordova) I can build apps locally and an xcode project gets generated, so that will not prevent people from submitting apps as in the end you will still build it with xcode.
However, with Adobe PhoneGap build, the app binary is compiled on adobe's servers and not on my installation of xcode, and that service does not generate an xcode project.
So my question is, will these PhoneGap Build generated apps be accepted by apple or not? I am afraid that I am right by thinking that they will not be accepted, but just want to make sure, so if you know more about this please let me know.
I'm pretty sure that the statement from Apple only means that apps built with Xcode version < 5 and not optimised for iOS7 are not accepted any longer - not that you cannot submit apps built with different frameworks (if they are compliant to their new UI guidelines, of course).
I would not worry about this. Apple basically said they will no longer allow apps that are built using the iOS 6 SDK / Xcode 4. I don't expect other changes in their policies and didn't hear a big outcry on Twitter either :)

Will Apple reject our app if I support iOS 3.x?

I'm aware that if I build our app on Xcode 4.5, We won't be able to submit our app to the App Store not to mention we won't even be able to run the thing on the device with iOS3.x.
Not what I want to clarify is that, if we decided to still support iOS3.x do we just use Xcode 4.3 or any Xcode lower than 4.5 and voila I can submit it to the app store and Apple won't give a care and approve the app if it supports iOS3.x or not since it was built using a lower version of Xcode?
As long as you provided an iPhone 5 screenshot, you should be able to submit app that backward supports iOS 3.x .
But why do you want to support iOS 3.x ? Not many devices are using this iOS version .

Does Apple state which SDK version is mandatory to use for iOS apps?

Does anyone knows if there is a document from Apple that states what iOS SDK version you have to use for building your app to upload it to iTunes Connect?
I often read in blogs "only the latest", but I need this official from Apple because our vendor wants to build against the iOS 4 SDK because of "strange errors with iOS 5".
I'm not sure if this is OK. We want to run the app to run on iOS 4 and 5.
I too had read what you had—that the latest SDK had to be used... Yet, I haven't found an official source for this now I go looking for it.
Using the iOS 5 SDK does not prevent you from having a build target of iOS 4.2 (or similar), which will it to run on both iOS 4.2+ as well as iOS 5. Perhaps a good starting point is educating the client that there is a fundamental difference between the iOS 5 SDK and iOS 5 itself—they may well just be reacting to media coverage of iOS 5 issues like battery life.

Resources