πFeel free to contribute this Repository!!π
- Coding Convention
- App Life Cycle
- ViewController Life Cycle
- Design Pattern
- Code Structuring
- UIDesign
- Bundle
- Screen Layout Programmatically
- Helper
- API
- JSON
- NotificationCenter
- UserDefaults
- Core Data
- Core Bluetooth
- Third Party Library
- Localization
- Accessibility
- GCD
- Operation
- Thread Sanitizer
- Testing
- CI/CD
- Swift DocC
- Tuist
- In App Purchase(IAP)
- Notification
- FRP
- Security
- Objective-C
- Error Search
- Useful Stuff
set of guidelines for a specific programming language that recommend programming style
The way of force you to adapt coding convention
otherwise project build will FAILED
- Swift Lint apply for all project:+1:
if which swiftlint >/dev/null; then
swiftlint
else
echo "error: SwiftLint not installed, download from https://github.com/realm/SwiftLint"
exit 1
fi
put .yml file into root folder and apply following code in Build Phases
You can modify(delete) SwiftLint Option with opening .yml file
Shift + Command + . will show the hidden file
ππ Recommend Book ππ
Book Name | Authors Name |
---|---|
Clean Code: A Handbook of Agile Software Craftsmanship | Robert C. Martin |
The Pragmatic Programmer Your Journey to Mastery, 20th Anniversary Edition | Andrew Hunt David Hurst Thomas |
- viewDidLoad
- viewWillAppear
- viewWillLayoutSubviews
- viewDidLayoutSubviews
- viewDidAppear
- viewWillDisappear
- viewDidDisappear
iOS View Controller Life Cycle
Check this website for design pattern in Swift
Adapter pattern is a structural design pattern that is useful for composing classes and objects into a larger system.
protocol Target {
func request()
}
class Adaptee {
func specificRequest() {}
}
class Adapter: Target {
let adaptee: Adaptee
init(adaptee: Adaptee) {
self.adaptee = adaptee
}
func request() {
adaptee.specificRequest()
}
}
Delegation is a design pattern that enables a class to hand off (or βdelegateβ) some of its responsibilities to an instance of another class.
Create a protocol
protocol SomeProtocol: AnyObject {
func reload()
}
Create a delegate
weak var delegate: SomeProtocol?
You can check the code using delegation pattern here
Dependency injection is a pattern that can be used to eliminate the need for singletons in a project
- Raise Transparency
- Improve Testability
1. initializer injection
class DataManager {
private let serializer: Serializer
init(serializer: Serializer) {
self.serializer = serializer
}
}
2. property injection
import UIKit
class ViewController: UIViewController {
var requestManager: RequestManager?
}
3. method injection
import Foundation
class DataManager {
func serializeRequest(request: Request, withSerializer serializer: Serializer) -> Data? {
...
}
}
Nuts and Bolts of Dependency Injection in Swift
Factory method is a creational design pattern which solves the problem of creating product objects without specifying their concrete classes.
Observer is a behavioral design pattern that allows some objects to notify other objects about changes in their state.
- Observer - An object that wishes to be notified when the state of another object changes.
- Subject (Observable) - An object that maintains a list of observers, and inform them of state changes usually by calling one of their methods. An observable slightly differs in this in that it is just a function that sets up an observation.
- Subscribe - An observer lets a subject know that it wants to be informed of changes through a process called subscribing.
Check following sites
TBD
KVO stands for Key Value Observing
We are using KVC in Storyboard!
singleton pattern is to ensure only one instance of a class is alive at any one time.
class SingletonPattern {
static let manager = SingletonPattern()
private init() {}
}
Swift-DocC is a documentation compiler for Swift frameworks and packages aimed at making it easy to write and publish great developer documentation.
Simple goes to Product-Build Documentation and DocC will open
ππ Recommend Book ππ
Book Name | Authors Name |
---|---|
Advanced iOS App Architecture : Real-world app architecture in Swift | raywenderlich Tutorial Team |
Clean Architecture: A Craftsman's Guide to Software Structure and Design | Robert Martin |
MVC pattern stands for Model - View - Controller
- Model - Model take care of storing data.
- View - View renders the data for users
- Controller - Controller modifies the View, accepts user input and interacts directly with the Model. And take care of view logic and business logic.
MVVM patterns stand for Model - View - ViewModel
-
Model β Which holds the application data
-
View β It displays the data that is stored in model. These are visual elements through which a user interacts. These are subclasses of UIView
-
View Model β Transform model information/data and it interacts with controller or view to display those informations.
-
Controller class β It will be there but the responsibility of view business logic has been removed and give to view model
You can check App example of using MVVM here
- View - Displays what it is told to by the Presenter and relays user input back to the Presenter.
- Interactor - Contains the business logic as specified by a use case.
- Presenter - contains view logic for preparing content for display (as received from the Interactor) and for reacting to user inputs (by requesting new data from the Interactor).
- Entity - contains basic model objects used by the Interactor.
- Routing - contains navigation logic for describing which screens are shown in which order.
Getting Started with the VIPER Architecture Pattern
The Composable Architecture is a library for building applications in a consistent and understandable way, with composition, testing, and ergonomics in mind
- Composable Architecture @ Point Free
- The Composable Architecture GitHub
- The Composable Architecture β One of the Best-Suited Architectures for SwiftUI
// example will update here
A reducer describes how to evolve the current state of an application to the next state, given an action, and describes what Effects should be executed later by the store, if any.
The Repository and Unit of Work Patterns
SwiftUI is a user interface toolkit that lets us design apps in a declarative way(Declarative syntax).
- Fucking SwiftUI Cheat Sheet for SwiftUI
- Gosh Darn SwiftUI Cheat Sheet for SwiftUI
- SimpleBoilerplates/SwiftUI-Cheat-Sheet
TBA
- SF Symbols Download SF Symbols2 for more icons!
- icon8 You can download icons imge for your APP
- appicon generate the app icon size
- flaticon Free icons download
- DetailsPro You can design with SwiftUI free π
- HEX Color Picker Good for picking color as Hex π
TBA
You can use Bundle+Extension.swift file to configure your bundle to your application.
Source code from : PhoneNumberKit
XCFrameworks is a distributable binary package created by Xcode that contains variants of a framework or library so that it can be used on multiple platforms (iOS, macOS, tvOS, and watchOS), including Simulator builds
Creating a multiplatform binary framework bundle
All files are resuable files and protocol oriented. Just Copy and Paste inside your project and use it!! π
These helper files are not with Error Handling! careful at use
You can check the file in the follow link
import MessageUI first
import MessageUI
Then use it
Don't forget to extend the mail, message delegate to your ViewController!
lazy var conversation = ConversationManager(presentingController: self, mailDelegate: self, messageDelegate: self, viewController: self)
@IBAction private func sendEmail(_ sender: UIButton) {
conversation.sendEmail(feedback: MailFeedback(recipients: ["abcd@google.com"], subject: "FeedBack", body: "Write feedback here"))
}
@IBAction private func sendMessage(_ sender: UIButton) {
conversation.sendMessage(feedback: MessageFeedBack(recipients: ["1111111111"], body: "Type here"))
}
@IBAction private func startCall(_ sender: UIButton) {
conversation.makeCall(number: "1111111111")
}
Good To GO πππ
See Example here
First, set the base URL in EndPointType file
Don't forget to put your API key in it!
var baseURL: URL {
guard let url = URL(string: "https://api.openweathermap.org/data/2.5/") else {
fatalError("baseURL could not be configured.")
}
return url
}
then make a instance of router.swift file in your code
private let router = Router<YourAPI>()
for YourAPI part, simply create a new enum with cases about specific api URL
It will make your router more dynamic! Don't forget extension to EndPointType!
enum YourAPI {
case first(country: String)
case second(time: Int)
case third(name: String)
}
extension YourAPI: EndPointType {
var path: String {
switch self {
case .first(let country):
return "\(country).json"
case .second(let time):
return "\(time).json"
case .third(let name):
return "\(name).json"
}
}
}
then, use it like this
router.request(.first(country: London)) { [weak self] (results: Result<CountryWeather, AppError>) in
guard let self = self else { return }
switch results {
case .success(let data):
// insert your modifications!
case .failure(let error):
// insert your modifications!
print(error)
}
}
CountryWeather should be a model with Decodable
If you want to see how can I use Network Layer in Project, check this
This reusable network layer files for referenced from here
Also Alamofire will be a great option for Network Layer!
Copy and Paste in your project and then declare Image Picker object inside your project
lazy var imagePicker = ImagePicker(presentationController: self, delegate: self)
Then, extend ImagePickerDelegate to your viewController
extension ViewController: ImagePickerDelegate {
func didSelect(image: UIImage?) {
self.yourImageView.image = image
self.dismiss(animated: true, completion: nil)
}
}
Good To GO πππ
See Example here
Copy and Paste in your project
let readData = FileManageHelper.manager.readFile(filename: fileNameTextField.text ?? "", type: extensionTextField.text ?? "")
resultTextField.text = readData
File Manager are wrote with singleton pattern, therefore no need to declare in side your code!
Good To GO πππ
Make an object of VideoManager inside your code
let videoManager = VideoManager()
use downloadVideoLinkAndCreateAsset function to start download with entering URL
self.videoManager.downloadVideoLinkAndCreateAsset(text)
Good To GO πππ
There is no file for Image Downloader.
To download images into device, only thing is this
if let data = try? Data(contentsOf: urls),
let image = UIImage(data: data) {
UIImageWriteToSavedPhotosAlbum(image, nil, nilil)
}
Just change urls into your image URL
UIImageWriteToSavedPhotosAlbum will take care it to download to device.
For more info go here
Good To GO πππ
Currently Working
API(Application Programming Interface) is an interface that defines interactions between multiple software applications or mixed hardware-software intermediaries. It defines the kinds of calls or requests that can be made, how to make them, the data formats that should be used, the conventions to follow, etc.
JSON is a language-independent data format
Which is relative with KEY - VALUE pair
{
"main": [
{
"title": "example1",
"body": "body1"
},
{
"title": "example2",
"body: "body2"
}
]
}
This extension makes JSON more structable JSON parser pro FREE π
To use JSONDecoder in swift, you have to define the model to be Codable or Decodable
public typealias Codable = Decodable & Encodable
Decodable can only decode the json data. Can't encoded json file!!
struct User: Codable {
var firstName: String
var lastName: String
var country: String
enum CodingKeys: String, CodingKey {
case firstName = "first_name"
case lastName = "last_name"
case country
}
}
To avoid snake_case in swift, use CodingKeys or JSONDecoder.KeyDecodingStrategy
To use JSONDecoding, declare JSONDecoder and use decode() function
do {
let data = try JSONDecoder().decode(T.self, from: unwrappedData)
completionOnMain(.success(data))
} catch {
print(error)
completionOnMain(.failure(.parseError))
}
T.self -> Model(Struct) of the data that you want to decode
data will decoded to form of T
unwrappedData -> Input actual data from file or server
This should be a Data Type!!
JSONSerialization is a old way of decode the JSON file.
Apple populated Codable since Swift 4
Example of number.json data
{
"number": [
{
"name": "Dennis",
"number": "111-222-3333"
},
{
"name": "Jenny",
"number": "444-555-6666"
},
{
"name": "Ben",
"number": "777-888-9999"
}
]
}
Here is a example of JSONSerialization with actaul JSON file in project folder
Otherwise you can use URL!
private func populateDataFromJson() {
if let path = Bundle.main.path(forResource: "NumberData", ofType: "json") {
do {
let dataJson = try Data(contentsOf: URL(fileURLWithPath: path))
let jsonDict = try JSONSerialization.jsonObject(with: dataJson, options: .mutableContainers)
if let jsonResults = jsonDict as? [String: Any],
let results = jsonResults["number"] as? [[String: Any]] {
results.forEach { dict in
// simply appended to list(array)
self.phoneNumberList.append(PhoneNumber(name: dict["name"] as? String ?? "", number: (dict["number"] as? String ?? "")))
self.phoneNumberListClone.append(PhoneNumber(name: dict["name"] as? String ?? "", number: (dict["number"] as? String ?? "")))
}
}
} catch {
print(error.localizedDescription)
}
}
}
.mutableContainers allows to working like a array and dictionary type
This library provide JSON parsing
A notification dispatch mechanism that enables the broadcast of information to registered observers.
The UserDefaults class provides a programmatic interface for interacting with the defaults system. Check Apple Document for more info
UserDefaults has to have key-value pair
- User information, like name, email address, age, occupation
- App settings, like user interface language, app color theme or βdetailed vs. simple UIβ
- Flags, more on this later
- If store data is small
Put this line of code inside of your project
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
print(NSSearchPathForDirectoriesInDomains(.documentDirectory, .userDomainMask, true).last ?? "")
return true
}
simply move into that path and you can find the documentDirectory of your Application
if Library is not shown up, just do Shift + Command + . to show hidden files in your folder
As you can see in the below, intArray will stored inside the device through UserDefaults(), so that if device is shut down, changed value wil be stored in device.
class ViewController: UIViewController {
var intArray = [1,2,3,4,5]
let defaults = UserDefaults()
override func viewDidLoad() {
super.viewDidLoad()
intArray = defaults.array(forKey: "IntArray") as! [Int]
}
@IBOutlet weak var textField: UILabel!
@IBAction private func isClicked(_ sender: UIButton) {
intArray.append(6)
defaults.set(intArray, forKey: "IntArray")
textField.text = "\(intArray)"
}
}
You can your plist file like this!
Declare Userdefault like this!
let defaults = UserDefaults.standard
standard allows to access from anywhere inside device
With using set function, you can set userdefaults
Also these function will allow to get a data from plist
You are GOOD TO GO πππ
Use Core Data to save your applicationβs permanent data for offline use, to cache temporary data, and to add undo functionality to your app on a single device.
Core Data in Swift is using SQLite as DEFAULT
Image From London App Brewery
ππ Recommend Book ππ
Book Name | Authors Name |
---|---|
Core Data by Tutorials: iOS 12 and Swift 4.2 Edition | raywenderlich Tutorial Team |
-
NSManagedObject - This is a base class of all the core data model object. This provides the schema of our database table. This is used to store model data in our application. KVO and KVC compliant. It can notify any changes that are done on its properties if any object is listening.
-
NSManagedObjectContext - Most important class. This is the place where you do all the computations. You can think this as a scratch pad where you do all the operations realated to core data (CRUD). It's an object which you can use to manipulate and track any changes done to manage object. All the changes done on a context object will be held until and unless you are discarding or writing those changes permaneently to persistntent storage.
-
NSPersistentStoreCoordinator - The main functionality is to provide a communication between context and persistent store.
-
NSPersistentStore - They are the stores in which the data are being saved. These includes SQLite, In-Memory, Binary, XML(the XML store is not available on iOS).
-
NSPersistentContainer - This contains the whole core data stacks.
Simply Click Core Data check box when you create a new project
If you want to attach Core Data in exsiting project
Create Data Model file first
Then import CoreData inside your AppDelegate.swift file
import CoreData
And Copy and Paste this lines of code inside your AppDelegate.swift file
// MARK: - Core Data stack
lazy var persistentContainer: NSPersistentContainer = {
/*
The persistent container for the application. This implementation
creates and returns a container, having loaded the store for the
application to it. This property is optional since there are legitimate
error conditions that could cause the creation of the store to fail.
*/
let container = NSPersistentContainer(name: "Your DataModel file name")
container.loadPersistentStores(completionHandler: { (storeDescription, error) in
if let error = error as NSError? {
// Replace this implementation with code to handle the error appropriately.
// fatalError() causes the application to generate a crash log and terminate. You should not use this function in a shipping application, although it may be useful during development.
/*
Typical reasons for an error here include:
* The parent directory does not exist, cannot be created, or disallows writing.
* The persistent store is not accessible, due to permissions or data protection when the device is locked.
* The device is out of space.
* The store could not be migrated to the current model version.
Check the error message to determine what the actual problem was.
*/
fatalError("Unresolved error \(error), \(error.userInfo)")
}
})
return container
}()
// MARK: - Core Data Saving support
func saveContext () {
let context = persistentContainer.viewContext
if context.hasChanges {
do {
try context.save()
} catch {
// Replace this implementation with code to handle the error appropriately.
// fatalError() causes the application to generate a crash log and terminate. You should not use this function in a shipping application, although it may be useful during development.
let nserror = error as NSError
fatalError("Unresolved error \(nserror), \(nserror.userInfo)")
}
}
}
Don't forget to change it
let container = NSPersistentContainer(name: "Your DataModel file name")
And goto SceneDelegate.swift file, copy below lines of code and replace yours
func sceneDidEnterBackground(_ scene: UIScene) {
// Called as the scene transitions from the foreground to the background.
// Use this method to save data, release shared resources, and store enough scene-specific state information
// to restore the scene back to its current state.
// Save changes in the application's managed object context when the application transitions to the background.
(UIApplication.shared.delegate as? AppDelegate)?.saveContext()
}
If your target is below iOS13, put this line of code in side your applicationWillTerminate of AppDelegate.swift file
self.saveContext()
Once you create your DataModel file, you can simply create a Entity(Class) and Attributes(Properties)
And then, change the type of attributes in inspector like this
Once you create your own Entities & Attributes, go to Inspector and change Module to CurrentProductModule
If you didn't set it, thats fine, but if you are working in big project, then you need to set it. Otherwise this can occurs some error.
As you can see in above, there are three options
- Manual/None - Swift didn't generate CoreDataClass, CoreDataProperties files so that you have to create yourself (full control)
- Class Definition - Swift will generate CoreDataClass, CoreDataProperties files. (No control)
- Category/Extension - Swift will generate only Extension file (Some Control)
CoreDataClass, CoreDataProperties are located in below
/Users/dennis/Library/Developer/Xcode/DerivedData/CoreDataUserDefaultPractice-hisefjfyuvglrjekndpftwazftug/Build/Intermediates.noindex/CoreDataUserDefaultPractice.build/Debug-iphonesimulator/CoreDataUserDefaultPractice.build/DerivedSources/CoreDataGenerated/CoreDataUserDefaultPractice
And CoreDataClass, CoreDataProperties are looking like this,
If your code can run it but didn't get your Entities, Rebuild it or Restart your Xcode
The reason that files divided into two files is that one for writing Business Logic, one for Properties
An entity represents a table in your database. It is the blueprint for the NSManagedObject subclass instances that you will create and use throughout your application.
Attributes are properties of your object. They translate to a column in your database table and a property in your managed object. You can choose from a variety of primitive values that the database has to offer such as a string, integer, or date.
A relationship describes how one entity relates to another. Two important aspects of this are the cardinality and the deletion rule
- One-to-many - Lets say that each Department has a group of Employees that can only work for a single Department. This would be a βone-to-manyβ relationship since each Department could have many Employees and each Employee can only work for one Department.
- Many-to-many - If a single Employee could work for multiple Departments, then our Department/Employee relationship would be βmany-to-manyβ because each Department could have many Employees and each Employee could work for multiple Departments.
Core Data Relationships and Delete Rules
- No Action - Do nothing to the object at the destination of the relationship. For example, if you delete a department, leave all the employees as they are, even if they still believe they belong to that department.
- Nullify (Default) - Set the inverse relationship for objects at the destination to null. For example, if you delete a department, set the department for all the current members to null. This only makes sense if the department relationship for an employee is optional, or if you ensure that you set a new department for each of the employees before the next save operation.
- Cascade - Delete the objects at the destination of the relationship. For example, if you delete a department, fire all the employees in that department at the same time.
- Deny - If there is at least one object at the relationship destination, then the source object cannot be deleted. For example, if you want to remove a department, you must ensure that all the employees in that department are first transferred elsewhere (or fired!) otherwise the department cannot be deleted.
Declare context as a global variable
let context = (UIApplication.shared.delegate as! AppDelegate).persistentContainer.viewContext
Get viewContext that we defined in AppDelegate.swift file
Simply you can use this code to save your data to CoreData
func saveItem() {
do {
try context.save()
} catch {
print("Error Saving Context: \(error.localizedDescription)")
}
}
Use it wherever you want
Data can be find if you print the path
print(FileManager.default.urls(for: .documentDirectory, in: .userDomainMask))
You can check Entities, Properties inside that file
Refer this code and apply it to your code wherever you want to reload it
func loadItem() {
let request: NSFetchRequest<Item> = Item.fetchRequest()
do {
itemArray = try context.fetch(request)
} catch {
print("Load Item Error: \(error.localizedDescription)")
}
}
Item will be your Entity, itemArray will be your Entity object Don't forget to import CoreData
Simply use setValue function so that you can update your value in DB
itemArray[0].setValue(<#T##value: Any?##Any?#>, forKey: <#T##String#>)
if you are using TableView or CollectionView, change 0 to indexPath.row
Simply use delete function in context
context.delete(itemArray[0])
change number for dynamic!
You are GOOD TO GO πππ
- Introduction to BLE Mobile Development [iOS]
- Core Bluetooth Tutorial for iOS: Heart Rate Monitor
- Getting Started with Core Bluetooth
You are GOOD TO GO πππ
Third Party Library saves you time as you do not need to develop the functionality that the library provides. SHOULD DEVELOPERS USE THIRD-PARTY LIBRARIES?
Relying on library(abused) is not a good idea
- awesome ios github Contains all the popular libraries in Swift:+1:
- awesome swift site You can broswe popular libraries related to iOS
- Explore Swift Discover & find a curated list of popular & new libraries, top authors and trending discussions on kandi.
A package manager is a tool that simplifies the process of working with code from multiple sources.
- Centralised hosting of packages and source code with public server with access to developers or contributors
- Download the source code at the run time, so that we donβt need to include it in the repository
- Link the source code to our working repository by including source files
Download cocoapods
$ sudo gem install cocoapods
After finish download cocoapods, go to your root folder of your project and make pod file
$ pod init
Click into your pod file and edit
Image
After finish editing, update your pod file
$ pod install
You are GOOD TO GO πππ
- Getting started with Carthage to manage dependencies in Swift and iOS
- Carthage Tutorial: Getting Started
- Carthage
First, install Carthage through HomeBrew
$ brew install carthage
if already installed, check if there is latest version.
$ carthage update
Then, go to your root project folder, and do this
touch Cartfile
open cartfile, put library that you want to use
github "<owner>/<repo>" == <version>
Example
github "Alamofire/Alamofire" == 4.9.0
github "Alamofire/AlamofireImage" ~> 3.4
And then, do this
carthage update --platform iOS
After finish downloading it, go to Xcode -> Build phases
TBD
You are GOOD TO GO πππ
Enter url of library that you want to install
You are GOOD TO GO πππ
- SDWebImage - Downloading and caching images from the web
- Kingfisher - Downloading and caching images from the web
- Hero - Various kind of animation with using Segue
- Alamofire - Network Layer tool
- Moya - Network abstraction layer written in Swift
- RxSwift - Reactive Programming in Swift
- SwiftyJSON - JSON parsar Helper
- IQKeyboardManager - Easy to manage Keyboard settings
- SnapKit - Swift Auto Layout DSL for iOS
- Charts - Make Beutiful Charts in your App
- Quick/Nimble - Testing Library + Asynchronous tests purpose
- Periphery - A tool to identify unused code in Swift Projects
- ReactorKit - A framework for a reactive and unidirectional Swift application architecture
- SwiftGen - SwiftGen is a tool to automatically generate Swift code for resources of your projects (like images etc), to make them type-safe to use.
- etc...
Localization is the process of making your app support other languages. (Base language is English)
- Localization Apple
- Localization Apple Developer
- iOS Localization Tutorial
- Internationalizing Your iOS App: Getting Started
First, you have to check Use Base Internationalization
It might be checked
English is a base Language
After you check it, add languages that you want to support in your App
Then, you can check your language file like this!
Create Localizable.strings file into your project
Unlike Swift, the .strings file requires that each line terminate with a semicolon .strings file is where you can add translation data as key-value pairs
In your .strings file, check localization button and choose language
And then add Key - Value pairs for tanslation
To use localization, use NSLocalizedString to implement it
NSLocalizedString(<#T##key: String##String#>, comment: <#T##String#>)
- [key] - put (key - value) pair that you created in .strings file
- [comment] - It will help your translators significantly and result in better translations
Simple example below
@IBAction func showAlert() {
let alertTitle = NSLocalizedString("Welcome", comment: "")
let alertMessage = NSLocalizedString("How are you", comment: "")
let cancelButtonText = NSLocalizedString("Cancel", comment: "")
let signupButtonText = NSLocalizedString("Signup", comment: "")
let alert = UIAlertController(title: alertTitle, message: alertMessage, preferredStyle: UIAlertController.Style.alert)
let cancelAction = UIAlertAction(title: cancelButtonText, style: UIAlertAction.Style.cancel, handler: nil)
let signupAction = UIAlertAction(title: signupButtonText, style: UIAlertAction.Style.default, handler: nil)
alert.addAction(cancelAction)
alert.addAction(signupAction)
present(alert, animated: true, completion: nil)
}
After that, we have to test if localization is working correctly or not
To test it, you can do either Edit Scheme or New Scheme
go to Run section, and change App Language
After finish setting Scheme try to run it!
You are GOOD TO GO πππ
- localazy localization tool for iOS and macOS apps. Supporting .strings, .stringsdict, .plist and XLIFF files.
- locastudio Analyze, review, and edit your app translations.
Accessibility is all about making the iPhone, iPod touch, and iPad work for as wide a range of people as possible. That can include the very young, the very old, people brand new to computers and mobile devices, and also people with disabilities and special needs.
-
Designing your app for accessibility makes it easier to write functional tests, whether youβre using the UI Testing in Xcode.
-
Youβll also broaden your market and user base by making your app usable by a larger group.
-
Implementing accessibility in your app shows youβre willing to go the extra mile for every user, and thatβs a good thing.
To use accessibility, you have to enable this
For most UIKit classes, the default is true, but for UILabel itβs false
label.isAccessibilityElement = true
- accessibilityLabel - short description of control e.g. "Save" for button, "Rating" for label
- accessibilityHint - helps the user to understand result of the action e.g "Save the documents"
- accessibilityTraits - collection of constants that describe the type of control and/or hot it should be treated
- accessibilityValue - Used to describe the value of a none-label UI component e.g. "50%" for progress bar
GCD(Grand Central Dispatch) is a low-level API for managing concurrent operations. It can help you improve your appβs responsiveness by deferring computationally expensive tasks to the background.
An object that manages the execution of tasks serially or concurrently on your app's main thread or on a background thread.
We can say main is a serial queue
We can say global is a concurrent queue
Concurrency & Thread Safety in Swift Thread Safety in Swift
- Dispatch Barrier
Use a barrier to synchronize the execution of one or more tasks in your dispatch queue.
Dispatch Barrier Apple Documentation
- Dispatch Semaphore
Dispatch Semaphore Apple Documentation
- NSLock
An object that coordinates the operation of multiple threads of execution within the same application.
The work you want to perform, encapsulated in a way that lets you attach a completion handle or execution dependencies.
DispatchWorkItem Apple Document
NSOperation Apple Documentation
NSOperationQueue Apple Documentation
Thread Sanitizer is a tool to identifies the potential thread-related corruption issues. And it is a good way to find the Readers and Writers problem in your application.
Go to this Option and Click EDIT SCHEME... π
And then go to RUN and check THREAD SANITIZER π
Test Double is a generic term for any case where you replace a production object for testing purposes.
- Mocks - Mocks are pre-programmered with expectations which form a specification of the calls they are expected to receive. They can throw an exception if they receive a call they don't expect and are checked during verification to ensure they got all the calls they were expecting.
// exaple code will update
- Fake - Objects actually have working implementations, but usually take some shortcut which makes them not suitable for production.
// exaple code will update
- Spies - Spies are stubs that also record some information based on how they were called. One form of this might be an email service that records how many messages it was sent.
// exaple code will update
- Stubs - Stubs provide canned answers to calls made during the test, usually not responding at all to anything outside what's programmed in for the test.
// exaple code will update
- Dummy - Objects are passed around but never actually used. Usually they are just used to fill parameter lists.
// exaple code will update
Debugging in Xcode 13: Tips & Tricks (2022) β iOS
Use expression
at the beginning and then add whatever what you want to change into. It will change in debugging stage π
If we want to know whenever hit certain function, use symbolic breakpoint
Test Driven Development
Normally in complicated Application, build time for testing is crazy therefore, TDD spent most of time in building the project.
Here are useful ways that we can reduce build time when we are working with TDD style.
un-check Debugger option
Enter below code in your terminal, be sure to restart Xcode after enter this code and Command + B
defaults write com.apple.dt.Xcode ShowBuildOperationDuration YES
BDD improves communication between tech and non-tech teams and stakeholders. In BDD, tests are more user-focused and based on the systemβs behavior.
Behavior Driven Development
- Encouraging collaboration across roles to build shared understanding of the problem to be solved
- Working in rapid, small iterations to increase feedback and the flow of value
- Producing system documentation that is automatically checked against the systemβs behaviour
First, take a small upcoming change to the system β a User Story β and talk about concrete examples of the new functionality to explore, discover and agree on the details of whatβs expected to be done.
Next, document those examples in a way that can be automated, and check for agreement.
Finally, implement the behaviour described by each documented example, starting with an automated test to guide the development of the code.
- Behaviour-Driven Development
- What is BDD? An Introduction to Behavioral Driven Development
- The WHY Behind the Code: BDD vs. TDD
Before start your Testing, add coverage will be a good option to show the result of test
First, check code coverage
Then, go to EDIT SHEME, check like this
Integration Testing Swift by Sundell
ππ Recommend Book ππ
Book Name | Authors Name |
---|---|
iOS Unit Testing by Example | Jon Reid |
UI Testing, also known as GUI Testing is basically a mechanism meant to test the aspects of any software that a user will come into contact with. This usually means testing the visual elements to verify that they are functioning according to requirements β in terms of functionality and performance. UI testing ensures that UI functions are bug-free.
Robot testing is a test design pattern that makes you to create stable, readable, and maintainable tests.
- Robot Pattern Testing for XCUITestπ
- Testing Robots- JAKE WHARTON
- Robot Testing Pattern - Overview
Snapshot Testing is a testing technique that can be used in Swift (and other programming languages) to test the user interface (UI) of an application.
In Snapshot Testing, a snapshot of the UI is taken and compared to a previously saved snapshot to check if any changes have been made. This technique can be used to ensure that changes to the UI do not break the existing functionality of the application.
With using Environment Variable in Xcode, we can directly re-capture failing snapshot test cases
SNAPSHOT_TESTING = YES
TestFlight makes it easy to invite users to test your apps and App Clips and collect valuable feedback before releasing your apps on the App Store.
CI and CD stand for continuous integration and continuous delivery/continuous deployment
- Why is CI/CD important?
- What is CI/CD? Continuous integration and continuous delivery explained
- Whatβs the difference between agile, CI/CD, and DevOps?
The easiest way to build and release mobile apps.
Jenkins is most popular CI/CD tools
Jira is project management software first and foremost, but it began its life in 2002 as an issue tracking platform for software developers
You can integrate Circle CI into Github repo, therefore we can use it in PR.
-
Danger runs after your CI, automating your team's conventions surrounding code review.
-
This provides another logical step in your process, through this Danger can help lint your rote tasks in daily code review.
-
You can use Danger to codify your team's norms, leaving humans to think about harder problems.
Codemagic - Build, test and deliver your mobile projects 20% faster.
WWDC21 Apple released Xcode Cloud for continuous integration
For more info, go to Apple Developer Website
-
Tuist is a command line tool that helps you generate, maintain and interact with Xcode projects.
Requirement
- Full Apple Developoment Program($99)
- Physical IPhone Device to test IAP
Simulator can not test IAP!!
Paywall is a way to restrict access to their information so that only paying users can use it.
Lots of developer recommend 80% - (Paywall) - 20%
TBD
For more info about getting start of IAP, go here π
-
Notifications are an integral way of conveying information to the user outside of an app.
-
Notifications can be either local or remote. The app on the device schedules and configures local notifications. In contrast, a server sends remote notifications using Apple Push Notification Service (APNS)
-
You can configure both local and remote notifications using the UserNotifications framework.
If you set repeatation less than 60 sec, it will cause ERROR!
APNS stands for Apple Push Notification service
First, go to Signing & Capabilities and add two features like this
Functional Reactive Programming
- RxSwift raywenderlich
- RxSwift - Github Repository
- RxSwift - Website
ππ Recommend Book ππ
Book Name | Authors Name |
---|---|
RxSwift: Reactive Programming with Swift | raywenderlich Tutorial Team |
Combine released on iOS13 from Apple for Functional Reactive Programming.
ππ Recommend Book ππ
Book Name | Authors Name |
---|---|
Combine: Asynchronous Programming with Swift | raywenderlich Tutorial Team |
RxCombine provides bi-directional type bridging between RxSwift and Apple's Combine framework.
Security secure the data your app manages, and control access to your app.
Check below for more detail about iOS Security as well as Application security
- Introduction to Apple platform security
- iOS Security
- Apple Developer Doc about Security
- iOS App Security: Best Practices
- Keychain For Sensitive Data Storage
- Application Transport Security Layer(TSL)
- SSL Pinning
- Jailbroken Device Check
- Disable Debug Logs
- Third-Party Library Usage Check
- Code Obfuscation
- Cryptography
- Biometric Access
When a mobile app communicates with a server, it uses SSL(Secure Socket Layer) pinning technique for protecting the transmitted data against tampering and eavesdropping.
- A browser attempts to connect with a website which is secured with a SSL. The browser then requests the web server to identify itself.
- Web server then sends the browser its SSL certificate copy.
- The browser checks if the SSL certificate must be trusted. If it can be, a message is sent to the web server.
- Web server then sends back an acknowledgement to begin the SSL encrypted session.
- The encrypted data is then finally shared between the browser and web server.
- Pin the certificate β you can download the serverβs certificate and bundle them in the app. At the runtime, the app compares the server certificate to ones that you have embedded.
- Pin the public key β you can retrieve the public key of certificate in the code as string. At the runtime, the application compared the certificateβs public key to one which is hard-coded in the code.
func urlSession(_ session: URLSession, didReceive challenge: URLAuthenticationChallenge, completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
if (challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodServerTrust) {
if let serverTrust = challenge.protectionSpace.serverTrust {
var secresult = SecTrustResultType.invalid
let status = SecTrustEvaluate(serverTrust, &secresult)
if (errSecSuccess == status) {
if let serverCertificate = SecTrustGetCertificateAtIndex(serverTrust, 0) {
let serverCertificateData = SecCertificateCopyData(serverCertificate)
let data = CFDataGetBytePtr(serverCertificateData);
let size = CFDataGetLength(serverCertificateData);
let cert1 = NSData(bytes: data, length: size)
let file_der = Bundle.main.path(forResource: "name-of-cert-file", ofType: "cer")
if let file = file_der {
if let cert2 = NSData(contentsOfFile: file) {
if cert1.isEqual(to: cert2 as Data) { completionHandler(URLSession.AuthChallengeDisposition.useCredential, URLCredential(trust:serverTrust))
return
}
}
}
}
}
}
}
// Pinning failed completionHandler(URLSession.AuthChallengeDisposition.cancelAuthenticationChallenge, nil)
}
If you are using above version, this code should be changed
First, Download SSL certificate to your project folder
https://www.yourdomain.com (NOT IN THIS WAY)
openssl s_client -showcerts -connect yourdomain.com:443 < /dev/null | openssl x509 -outform DER > yourdomain.cer
Make a SessionManager to get SSL Pinning
let sessionManager: SessionManager = {
let serverTrustPolicies: [String: ServerTrustPolicy] = ["yourdomain.com": .pinCertificates(certificates: ServerTrustPolicy.certificates(),
validateCertificateChain: true,
validateHost: true)]
return SessionManager(serverTrustPolicyManager: ServerTrustPolicyManager(policies: serverTrustPolicies))
}()
request from sessionManager, if it is invalid, print error
sessionManager.request("https://yourdomain.com").responseString { (dataResponse) in
switch dataResponse.result {
case .failure(let err):
print(err)
case .success(let val):
print(val)
if let headerFields = dataResponse.response?.allHeaderFields {
print(headerFields)
}
}
}
TrustKit makes it easy to deploy SSL public key pinning
Code obfuscation is the act of deliberately obscuring source code, making it very difficult for humans to understand, and making it useless to hackers who may have ulterior motives.
Apple made a big change when it released the iPhone X: It ditched Touch ID fingerprint security for a new face-based biometric sign-on tool called Face ID. The fingerprint scanner on most post-iPhone X Apple products is gone, and in its place is a new camera array capable of capturing a face map that is, according to Apple, 20 times less likely to be hacked than a Touch ID fingerprint.
To use Face ID, Add Privacy - Face ID Usage Description into your info.plist file in your project
import LocalAuthentication, which can allow you to implement Biometric Access
import LocalAuthentication
After that, using LAContext() we can implement Face ID
Here are simple example that how Face ID can impelement
@IBAction private func isTouched(_ sender: UIButton!) {
let context = LAContext()
var error: NSError? = nil
if context.canEvaluatePolicy(.deviceOwnerAuthenticationWithBiometrics, error: &error) {
let reason = "touch id"
context.evaluatePolicy(.deviceOwnerAuthenticationWithBiometrics, localizedReason: reason) { [weak self](success, error) in
DispatchQueue.main.async {
guard success, error == nil else {
// If Fail
let alert = UIAlertController(title: "FAceID Fail", message: "error", preferredStyle: .alert)
let action = UIAlertAction(title: "cancle", style: .cancel, handler: nil)
alert.addAction(action)
self?.present(alert, animated: true, completion: nil)
return
}
// If success
let vc = UIViewController()
vc.title = "hi"
vc.view.backgroundColor = .blue
self?.present(vc, animated: true, completion: nil)
}
}
} else {
// If device is not supporting Face ID
}
}
Error Handling is your own part
You are GOOD TO GO πππ
Still we need to study Objective-C for legacy code which is still remain in our project!
Here are some useful website that you can study about simple concept of Obj-C!!
ππ Recommend Book ππ
Book Name | Authors Name |
---|---|
Objective-C Programming: The Big Nerd Ranch Guide | Aaron Hillegass, Mikey Ward |
Can we really say "Our application is built with pure Swift"?. NO! Lots of Objective-C codes are running in the background to built swift.
Here is a example that you can try
Simply create a pure swift application and use this lines in debug console!!
break set -r "-\[.*\]"
break set -r DebugMode
break set -r Emoji
Use one of above line when you want to find out how many Objective-C codes are consist in simple pure swift application!!
Bridging header means access classes and other declarations from your Objective-C code in Swift.
Importing Objective-C into Swift Apple Documentation
Find your common error here
I listed some of the useful & interesting stuff related with Swift
Here are the useful blog list which you can get references & knowledges about iOS development
- SwiftLee π
- Apple Developer Find recent technique with videos and example codes!!
- appinventiv Including iOS and others!!
- Continue adding lists...
You can check the iOS Version adoption in this site
SwiftPlayground - Online Swift Playground
Copy this code and Paste into your controller
#if canImport(SwiftUI) && DEBUG
import SwiftUI
struct SwiftLeeViewRepresentable: UIViewRepresentable {
func makeUIView(context: Context) -> UIView {
return UIStoryboard(name: "Main", bundle: Bundle.main).instantiateInitialViewController()!.view
}
func updateUIView(_ view: UIView, context: Context) {
}
}
@available(iOS 13.0, *)
struct SwiftLeeViewController_Preview: PreviewProvider {
static var previews: some View {
SwiftLeeViewRepresentable()
}
}
#endif
Enable canvas option like this
You are GOOD TO GO πππ
You can compare changes based on Swift Verison
This will be helful when you are running out of storage in your mac
# 1
echo "Removing Derived Data..."
rm -rf ~/Library/Developer/Xcode/DerivedData/
# 2
echo "Removing Device Support..."
rm -rf ~/Library/Developer/Xcode/iOS\ DeviceSupport
rm -rf ~/Library/Developer/Xcode/watchOS\ DeviceSupport
rm -rf ~/Library/Developer/Xcode/tvOS\ DeviceSupport
# 3
echo "Removing old simulators..."
xcrun simctl delete unavailable
# 4
echo "Removing caches..."
rm -rf ~/Library/Caches/com.apple.dt.Xcode
rm -rf ~/Library/Caches/org.carthage.CarthageKit
# 5
if command -v pod &> /dev/null
then
# 6
pod cache clean --all
fi
echo "Done!"
After writing, run it with this command
chmod u+x clean-xcode.sh
And then
./clean-xcode.sh
This will cleans out derived data, device support, simulators and caches. So that once you execute it, You have to build your project AGAIN
For More Info, visit here
check this out here
Check this site for more info!
Since Xcode 13(BETA), you can find Vim in Preference -> Text Editing -> Editing -> Enable Vim Key bindings
this feature deprecated in Xcode 13(BETA)
how-to-write-a-readme will help you to write a README.md file more dynamically π
Also you can edit Readme.md file with VSCode Extension! Check out in VSCode!
This README.md file is written by Jungpyo Hong (Dennis) email: ghdwjdvy96@gmail.com