Question 1

How do I integrate Siren into a SwiftUI app?

Accepted Answer

Siren doesn't have built-in SwiftUI support, but you can call Siren.shared.wail() from the AppDelegate or SceneDelegate, or use UIKit lifecycle methods in SwiftUI's UIApplicationDelegateAdaptor. The README provides examples for traditional UIKit setups.

Question 2

Siren vs. Harpy: which one should I use?

Accepted Answer

Siren is the Swift-based successor to Harpy (Objective-C), which is deprecated. For new Swift projects, Siren is recommended due to modern Swift support and ongoing maintenance, though both share similar core features.

Question 3

How can I test Siren alerts locally without an App Store submission?

Accepted Answer

Temporarily change your app's version string to an older version or use a bundle ID from an existing App Store app (like Facebook's), as described in the Testing section. This simulates an update check against live App Store data.

Question 4

Does Siren work with TestFlight beta distributions?

Accepted Answer

No, Siren is designed for production App Store versions and may not correctly handle TestFlight builds, as it checks the public App Store JSON, which doesn't include beta version information.

Question 5

How to customize the update alert UI in Siren?

Accepted Answer

Siren uses system alerts by default, but you can bypass them by implementing delegate methods to handle update notifications externally, allowing for custom interfaces. The README mentions alternative notification methods.

Question 6

What happens with Siren during Apple's phased releases?

Accepted Answer

Siren will prompt all users immediately unless configured otherwise. To align with phased rollouts, you can set a delay (e.g., 7 days) using showAlertAfterCurrentVersionHasBeenReleasedForDays or disable Siren remotely via your backend.

Siren

What is Siren?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions