Alternative to override willFinishLaunching in the AppDelegate

[Dlemex]

What Stanford Spezi module is your challenge related to?

Spezi

Description

I need to register a background task (for a custom identifier), start app metrics, and currently, for convenience, register user defaults. I have been doing this as an override of application(willFinishLaunchingWithOptions:) with the intent to migrate to LifeCycleHandler. Some Spezi docs still imply that this is correct. However, the code declares those methods as deprecated as well. What do you think is the best way to handle this? The background task registration needs to occur before the delegate method returns.

Reproduction

Current functionality works with the deprecation notice.

Most LifeCycleHandler mentions are fleeting, such as the tip in Spezi/Module and Spezi/Interactions with SwiftUI. But noticeably gone from Spezi/Interactions with Application.

Expected behavior

Any alternatives to avoid the deprecation notice? I may just be missing something obvious, but I am not sure.

Additional context

No response

Code of Conduct

• I agree to follow this projects's Code of Conduct and Contributing Guidelines

[PSchmiedmayer]

Thank you for reaching out @Dlemex!

Overriding the methods and calling the super methods should be the way to go. Can you share some more details about the code and the example that triggers the deprivation warning?

Once we have that @Supereg can probably provide some additional context on this 👍

[lukaskollmer]

unless i'm missing something here, the easiest approach would be to simply define a custom Module, add it to the app's Spezi Configuration, and use the module's configure() function to register the background task.

AFAIK, all modules are intialized and configured before willFinishLaunching returns

[Dlemex]

@lukaskollmer @PSchmiedmayer I didn't realize that that was guaranteed. I can easily create modules for those items and ditch the override. I knew there had to be a simple solution. Thanks!

[bauer-andreas]

Exactly what @lukaskollmer said already, just implement a Module and put your logic into the configure() method. The benefit of this is that it stays platform-agnostic. So we do the heavy lifting of making this approach work across WatchKit and AppKit as well.

You can use @Application(\.launchOptions) if you need access to the launch options at all. Note that the type might be platform dependent though.