codesanitize

ios – The way to seize the situation occasion (enter/exit) that launched the app from terminated state?

iOS Development

codesanitize

31 July 2025

I’m implementing geofencing in my iOS app and working into some issues when the app is terminated (swiped up). I’m utilizing locationManager.startMonitoring(for: area) to provoke monitoring and utilizing locationManager(_ supervisor: CLLocationManager, didEnterRegion area: CLRegion) and didExitRegion to seize when the area boundary is crossed.

When the app is terminated and the primary set off comes by way of, the app launches within the background in response to the situation occasion. This triggers AppDelegate‘s didFinishLaunchingWithOptions and I can see that launchOptions?[UIApplication.LaunchOptionsKey.location] isn’t nil to suggest the situation occasion is why it opened. Nice!

Nevertheless, although the very first line of code in didFinishLaunchingWithOptions is locationManager.delegate = self, it is as if it is too late to seize the precise enter/exit occasion and neither didEnterRegion nor didExitRegion are fired.

Now as an example one other boundary occasion is triggered as a result of I’ve returned residence with out touching the app. This second (and all subsequent) occasions will set off didEnter/ExitRegion as a result of the app continues to be semi-launched from the primary occasion. So I can deal with these efficiently. However “lacking” that first occasion could be very problematic and appears unintended!

Does anybody have any expertise or recommendation on whether or not they’ve had the identical subject or whether or not it is a mistake on my finish?

Thanks!

Related, simplified code inside AppDelegate:

var locationManager: CLLocationManager = {
    let locationManager = CLLocationManager()
    locationManager.allowsBackgroundLocationUpdates = true
    return locationManager
}()

func locationManager(_ supervisor: CLLocationManager, didEnterRegion area: CLRegion) {
    log("didEnterRegion - sid: (area.identifier)")
}

func locationManager(_ supervisor: CLLocationManager, didExitRegion area: CLRegion) {
    log("didExitRegion - sid: (area.identifier)")
}

func startMonitoring() {
    area.notifyOnEntry = true
    area.notifyOnExit = true

    locationManager.startMonitoring(for: area)
    log("Began monitoring")
}

func utility(_ utility: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil) -> Bool {
    locationManager.delegate = self
    log("LAUNCH")

    // Test if app was launched resulting from location occasion
    if launchOptions?[UIApplication.LaunchOptionsKey.location] != nil {
        // App was launched resulting from location occasion
        log("App launched resulting from location occasion")
    } else {
        startMonitoring()
    }

    return true
}

And instance log output after terminating the app, then strolling out of the boundary after which strolling again contained in the boundary. Notice the launch occurred once I exited at 16:56, however no didExitRegion fired. Then at 16:57 once I entered, there isn’t a launch resulting from it already launching and I efficiently obtain didEnterRegion:

[2025-07-30 16:56:05.392] [INFO] LAUNCH
[2025-07-30 16:56:05.393] [INFO] App launched resulting from location occasion
[2025-07-30 16:57:49.290] [INFO] didEnterRegion - sid: 7285152

ios – Switching tab and pushing to NavigationStack doesn’t present new View

iOS Development

codesanitize

30 July 2025

I’ve a TabView with two tabs (FirstTab and SecondTab).

From the primary tab, I need to programmatically swap to the second tab after which instantly push a element display contained in the second tab’s NavigationStack.

I wrote a simplified instance:

struct FirstTab: View {
    var onNavigate: (String) -> Void

    var physique: some View {
        VStack {
            Textual content("FirstTab")

            Button("Go to SecondTab") {
                onNavigate("Whats up from FirstView")
            }
        }
    }
}


class SecondTabViewModel: ObservableObject {
    @Printed var textToShow: String? = nil
}

struct SecondTab: View {
    @ObservedObject var viewModel: SecondTabViewModel
    @State non-public var path = NavigationPath()

    var physique: some View {
        NavigationStack(path: $path) {
            VStack {
                Textual content("SecondTab")
            }
            .navigationDestination(for: String.self) { worth in
                DetailView(textual content: worth)
            }
            .onChange(of: viewModel.textToShow) { oldValue, newValue in
                print("onChange SecondTab textual content: (String(describing: newValue))")
                if let newValue = newValue, newValue != oldValue {
                    print("Pushing DetailView with: (newValue)")
                    path.append(newValue)
                }
            }
        }
    }
}

struct DetailView: View {
    let textual content: String

    var physique: some View {
        VStack {
            Textual content("DetailView")

            Textual content("Textual content: (textual content)")
        }
    }
}

struct ContentView: View {
    @State non-public var selectedTab = 0
    @StateObject non-public var secondVM = SecondTabViewModel()

    var physique: some View {
        TabView(choice: $selectedTab) {
            FirstTab { textual content in
                print("Closure referred to as with textual content: (textual content)")
                selectedTab = 1 // swap tab
                DispatchQueue.foremost.asyncAfter(deadline: .now() + 1) {
                    secondVM.textToShow = textual content
                }
            }
            .tabItem { Label("First", systemImage: "1.circle") }
            .tag(0)

            SecondTab(viewModel: secondVM)
                .tabItem { Label("Second", systemImage: "2.circle") }
                .tag(1)
        }
    }
}

The problem :

The closure is appropriately referred to as once I faucet the button in FirstTab.
The tab switches to SecondTab.
I anticipate the DetailView to mechanically push within the NavigationStack.

However nothing seems – onChange is named, however no push happens.

If I wrap the textToShow inside a DispatchQueue.foremost.asyncAfter (e.g. 0.1 seconds), it really works.

Instance of the workaround:

FirstTab { textual content in
    print("Closure referred to as with textual content: (textual content)")
    selectedTab = 1 // swap tab
    DispatchQueue.foremost.asyncAfter(deadline: .now() + 1) {
        secondVM.textToShow = textual content
    }
}

However this looks like a hack.

Why doesn’t the navigation push (path.append) work when switching tabs instantly?

Is there a beneficial, clear manner in SwiftUI to vary tab after which push a vacation spot in that tab’s NavigationStack?

Ought to I be utilizing a distinct navigation method (e.g. Coordinator, Observable shared state)?

12 3...4,281 Page 1 of 4,281

codesanitize

ios – The way to seize the situation occasion (enter/exit) that launched the app from terminated state?

AI-Generated Code Poses Main Safety Dangers in Practically Half of All Improvement Duties, Veracode Analysis Reveals

Begin Your Networking Profession with Cisco U.

Specialists weigh in: Why does “Again to Fundamentals” matter on your profession?

Who’re the Cisco consultants?

Meet Kyle Winters

Meet Francois Caen

Meet Chuck Stickney

What do Cisco consultants advocate for beginning a networking profession?

Kyle’s suggestions: The place to start out with networking

Francois’s suggestion: Deal with subnetting first

Chuck’s suggestion: Begin with Cisco Licensed Assist Technician (CCST) content material

What do consultants say about tech studying?

What closing recommendation do the Cisco U. consultants have?

Prepared to start your networking coaching?

ios – Switching tab and pushing to NavigationStack doesn’t present new View

UAE knowledge middle brings enhanced e mail safety to area