# Objective-C

Objective-C is a C programming language with object-oriented capabilities and a dynamic runtime.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Codebase Exploration with AI \[SUBSCRIBER\]

DevFeed: [Codebase Exploration with AI \[SUBSCRIBER\]](<https://devfeed.tech/articles/codebase-exploration-with-ai-subscriber-91867.md>)

Original publisher: [Read original article](<https://www.kodeco.com/ios/paths/ai-assisted-ios-dev/53684539-codebase-exploration-with-ai>)

Author: ifeli

Published: 2026-10-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Kodeco](<https://devfeed.tech/sources/kodeco-high-quality-programming-tutorials-ios-android-swift-kotlin-unity-and-more.md>)

Topics: [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [exploration](<https://devfeed.tech/tags/exploration.md>), [feature](<https://devfeed.tech/tags/feature.md>), [human-in-the-loop](<https://devfeed.tech/tags/human-in-the-loop.md>), [independent](<https://devfeed.tech/tags/independent.md>), [ios](<https://devfeed.tech/tags/ios.md>), [modernization](<https://devfeed.tech/tags/modernization.md>), [multimodal-module](<https://devfeed.tech/tags/multimodal-module.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [risks](<https://devfeed.tech/tags/risks.md>), [subscriber](<https://devfeed.tech/tags/subscriber.md>), [swift](<https://devfeed.tech/tags/swift.md>), [swiftui](<https://devfeed.tech/tags/swiftui.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>), [testing](<https://devfeed.tech/tags/testing.md>), [uikit](<https://devfeed.tech/tags/uikit.md>)

### AI overview

Explore an unfamiliar iOS codebase with focused AI questions, then verify proposed codebase maps and technical-debt findings against the source. The module emphasizes evaluating debt without treating age, Objective-C, or UIKit as problems by themselves; planning incremental Objective-C-to-Swift and UIKit-to-SwiftUI modernization without rewriting the app; and preparing for a feature change by tracing dependencies, risks, testing gaps, and open questions. AI assists exploration and review, while people verify findings and make decisions.

### Source excerpt

Explore an unfamiliar legacy iOS codebase with AI without treating its answers as authoritative. You will verify a codebase map and technical-debt findings against the source, create a high-level Objective-C-to-Swift and UIKit-to-SwiftUI modernization plan, and investigate whether the app is ready for a safe feature change.

## MacSync info-stealing malware hides malicious commands in an iCloud calendar

DevFeed: [MacSync info-stealing malware hides malicious commands in an iCloud calendar](<https://devfeed.tech/articles/macsync-info-stealing-malware-hides-malicious-commands-in-an-icloud-calendar-59882.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/09/25/macsync-info-stealing-malware-for-macos/>)

Author: Sinisa Markovic

Published: 2026-09-25T09:22:45Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [Malware](<https://devfeed.tech/topics/malware.md>), [Security](<https://devfeed.tech/topics/security.md>), [backdoor](<https://devfeed.tech/topics/backdoor.md>), [Shell](<https://devfeed.tech/topics/shell.md>), [file](<https://devfeed.tech/topics/file.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Server](<https://devfeed.tech/topics/server.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [apple](<https://devfeed.tech/tags/apple.md>), [backdoor](<https://devfeed.tech/tags/backdoor.md>), [clickfix](<https://devfeed.tech/tags/clickfix.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [crypto](<https://devfeed.tech/tags/crypto.md>), [data](<https://devfeed.tech/tags/data.md>), [files](<https://devfeed.tech/tags/files.md>), [kaspersky](<https://devfeed.tech/tags/kaspersky.md>), [mac](<https://devfeed.tech/tags/mac.md>), [macos](<https://devfeed.tech/tags/macos.md>), [malware](<https://devfeed.tech/tags/malware.md>), [news](<https://devfeed.tech/tags/news.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>), [server](<https://devfeed.tech/tags/server.md>), [shell](<https://devfeed.tech/tags/shell.md>), [swift](<https://devfeed.tech/tags/swift.md>), [telegram](<https://devfeed.tech/tags/telegram.md>), [x](<https://devfeed.tech/tags/x.md>), [zsh](<https://devfeed.tech/tags/zsh.md>)

### AI overview

A MacSync malware variant for macOS uses a more complex infection chain involving binary droppers and loaders. In one campaign, malicious commands were hidden in a public iCloud calendar and used to download additional payloads. The malware targets credentials, cryptocurrency wallet data, and files.

### Source excerpt

A new MacSync variant targets Mac users with an infostealer and persistent backdoor designed to steal credentials, crypto wallet data, and files, according to Kaspersky. Researchers found the malware spreading through a crypto wallet app called Toria, which had its own website and was promoted on X and Telegram. MacSync is a family of Mac malware that emerged in 2025 as Mac.c and was later renamed. Early versions used AppleScripts that closely resembled the AMOS ... More -> The post MacSync info-stealing malware hides malicious commands in an iCloud calendar appeared first on Help Net Security.

## MacSync under the microscope: new delivery methods and a new payload

DevFeed: [MacSync under the microscope: new delivery methods and a new payload](<https://devfeed.tech/articles/macsync-under-the-microscope-new-delivery-methods-and-a-new-payload-59229.md>)

Original publisher: [Read original article](<https://securelist.com/macsync-new-version/121383/>)

Author: Sergey Puzan

Published: 2026-09-24T10:00:21Z

Content type: article

Language: en

Sources: [Securelist](<https://devfeed.tech/sources/securelist.md>)

Topics: [Malware](<https://devfeed.tech/topics/malware.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [backdoor](<https://devfeed.tech/topics/backdoor.md>), [Social engineering](<https://devfeed.tech/topics/social-engineering.md>), [ClickFix](<https://devfeed.tech/topics/clickfix.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Script](<https://devfeed.tech/topics/script.md>), [Shell](<https://devfeed.tech/topics/shell.md>)

Tags: [apple-macos](<https://devfeed.tech/tags/apple-macos.md>), [backdoor](<https://devfeed.tech/tags/backdoor.md>), [clickfix](<https://devfeed.tech/tags/clickfix.md>), [cryptocurrencies](<https://devfeed.tech/tags/cryptocurrencies.md>), [full](<https://devfeed.tech/tags/full.md>), [infostealers](<https://devfeed.tech/tags/infostealers.md>), [large](<https://devfeed.tech/tags/large.md>), [macos](<https://devfeed.tech/tags/macos.md>), [macsync](<https://devfeed.tech/tags/macsync.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-descriptions](<https://devfeed.tech/tags/malware-descriptions.md>), [malware-technologies](<https://devfeed.tech/tags/malware-technologies.md>), [medium](<https://devfeed.tech/tags/medium.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [script](<https://devfeed.tech/tags/script.md>), [shell](<https://devfeed.tech/tags/shell.md>), [social-engineering](<https://devfeed.tech/tags/social-engineering.md>), [swift](<https://devfeed.tech/tags/swift.md>), [thumbnail](<https://devfeed.tech/tags/thumbnail.md>), [trojan](<https://devfeed.tech/tags/trojan.md>), [trojan-stealer](<https://devfeed.tech/tags/trojan-stealer.md>), [unix-and-macos-malware](<https://devfeed.tech/tags/unix-and-macos-malware.md>)

### AI overview

This report examines a new MacSync macOS infostealer infection chain observed in September 2026. It describes a shift from script-based droppers to binary payload delivery, malware modules written in Objective-C and Swift, and the use of iCloud during infection. MacSync is distributed through malware-as-a-service, social engineering, fake applications, and ClickFix-style attacks.

### Source excerpt

We look at a new version of the MacSync macOS stealer with a backdoor module that targets crypto enthusiasts and developers.

## Swift 6 Gave Me Zero Warnings, but Two Objective-C Callbacks Still Crashed at Runtime

DevFeed: [Swift 6 Gave Me Zero Warnings, but Two Objective-C Callbacks Still Crashed at Runtime](<https://devfeed.tech/articles/swift-6-gave-me-zero-warnings-but-two-objective-c-callbacks-still-crashed-at-runtime-58017.md>)

Original publisher: [Read original article](<https://hackernoon.com/swift-6-gave-me-zero-warnings-but-two-objective-c-callbacks-still-crashed-at-runtime?source=rss>)

Author: Amana

Published: 2026-09-22T14:42:08Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Swift](<https://devfeed.tech/topics/swift.md>), [Actor](<https://devfeed.tech/topics/actor.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Xcode](<https://devfeed.tech/topics/xcode.md>), [Closure](<https://devfeed.tech/topics/closure.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [actor](<https://devfeed.tech/tags/actor.md>), [amana](<https://devfeed.tech/tags/amana.md>), [apple](<https://devfeed.tech/tags/apple.md>), [bgtaskscheduler](<https://devfeed.tech/tags/bgtaskscheduler.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [dynamic-actor-isolation](<https://devfeed.tech/tags/dynamic-actor-isolation.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-development](<https://devfeed.tech/tags/ios-development.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [shipaton](<https://devfeed.tech/tags/shipaton.md>), [swift](<https://devfeed.tech/tags/swift.md>), [swift-6](<https://devfeed.tech/tags/swift-6.md>), [swift-concurrency](<https://devfeed.tech/tags/swift-concurrency.md>)

### AI overview

The article examines two runtime crashes caused by Swift 6 actor isolation interacting with Objective-C callbacks from BGTaskScheduler and PhotoKit. It explains why the compiler produced no warnings, how queue and isolation mismatches caused the crashes, and how the fixes were reproduced and validated.

### Source excerpt

How two Objective-C callbacks triggered Swift 6 actor-isolation crashes despite zero compiler warnings, and how the bugs were reproduced and fixed.

## The Future of KMP's iOS Interop - Daniel Bertoldi

DevFeed: [The Future of KMP's iOS Interop - Daniel Bertoldi](<https://devfeed.tech/articles/the-future-of-kmp-s-ios-interop-daniel-bertoldi-38329.md>)

Original publisher: [Read original article](<https://touchlab.co/the-future-of-kmps-ios-interop>)

Published: 2026-06-12T00:00:00Z

Content type: comparison

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>)

Tags: [compare](<https://devfeed.tech/tags/compare.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [interop](<https://devfeed.tech/tags/interop.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [native](<https://devfeed.tech/tags/native.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [production](<https://devfeed.tech/tags/production.md>), [skie](<https://devfeed.tech/tags/skie.md>), [swift](<https://devfeed.tech/tags/swift.md>), [swift-export](<https://devfeed.tech/tags/swift-export.md>)

### AI overview

This comparison examines Kotlin Multiplatform iOS interoperability through Kotlin's experimental Swift Export and the Objective-C bridge enhanced by SKIE. It compares their generated output, capabilities, limitations, and tradeoffs.

### Source excerpt

Kotlin's new Swift Export feature promises to eliminate the Objective-C middleman and generate native Swift APIs directly from your KMP code. But with SKIE already solving many of the same pain points in production today, which approach should your team bet on? We break down the capabilities, limitations, and tradeoffs of both.

## GSoC 2025: Usability Improvements for the Undefined Behavior Sanitizer

DevFeed: [GSoC 2025: Usability Improvements for the Undefined Behavior Sanitizer](<https://devfeed.tech/articles/gsoc-2025-usability-improvements-for-the-undefined-behavior-sanitizer-43122.md>)

Original publisher: [Read original article](<https://blog.llvm.org/posts/2025-09-01-gsoc-ubsan-trap-messages/>)

Author: Anthony Tran

Published: 2025-10-20T00:00:00Z

Content type: article

Language: en

Sources: [LLVM Project](<https://devfeed.tech/sources/the-llvm-project-blog.md>)

Topics: [undefined\_behavior](<https://devfeed.tech/topics/undefined-behavior.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [C](<https://devfeed.tech/topics/c.md>), [C++](<https://devfeed.tech/topics/c-plus-plus.md>), [clang](<https://devfeed.tech/topics/clang.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [c](<https://devfeed.tech/tags/c.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [clang](<https://devfeed.tech/tags/clang.md>), [codegen](<https://devfeed.tech/tags/codegen.md>), [debug](<https://devfeed.tech/tags/debug.md>), [gsoc](<https://devfeed.tech/tags/gsoc.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [sanitizer](<https://devfeed.tech/tags/sanitizer.md>), [undefined-behavior](<https://devfeed.tech/tags/undefined-behavior.md>)

### AI overview

This article reports on Google Summer of Code 2025 work to improve the usability of trapping Undefined Behavior Sanitizer (UBSan). It explains how trapping mode supports kernel, embedded, and production-hardening use cases, but previously made debugging undefined behavior difficult. The work improves the information available to developers when debugger execution stops on a sanitizer trap.

### Source excerpt

Introduction My name is Anthony and I had the pleasure of working on improving the Undefined Behavior Sanitizer this Google Summer of Code 2025. My mentors were Dan Liew and Michael Buch. Background Undefined Behavior Sanitizer (UBSan) is a tool for detecting a subset of the undefined behaviors in the C, C++, and Objective-C languages at runtime. This project focused mainly on the trapping variant of UBSan, which is evoked through -fsanitize-trap=<...> along with -fsanitize=<...>. Trapping UBSan is a lighter-weight version of UBSan because upon detection of undefined behavior a trap instruction is executed rather than calling into a runtime library to handle the undefined behavior. This makes it more appealing for kernel, embedded, and production hardening use cases. For cases of undefined behavior that can be detected by UBSan, check out the official clang documentation. An issue with trapping UBSan prior to my work was that it was much harder to debug undefined behavior when it is detected when compared to the non-trapping mode. To illustrate this consider this C program that reads integers from the command line arguments and adds them. #include <stdlib.h>#include <stdio.h>int add(int a, int b) { return a + b;}int main(int argc, const char** argv) { if (argc < 3) return 1; int a = atoi(argv[1]); int b = atoi(argv[2]); int result = add(a, b); printf("Added %d + %d = %d\n", a, b, result); return 0;} If this program is compiled and executed using UBSan with its userspace runtime it provides helpful output diagnosing the problem and also allows execution to continue. $ bin/clang -fsanitize=undefined add.c -g -o add && ./add 2147483647 1add.c:5:13: runtime error: signed integer overflow: 2147483647 + 1 cannot be represented in type 'int'SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior add.c:5:13 Added 2147483647 + 1 = -2147483648 In contrast when using UBSan in trapping mode the program immediately terminates when undefined behavior is detected as shown below. $

## React Native 0.77 - New Styling Features, Android's 16KB page support, Swift Template

DevFeed: [React Native 0.77 - New Styling Features, Android's 16KB page support, Swift Template](<https://devfeed.tech/articles/react-native-0-77-new-styling-features-android-s-16kb-page-support-swift-template-48123.md>)

Original publisher: [Read original article](<https://reactnative.dev/blog/2025/01/21/version-0.77>)

Author: Vojtech Novak; Mazen Chami; Blake Friedman; Rob Hogan

Published: 2025-01-21T00:00:00Z

Content type: release

Language: en

Sources: [React Native Blog](<https://devfeed.tech/sources/react-native-blog.md>)

Topics: [React Native](<https://devfeed.tech/topics/react-native.md>), [Android](<https://devfeed.tech/topics/android.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Template](<https://devfeed.tech/topics/template.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [css](<https://devfeed.tech/tags/css.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [features](<https://devfeed.tech/tags/features.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [react-native](<https://devfeed.tech/tags/react-native.md>), [release](<https://devfeed.tech/tags/release.md>), [swift](<https://devfeed.tech/tags/swift.md>), [template](<https://devfeed.tech/tags/template.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

React Native 0.77 introduces new CSS styling capabilities for layout, sizing, and blending, adds Android 15 and 16KB page support, and updates the community template by migrating it to Swift while maintaining Objective-C compatibility.

### Source excerpt

Today we are excited to release React Native 0.77!

## Using Dart FFI and C for Objective-C and Swift Interoperability in Flutter iOS Apps

DevFeed: [Using Dart FFI and C for Objective-C and Swift Interoperability in Flutter iOS Apps](<https://devfeed.tech/articles/platform-channels-are-dead-objective-c-swift-interop-is-here-23986.md>)

Original publisher: [Read original article](<https://quickbirdstudios.com/blog/dart-swift-objective-c-interop/>)

Author: Marvin März

Published: 2023-12-11T15:43:49Z

Content type: tutorial

Language: en

Sources: [QuickBird Studios Blog](<https://devfeed.tech/sources/quickbird-studios-blog.md>)

Topics: [Dart](<https://devfeed.tech/topics/dart.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [C](<https://devfeed.tech/topics/c.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [c](<https://devfeed.tech/tags/c.md>), [dart](<https://devfeed.tech/tags/dart.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [interop](<https://devfeed.tech/tags/interop.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [ios](<https://devfeed.tech/tags/ios.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [platform](<https://devfeed.tech/tags/platform.md>), [post](<https://devfeed.tech/tags/post.md>), [swift](<https://devfeed.tech/tags/swift.md>)

### AI overview

This guide explains how Dart 2.18's Objective-C/Swift Interop lets Flutter applications call native iOS code from Dart through Dart FFI and C. It discusses limitations of platform channels, including duplicated boilerplate and maintenance concerns, and introduces the interop approach.

### Source excerpt

Dart 2.18 introduced Objective-C/Swift Interop. In this comprehensive guide, we explore how to seamlessly integrate native iOS code into your Flutter app using Dart FFI and C as an interoperability layer. The post Platform Channels are Dead! Objective-C/Swift Interop is Here! appeared first on QuickBird Studios.

## When iOS Engineers Should Use Kotlin Multiplatform's expect/actual Syntax

DevFeed: [When iOS Engineers Should Use Kotlin Multiplatform's expect/actual Syntax](<https://devfeed.tech/articles/why-ios-engineers-should-avoid-this-glorified-kmm-technique-34119.md>)

Original publisher: [Read original article](<https://artandscienceofcoding.com/science/avoid-this-kmm-technique/>)

Author: Derek Lee

Published: 2022-09-22T00:00:00Z

Content type: opinion

Language: en

Sources: [art and science of coding](<https://devfeed.tech/sources/art-and-science-of-coding.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>)

Tags: [guide](<https://devfeed.tech/tags/guide.md>), [kmm](<https://devfeed.tech/tags/kmm.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [science](<https://devfeed.tech/tags/science.md>)

### AI overview

This article argues that iOS engineers building multiplatform apps with Kotlin Multiplatform Mobile should generally write platform-dependent code in Swift instead of using the expect/actual syntax. It identifies building a multiplatform framework as the main case where the syntax may be worth considering and recommends consulting Apple's Objective-C documentation and Kotlin/Native headers when using it.

### Source excerpt

TL;DR If you're an iOS engineer who wants to build multiplatform apps using KMM, the few benefits of using the expect/actual syntax do not outweigh those of writing your platform-dependent code in Swift. The use-case for iOS engineers to consider leveraging expect/actual syntax would be when building a multiplatform framework. If you're going to use expect/actual, be sure to reference Apple's Objective-C documentation over Swift documentation and use the Kotlin/Native headers for the most accurate representation of the iOS APIs available in Kotlin. The expect/actual Syntax of Kotlin Multiplatform Mobile (KMM) The Kotlin Multiplatform SDK includes a syntactical construct integrated into JetBrains IDEs that engineers can use to define classes and functions that are expect -ed (pun intended) to have platform-specific implementations. The actual implementations are also written in Kotlin separately for Android and iOS. When looking at the code modules in a KMM project: within the KMM shared framework module, you first define a class or a function as expected. Then the actual implementations are written for each supported platform module. The following example illustrates what module the code is defined within for Android and iOS: The `common` module defines the expected classes and functions, and platform modules define the actual implementation. We looked at some simple examples in the last blog. These examples are helpful because they allow us to wrap our heads around the concept before diving into something more complicated. I want to take you on a journey of writing some code using this approach to illustrate how this can become more complicated in practice than expected. In fact, I'm going to make a bold statement and propose that there's only a single scenario where you, the iOS Engineer, should even consider using the expect/actual syntax. This post is part of a series on Kotlin Multiplatform: The iOS Engineer's Guide to Beginning Kotlin Multiplatform Development

## Getting Square's iOS build ready for Apple Silicon with Bazel

DevFeed: [Getting Square's iOS build ready for Apple Silicon with Bazel](<https://devfeed.tech/articles/getting-square-s-ios-build-ready-for-apple-silicon-with-bazel-15665.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/getting-squares-ios-build-ready-for-apple-silicon-with-bazel>)

Author: Jerry Marino

Published: 2022-01-27T20:00:00Z

Content type: tutorial

Language: en

Sources: [Square Corner](<https://devfeed.tech/sources/square-corner-blog-medium.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [build times](<https://devfeed.tech/topics/build-times.md>), [cpu](<https://devfeed.tech/topics/cpu.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [arm](<https://devfeed.tech/tags/arm.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [build](<https://devfeed.tech/tags/build.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [caching](<https://devfeed.tech/tags/caching.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [ios](<https://devfeed.tech/tags/ios.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [simulator](<https://devfeed.tech/tags/simulator.md>), [swift](<https://devfeed.tech/tags/swift.md>), [x86](<https://devfeed.tech/tags/x86.md>)

### AI overview

Square describes adapting its Bazel-based iOS build system for Apple Silicon by building and running iOS applications on the M1 simulator. The article explains the available development paths and why device builds and x86_64 builds under Rosetta 2 were not selected.

### Source excerpt

Building and running iOS builds using the M1 simulator

## An Approach for Migrating From Objective-C to Swift

DevFeed: [An Approach for Migrating From Objective-C to Swift](<https://devfeed.tech/articles/an-approach-for-migrating-from-objective-c-to-swift-25811.md>)

Original publisher: [Read original article](<https://www.steveonstuff.com/2022/01/13/migrating-from-objc-to-swift>)

Author: Steve Barnegren

Published: 2022-01-13T00:00:00Z

Content type: tutorial

Language: en

Sources: [Steve Barnegren](<https://devfeed.tech/sources/steve-barnegren.md>)

Topics: [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [tvOS](<https://devfeed.tech/topics/tvos.md>), [generic programming](<https://devfeed.tech/topics/generic-programming.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [enums](<https://devfeed.tech/tags/enums.md>), [generics](<https://devfeed.tech/tags/generics.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [ios](<https://devfeed.tech/tags/ios.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [optional](<https://devfeed.tech/tags/optional.md>), [swift](<https://devfeed.tech/tags/swift.md>), [types](<https://devfeed.tech/tags/types.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

This article shares lessons from transitioning a large iOS and tvOS application from Objective-C to Swift. It explains why simply adding new Swift code produced limited progress and caused Swift code to be constrained by Objective-C interoperability.

### Source excerpt

It feels like Swift is pretty ubiquitous across the Apple ecosystem now, but there's a lot of Objective-C out there. The larger and older the app, the more likely that there's still a bunch of Objective-C powering various bits behind the scenes.

## Kotlin Native -- Using swift, not Objective-C

DevFeed: [Kotlin Native -- Using swift, not Objective-C](<https://devfeed.tech/articles/kotlin-native-using-swift-not-objective-c-24746.md>)

Original publisher: [Read original article](<https://medium.com/yazio-engineering/kotlin-native-using-swift-not-objective-c-d7742c040539?source=rss----65bd178b00af---4>)

Author: Paul Woitaschek

Published: 2021-11-19T08:00:42Z

Content type: article

Language: en

Sources: [YAZIO](<https://devfeed.tech/sources/yazio-engineering-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [data-class](<https://devfeed.tech/tags/data-class.md>), [enums](<https://devfeed.tech/tags/enums.md>), [interop](<https://devfeed.tech/tags/interop.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [kotlin-native](<https://devfeed.tech/tags/kotlin-native.md>), [ksp](<https://devfeed.tech/tags/ksp.md>), [library](<https://devfeed.tech/tags/library.md>), [mapping](<https://devfeed.tech/tags/mapping.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [swift](<https://devfeed.tech/tags/swift.md>)

### AI overview

YAZIO uses Kotlin Native for shared feature logic, but Kotlin types exposed through Objective-C do not provide the Swift-native structs, property types, enums, or sealed classes its iOS API needs. The team has been manually mapping the public API into Swift, which produces a clean interface but adds substantial boilerplate. The excerpt proposes generating those mappings: KSP analyzes Kotlin syntax and provides hooks for code generation, while SwiftPoet generates Swift code. It describes an example that selects annotated classes, derives an enum name, converts contained declarations into enum cases, and writes a Swift file. The excerpt ends during setup guidance, so it does not establish the full implementation or its results.

### Source excerpt

Kotlin Native -- Using Swift, not Objective-C At YAZIO we use Kotlin Native Extensively. The business logic of all new app features is exclusively written in Kotlin. In its core, every screen has one ViewModel which exposes a single Flow<ViewState> that the Android App and the iOS can consume to render the state. On Android, rendering the view state is no burden because it's the language we use in the Android App anyways. However this is different for iOS. While Swift does interop with Objective-C, the public API as seen from Swift is bad. A simple data class is exported as a regular class. The properties are not native Swift types. What should be a Bool becomes a KotlinBoolean. What should be come a Double becomes a KotlinDouble. But what we want is most of the times a struct with Swift types. These are the lesser evils, the greater ones are enums and sealed classes. In Objective-C, they both become regular classes. And therefore lose all the advantages they have when used from Swift. But what we want is a Swift enum. To overcome these restrictions for quite some time our iOS team has created mappings. There is a whole target, dedicated to mapping the Objective-C classes to Swift. Basically when developing a new feature, the whole public API is manually mapped to Swift. This is good because the result is a clean Swift-native API. But that's bad because it's extreme boilerplate and a real productivity killer. What if we could directly generate these mappings and use code generation to handle that for us? Turns out: There are two tools available that make it possible. The first one is KSP. It is basically a library that lets you implement a Kotlin compiler plugin and it gives you hooks to analyze the Kotlin Syntax Tree and generate code based on it. The second one is SwiftPoet. SwiftPoet is a library you can use to generate Swift code from Kotlin, similar to what KotlinPoet and JavaPoet do. Okay, let's get our handy dirty. For the basic setup, just follow the tutorial

## Kotlin Native -- Using swift, not Objective-C

DevFeed: [Kotlin Native -- Using swift, not Objective-C](<https://devfeed.tech/articles/kotlin-native-using-swift-not-objective-c-26007.md>)

Original publisher: [Read original article](<https://medium.com/yazio-engineering/kotlin-native-using-swift-not-objective-c-d7742c040539?source=rss-fbf9b6d94e65------2>)

Author: Paul Woitaschek

Published: 2021-11-19T07:21:13Z

Content type: tutorial

Language: en

Sources: [Paul Woitaschek](<https://devfeed.tech/sources/stories-by-paul-woitaschek-on-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [data-class](<https://devfeed.tech/tags/data-class.md>), [enum](<https://devfeed.tech/tags/enum.md>), [enums](<https://devfeed.tech/tags/enums.md>), [interop](<https://devfeed.tech/tags/interop.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-compiler](<https://devfeed.tech/tags/kotlin-compiler.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [kotlin-native](<https://devfeed.tech/tags/kotlin-native.md>), [ksp](<https://devfeed.tech/tags/ksp.md>), [mapping](<https://devfeed.tech/tags/mapping.md>), [mappings](<https://devfeed.tech/tags/mappings.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [sealed-classes](<https://devfeed.tech/tags/sealed-classes.md>), [swift](<https://devfeed.tech/tags/swift.md>)

### AI overview

YAZIO uses Kotlin Native for shared feature logic, but Kotlin types exposed through Objective-C interop do not provide the Swift-native API the iOS team wants: data classes appear as classes with non-native property types, and enums and sealed classes lose their Swift enum behavior. The team has manually mapped the public API into Swift, producing a clean interface at the cost of substantial boilerplate. The excerpt proposes automating these mappings with KSP, which analyzes Kotlin symbols and enables code generation, and SwiftPoet, which generates Swift code from Kotlin. It begins an enum-generation example: derive the enum name from an annotated class, turn its contained declarations into enum cases, then build and write a Swift file. The setup details are cut off.

### Source excerpt

Kotlin Native -- Using Swift, not Objective-C At YAZIO we use Kotlin Native Extensively. The business logic of all new app features is exclusively written in Kotlin. In its core, every screen has one ViewModel which exposes a single Flow<ViewState> that the Android App and the iOS can consume to render the state. On Android, rendering the view state is no burden because it's the language we use in the Android App anyways. However this is different for iOS. While Swift does interop with Objective-C, the public API as seen from Swift is bad. A simple data class is exported as a regular class. The properties are not native Swift types. What should be a Bool becomes a KotlinBoolean. What should be come a Double becomes a KotlinDouble. But what we want is most of the times a struct with Swift types. These are the lesser evils, the greater ones are enums and sealed classes. In Objective-C, they both become regular classes. And therefore lose all the advantages they have when used from Swift. But what we want is a Swift enum. To overcome these restrictions for quite some time our iOS team has created mappings. There is a whole target, dedicated to mapping the Objective-C classes to Swift. Basically when developing a new feature, the whole public API is manually mapped to Swift. This is good because the result is a clean Swift-native API. But that's bad because it's extreme boilerplate and a real productivity killer. What if we could directly generate these mappings and use code generation to handle that for us? Turns out: There are two tools available that make it possible. The first one is KSP. It is basically a library that lets you implement a Kotlin compiler plugin and it gives you hooks to analyze the Kotlin Syntax Tree and generate code based on it. The second one is SwiftPoet. SwiftPoet is a library you can use to generate Swift code from Kotlin, similar to what KotlinPoet and JavaPoet do. Okay, let's get our handy dirty. For the basic setup, just follow the tutorial

## Improving Djinni - Snap Engineering

DevFeed: [Improving Djinni - Snap Engineering](<https://devfeed.tech/articles/improving-djinni-snap-engineering-56689.md>)

Original publisher: [Read original article](<https://eng.snap.com/improving_djinni>)

Author: Client Systems & Performance

Published: 2021-09-30T17:00:00Z

Content type: article

Language: en

Sources: [Snap](<https://devfeed.tech/sources/snap.md>)

Topics: [C++](<https://devfeed.tech/topics/c-plus-plus.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [cross-platform](<https://devfeed.tech/topics/cross-platform.md>), [Java](<https://devfeed.tech/topics/java.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>)

Tags: [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [decoding](<https://devfeed.tech/tags/decoding.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [github](<https://devfeed.tech/tags/github.md>), [java](<https://devfeed.tech/tags/java.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>)

### AI overview

Snap describes improvements to Djinni, its C++ cross-platform middleware for generating bridging code between C++ and languages such as Java and Objective-C. The article covers performance, stability, maintenance, and optimization work, including a bottleneck in string encoding and decoding across the JNI boundary.

### Source excerpt

Improving Djinni C++ is an important part of Snap's client development strategy due to its portability along with its ability to utilize the full potential of client hardware. It powers Snap's Lens technology which is used in the Snapchat mobile app, Lens Studio, and Snap Camera. It also powers our voice and video calling, messaging, mobile UI frameworks, and a growing set of client infrastructure components.

## Developing on iOS and Android

DevFeed: [Developing on iOS and Android](<https://devfeed.tech/articles/developing-on-ios-and-android-15610.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/developing-on-ios-and-android>)

Author: Jesse Wilson

Published: 2019-04-22T19:00:00Z

Content type: article

Language: en

Sources: [Square Corner](<https://devfeed.tech/sources/square-corner-blog-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [development](<https://devfeed.tech/tags/development.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [swift](<https://devfeed.tech/tags/swift.md>)

### AI overview

This article describes the convergence of iOS and Android development and the redundancy of maintaining separate implementations. It presents cross-team code reviews and an incremental multiplatform Kotlin experiment, beginning with replacing Objective-C persistence code using Kotlin/Native and SQLDelight.

### Source excerpt

The convergence of iOS and Android development

## How We Develop New Features Using Offsites and Clean Architecture

DevFeed: [How We Develop New Features Using Offsites and Clean Architecture](<https://devfeed.tech/articles/how-we-develop-new-features-using-offsites-and-clean-architecture-2052.md>)

Original publisher: [Read original article](<https://developers.soundcloud.com/blog//how-we-develop-new-features-using-offsites-and-clean-architecture>)

Published: 2018-11-02T00:00:00Z

Content type: article

Language: en

Sources: [SoundCloud Backstage](<https://devfeed.tech/sources/soundcloud-backstage-blog.md>)

Topics: [iOS](<https://devfeed.tech/topics/ios.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [mvc](<https://devfeed.tech/topics/mvc.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [bug](<https://devfeed.tech/tags/bug.md>), [code](<https://devfeed.tech/tags/code.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [ios](<https://devfeed.tech/tags/ios.md>), [mvc](<https://devfeed.tech/tags/mvc.md>), [new-feature](<https://devfeed.tech/tags/new-feature.md>), [swift](<https://devfeed.tech/tags/swift.md>)

### AI overview

SoundCloud describes how its iOS team developed new features while modernizing a large legacy codebase containing Objective-C and Swift. The team adopted the VIPER architectural pattern, compared with MVC, and used it successfully for the Mini Player and later features. The article also explains how project kickoffs and focused offsites support feature planning, brainstorming, and team productivity.

### Source excerpt

The current SoundCloud iOS App was built back in 2014, resulting in a huge codebase consisting of both Objective-C and Swift, with multiple...

## Delegates vs Closure Callbacks

DevFeed: [Delegates vs Closure Callbacks](<https://devfeed.tech/articles/delegates-vs-closure-callbacks-25806.md>)

Original publisher: [Read original article](<https://www.steveonstuff.com/2018/08/16/delegates-vs-closure-callbacks>)

Author: Steve Barnegren

Published: 2018-08-16T00:00:00Z

Content type: comparison

Language: en

Sources: [Steve Barnegren](<https://devfeed.tech/sources/steve-barnegren.md>)

Topics: [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>)

Tags: [callback](<https://devfeed.tech/tags/callback.md>), [closure](<https://devfeed.tech/tags/closure.md>), [compare](<https://devfeed.tech/tags/compare.md>), [delegates](<https://devfeed.tech/tags/delegates.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [swift](<https://devfeed.tech/tags/swift.md>)

### AI overview

This comparison examines delegate and closure callback patterns in Swift, focusing on retain-cycle handling and managing callbacks from multiple instances. It finds delegates safer for weak-reference relationships, while closure callbacks are clearer when separating callbacks for multiple instances.

### Source excerpt

Remember how awesome the delegate pattern was in Objective-C? Enabling classes to be super reusable by delegating out the bits that you might want control over. There's a reason that it's so ubiquitous across Cocoa Touch, it's just so damn good!

## Artisanal Objective-C Sum Types

DevFeed: [Artisanal Objective-C Sum Types](<https://devfeed.tech/articles/artisanal-objective-c-sum-types-20448.md>)

Original publisher: [Read original article](<https://medium.com/twitch-news/artisanal-objective-c-sum-types-8ea1ab9da342?source=rss----3ae745429979--engineering>)

Author: Heath Borders

Published: 2018-05-14T18:49:35Z

Content type: tutorial

Language: en

Sources: [Twitch](<https://devfeed.tech/sources/twitch.md>)

Topics: [union types](<https://devfeed.tech/topics/union-types.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [enum](<https://devfeed.tech/topics/enum.md>), [Programming Language Type Systems](<https://devfeed.tech/topics/programming-language-type-systems.md>), [data type](<https://devfeed.tech/topics/data-type.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [arc](<https://devfeed.tech/tags/arc.md>), [block](<https://devfeed.tech/tags/block.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [c](<https://devfeed.tech/tags/c.md>), [callback](<https://devfeed.tech/tags/callback.md>), [class](<https://devfeed.tech/tags/class.md>), [combines](<https://devfeed.tech/tags/combines.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [enum](<https://devfeed.tech/tags/enum.md>), [error](<https://devfeed.tech/tags/error.md>), [generator](<https://devfeed.tech/tags/generator.md>), [generic](<https://devfeed.tech/tags/generic.md>), [generics](<https://devfeed.tech/tags/generics.md>), [implement](<https://devfeed.tech/tags/implement.md>), [interface](<https://devfeed.tech/tags/interface.md>), [ios](<https://devfeed.tech/tags/ios.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [structs](<https://devfeed.tech/tags/structs.md>), [swift](<https://devfeed.tech/tags/swift.md>), [twitch](<https://devfeed.tech/tags/twitch.md>), [types](<https://devfeed.tech/tags/types.md>), [union](<https://devfeed.tech/tags/union.md>), [value](<https://devfeed.tech/tags/value.md>)

### AI overview

Swift enums provide concise, compiler-checked sum types; a C union paired with an enum can represent them but does not prevent mismatched values. Because ARC does not allow Objective-C objects in unions, the article builds a class-based alternative: a base class and subclasses represent the variants, and a block-based `switchFoo:bar:` callback dispatches each variant. Unavailable initializers discourage direct construction, while `NS_REQUIRES_SUPER` helps flag subclasses that fail to call the base method if its signature changes. A separate generic `Switcher` class captures a return type at each call site, avoiding missed local assignments; the excerpt says this still leaves a single place where an assignment can be missed. The approach provides type checking for construction, processing, and unpacking, but requires substantial mechanical boilerplate; the author suggests generating the code. The supplied text is an excerpt.

### Source excerpt

A sum type combines many possible differently-typed values into a single value, expressed in Swift as an enum. https://medium.com/media/6217cfe231386e04ce2e7228080fae7a/href In C, we can achieve the power of Swift's enum with a combination of a C union and a C enum: https://medium.com/media/3f1696d38fcec2600a942ffbe03c8cd4/href First, I'm sure you notice Swift's enum is more concise, but it's also safer. In C, the compiler doesn't prevent us from either creating an example with a mismatched type or from consuming a union as a mismatched type: https://medium.com/media/82f0586deab20a07abc615a9e459028e/href Trying to mismatch our enum types in Swift won't compile. Yay! https://medium.com/media/03d37cc33364b48d851beb4ccf38a97d/href Unfortunately, in Objective-C, we can't use Objective-C objects in structs or unions in ARC, so we can't use our C sum type with Objective-C objects. However, we can build a similar construct by hand. First, we need a class to capture all of the distinct types, and expose them through a single block-based callback interface: https://medium.com/media/78216b190ad6501c26ad89d0864b1c5c/href We must declare forward references for our distinct types, which we'll define later. We mark new and init as NS_UNAVAILABLE so that consumers won't be able to instantiate our base class directly. If they use -Wobjc-designated-initializers, they won't be able to subclass our base class either (without importing ExamplePrivate.h, which we won't distribute to them). Next, we'll declare our distinct types: https://medium.com/media/329743de725ccd196c3f535306714cf9/hrefhttps://medium.com/media/1785598f614b3963a0a39ec81d8c5dac/href They're simply plain-old-objective-c-objects that extend our base class. Our base class and our distinct types all have switchFoo:bar:. The distinct types will simply call the respective callback block with self. The base class will have an empty implementation. We use NS_REQUIRES_SUPER on switchFoo:bar: because if we add another distinct

## Build Native Interfaces - Camera Edition

DevFeed: [Build Native Interfaces - Camera Edition](<https://devfeed.tech/articles/build-native-interfaces-camera-edition-19229.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/build-native-interfaces-module-camera-edition/>)

Author: Shai Almog

Published: 2018-04-03T00:00:00Z

Content type: article

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Code](<https://devfeed.tech/topics/code.md>), [configuration](<https://devfeed.tech/topics/configuration.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [native](<https://devfeed.tech/tags/native.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>)

### AI overview

A new course module explains how to build the Camera cn1lib and work with native interfaces. It covers Objective-C, callbacks, delegates, and configuration issues, providing broader guidance for native integration.

### Source excerpt

I discussed the new Camera cn1lib last week. One of the motivations for doing it (besides the request from an enterprise account) was that of a new course module. Last week I added a new module covering the process of building the camera cn1lib... We have several online videos (both in the course and outside of it) covering native interfaces. So why do we need another one? Working with native code is error prone & complex. A lot of the tutorials we built in the past ended up spending more time on configuration issues than on code. In this module I talked a lot about Objective-C, callbacks, delegates & more. If you are thinking about native integration this helps give a more rounded view of the options.

## Meltdown and Spectre Server Updates and Codename One Feature Updates

DevFeed: [Meltdown and Spectre Server Updates and Codename One Feature Updates](<https://devfeed.tech/articles/meltdown-and-other-updates-19365.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/meltdown-updates/>)

Author: Shai Almog

Published: 2018-01-16T00:00:00Z

Content type: article

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Server](<https://devfeed.tech/topics/server.md>), [IO](<https://devfeed.tech/topics/io.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Java](<https://devfeed.tech/topics/java.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Barcode](<https://devfeed.tech/topics/barcode.md>), [QR Code](<https://devfeed.tech/topics/qrcode.md>), [simulator](<https://devfeed.tech/topics/simulator.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [api](<https://devfeed.tech/tags/api.md>), [blog](<https://devfeed.tech/tags/blog.md>), [io](<https://devfeed.tech/tags/io.md>), [ios](<https://devfeed.tech/tags/ios.md>), [java](<https://devfeed.tech/tags/java.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [qr-code](<https://devfeed.tech/tags/qr-code.md>), [servers](<https://devfeed.tech/tags/servers.md>), [simulator](<https://devfeed.tech/tags/simulator.md>), [updates](<https://devfeed.tech/tags/updates.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

The post announces server updates in response to the Meltdown and Spectre chip vulnerabilities, with possible short-term downtime and limited expected impact on build speed because IO, rather than CPU speed, is the main bottleneck. It also mentions new Codename One libraries for Objective-C interoperability and Scandit barcode and QR code scanning, plus a push notification simulator feature.

### Source excerpt

I've been so busy I just don't have time to blog as much as I should. I do hope next month will be better in this regard (more on that below) but right now I have to make an important announcement. There are new chip vulnerabilities I'm sure you heard a lot about specifically Meltdown & Spectre. Thankfully we are at a layer that shouldn't be impacted by these issues but we need to update our servers and will be doing so over the course of the next few days (possibly more as patches get updated).

## Doppl Sample Update - Kevin Galligan

DevFeed: [Doppl Sample Update - Kevin Galligan](<https://devfeed.tech/articles/doppl-sample-update-kevin-galligan-38189.md>)

Original publisher: [Read original article](<https://touchlab.co/doppl-sample-update>)

Published: 2017-10-04T15:00:55Z

Content type: article

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [RxJava](<https://devfeed.tech/topics/rxjava.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Xcode](<https://devfeed.tech/topics/xcode.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-library](<https://devfeed.tech/tags/android-library.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [built-by-touchlab](<https://devfeed.tech/tags/built-by-touchlab.md>), [code-sharing](<https://devfeed.tech/tags/code-sharing.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [java](<https://devfeed.tech/tags/java.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [retrofit](<https://devfeed.tech/tags/retrofit.md>), [rxjava](<https://devfeed.tech/tags/rxjava.md>), [update](<https://devfeed.tech/tags/update.md>), [version](<https://devfeed.tech/tags/version.md>), [xcode](<https://devfeed.tech/tags/xcode.md>)

### AI overview

A progress update on Touchlab's Doppl libraries and sample apps. The update covers compatibility work for J2objc 2.0.4, redeployed libraries, Party Clicker, reactive Room architecture code, and planned work on RxJava 2, Retrofit 2, Xcode support, the Gradle plugin, Architecture Components, and Kotlin.

### Source excerpt

We're going through and updating Doppl libs & sample apps. For the next few months, we'll be working with 2.0.4 and locking down the libraries and versions.

## Fixing autocompletion on mixed Objective-C and Swift projects

DevFeed: [Fixing autocompletion on mixed Objective-C and Swift projects](<https://devfeed.tech/articles/fixing-autocompletion-on-mixed-objective-c-and-swift-projects-21621.md>)

Original publisher: [Read original article](<http://miqu.me/blog/2017/06/16/fixing-autocompletion-on-mixed-objective-c-and-swift-projects/>)

Author: Miguel Angel Quiñones

Published: 2017-06-16T22:55:27Z

Content type: tutorial

Language: en

Sources: [Miguel Quinones](<https://devfeed.tech/sources/miguel-quinones.md>)

Topics: [Swift](<https://devfeed.tech/topics/swift.md>), [cocoapods](<https://devfeed.tech/topics/cocoapods.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [2017](<https://devfeed.tech/tags/2017.md>), [apple](<https://devfeed.tech/tags/apple.md>), [bridging](<https://devfeed.tech/tags/bridging.md>), [bug](<https://devfeed.tech/tags/bug.md>), [cocoapods](<https://devfeed.tech/tags/cocoapods.md>), [code-completion](<https://devfeed.tech/tags/code-completion.md>), [debug](<https://devfeed.tech/tags/debug.md>), [ide](<https://devfeed.tech/tags/ide.md>), [import](<https://devfeed.tech/tags/import.md>), [index](<https://devfeed.tech/tags/index.md>), [indexer](<https://devfeed.tech/tags/indexer.md>), [issue](<https://devfeed.tech/tags/issue.md>), [latest-release](<https://devfeed.tech/tags/latest-release.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [project](<https://devfeed.tech/tags/project.md>), [projects](<https://devfeed.tech/tags/projects.md>), [swift](<https://devfeed.tech/tags/swift.md>), [wwdc](<https://devfeed.tech/tags/wwdc.md>), [xcode](<https://devfeed.tech/tags/xcode.md>)

### AI overview

In the author's mixed Objective-C/Swift project, Swift autocompletion could fail intermittently because SourceKit had trouble indexing a library header imported without its path in the bridging header. The workaround was to use a library-style import such as `#import "path-to-library/MyClass.h"` instead of `#import "MyClass.h"`; the latter still compiled but could break completion. To investigate, the excerpt describes checking the SourceKit service log for code-completion requests, taking the compiler arguments and source file from the log, and running a Swift frontend invocation to expose the failing header. The author was unsure whether the behavior was an indexer bug or an import inconsistency. An update says the issues seemed fixed in Xcode 9.0.1 and that the Internal menu no longer appeared accessible, limiting the relevance of the debugging-menu steps.

### Source excerpt

This year I had the privilege of attending WWDC for the first time. I knew the labs were very important, and I want to share a resolution to fix a problem for our big project at Peak: Autocompletion on Swift code was not working most of the time in the IDE, and with the help of an Apple engineer in the labs we got it sorted. Update on 30/10/2017: The issues described here seem to be fixed with latest release version of Xcode 9.0.1 (9A1004). Also the 'internal' menu doesn't seem to be accessible anymore. If you know how to access it I'd love to hear from you! The issue If you are using Xcode 8 or Xcode 9 (beta 1 as of this writing), when you have a project with mixed Objective-C and Swift, you might encounters problems with autocompletion inside the Swift code. We've had this intermitently and most recent IDE versions made work very difficult as we would not have any autocompletion for our Swift code, or it would work intermitently. Our gut feeling was that the bridging header had some classes that were causing SourceKit to fail, but we didn't know how to debug the issue nor provide good feedback for Apple to fix it. Our chance came while visiting the labs at the conference, and a very helpful and patient Apple engineer worked with our project to understand what was wrong. Bridging header imports It turns out that if you import classes from libraries (in our case using CocoaPods) omitting the path may result in Sourcekit unable to index properly. For example, a class in some library: #import "MyClass.h" Code will compile fine but your code completion in Swift side might break because the indexer fails when encountering this file. I'm still unsure if it's because of importing the file somewhere else differently or if it's just a bug in the indexer. Anyway, the way to work around it (Apple is supposedly aware of this) is to import with the framework or library style, including the path: #import "path-to-library/MyClass.h" How to debug The engineer kindly made a wrote u

## Fixing autocompletion on mixed Objective-C and Swift projects

DevFeed: [Fixing autocompletion on mixed Objective-C and Swift projects](<https://devfeed.tech/articles/fixing-autocompletion-on-mixed-objective-c-and-swift-projects-97441.md>)

Original publisher: [Read original article](<https://miqu.me/blog/2017/06/16/fixing-autocompletion-on-mixed-objective-c-and-swift-projects/>)

Published: 2017-06-16T22:55:27Z

Content type: article

Language: en

Sources: [Miguel Quinones](<https://devfeed.tech/sources/miguel-quinones.md>)

Topics: [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [cocoapods](<https://devfeed.tech/topics/cocoapods.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [2017](<https://devfeed.tech/tags/2017.md>), [apple](<https://devfeed.tech/tags/apple.md>), [bridging](<https://devfeed.tech/tags/bridging.md>), [cocoapods](<https://devfeed.tech/tags/cocoapods.md>), [code-completion](<https://devfeed.tech/tags/code-completion.md>), [debug](<https://devfeed.tech/tags/debug.md>), [import](<https://devfeed.tech/tags/import.md>), [indexer](<https://devfeed.tech/tags/indexer.md>), [objective-c](<https://devfeed.tech/tags/objective-c.md>), [swift](<https://devfeed.tech/tags/swift.md>), [tips](<https://devfeed.tech/tags/tips.md>), [wwdc](<https://devfeed.tech/tags/wwdc.md>), [xcode](<https://devfeed.tech/tags/xcode.md>)

### AI overview

In mixed Objective-C and Swift projects using Xcode 8 or Xcode 9 beta 1, a library header imported in a bridging header without its path could compile successfully yet cause SourceKit indexing to fail and Swift autocompletion to break intermittently. The reported workaround is to include the library path in the import, such as `#import "path-to-library/MyClass.h"`. To investigate, enable Xcode's debug menu from the command line, inspect `/tmp/sourcekit-service-log.txt` for code-completion requests, and use the logged compiler arguments to run a Swift frontend invocation; the resulting errors can identify headers to fix. The author said the issue seemed fixed in Xcode 9.0.1 and that the Internal menu no longer appeared accessible.

### Source excerpt

This year I had the privilege of attending WWDC for the first time. I knew the labs were very important, and I want to share a resolution to fix a problem for our big project at Peak: Autocompletion on Swift code was not working most of the time in the IDE, and with the help of an Apple engineer in the labs we got it sorted. Update on 30/10/2017: The issues described here seem to be fixed with latest release version of Xcode 9.0.1 (9A1004). Also the 'internal' menu doesn't seem to be accessible anymore. If you know how to access it I'd love to hear from you! The issue If you are using Xcode 8 or Xcode 9 (beta 1 as of this writing), when you have a project with mixed Objective-C and Swift, you might encounters problems with autocompletion inside the Swift code. We've had this intermitently and most recent IDE versions made work very difficult as we would not have any autocompletion for our Swift code, or it would work intermitently. Our gut feeling was that the bridging header had some classes that were causing SourceKit to fail, but we didn't know how to debug the issue nor provide good feedback for Apple to fix it. Our chance came while visiting the labs at the conference, and a very helpful and patient Apple engineer worked with our project to understand what was wrong. Bridging header imports It turns out that if you import classes from libraries (in our case using CocoaPods) omitting the path may result in Sourcekit unable to index properly. For example, a class in some library: #import "MyClass.h" Code will compile fine but your code completion in Swift side might break because the indexer fails when encountering this file. I'm still unsure if it's because of importing the file somewhere else differently or if it's just a bug in the indexer. Anyway, the way to work around it (Apple is supposedly aware of this) is to import with the framework or library style, including the path: #import "path-to-library/MyClass.h" How to debug The engineer kindly made a wrote u

## Maintaining a Swift and Objective-C Hybrid Codebase

DevFeed: [Maintaining a Swift and Objective-C Hybrid Codebase](<https://devfeed.tech/articles/maintaining-a-swift-and-objective-c-hybrid-codebase-1476.md>)

Original publisher: [Read original article](<https://shopify.engineering/maintaining-a-swift-and-objective-c-hybrid-codebase>)

Author: Adrianna Chang

Published: 2017-06-15T18:13:00Z

Content type: article

Language: en

Sources: [Shopify Engineering](<https://devfeed.tech/sources/shopify-engineering.md>), [Shopify Engineering - Shopify Engineering](<https://devfeed.tech/sources/shopify-engineering-shopify-engineering.md>)

Topics: [Swift](<https://devfeed.tech/topics/swift.md>), [Objective-C](<https://devfeed.tech/topics/objective-c.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Code](<https://devfeed.tech/topics/code.md>), [WebKit](<https://devfeed.tech/topics/webkit.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [bridging](<https://devfeed.tech/tags/bridging.md>), [c](<https://devfeed.tech/tags/c.md>), [crash](<https://devfeed.tech/tags/crash.md>), [ios](<https://devfeed.tech/tags/ios.md>), [null](<https://devfeed.tech/tags/null.md>), [optional](<https://devfeed.tech/tags/optional.md>), [pointers](<https://devfeed.tech/tags/pointers.md>), [swift](<https://devfeed.tech/tags/swift.md>)

### AI overview

This article explains how to maintain a hybrid Swift and Objective-C codebase when adding new Swift code to an existing actively supported Objective-C project. It discusses interoperability between the two languages and the importance of correct nullability annotations for preserving Swift's compile-time optionality guarantees and avoiding runtime crashes.

### Source excerpt

6 minute read Swift is gaining popularity among iOS developers, which is of no surprise. It's strictly typed, which means you can prove the correctness of your program at compile time, given that your typesystem describes the domain well. It's a modern language offering syntax constructs encouraging developers to write better architecture using fewer lines of code, making it expressive. It's more fun to work with, and all the new Cocoa projects are being written in Swift. At Shopify, we want to adopt Swift where it makes sense, while understanding that many existing projects have an extensive codebase (some of them written years ago) in Objective-C (OBJC) that are still actively supported. It's tempting to write new code in Swift, but we can't migrate all the existing OBJC codebase quickly. And sometimes it just isn't worth the effort.

[Next page](<https://devfeed.tech/topics/objective-c.md?cursor=WyIyMDE3LTA2LTE1VDE4OjEzOjAwKzAwOjAwIiwgIjg5ZWZjMGJjLThkZDYtNGRkMi04NDg0LTMyNzI3ZGI5N2E5YiJd>)