Replies: 1 comment 1 reply
|
The way we handle this is in the You can add your own notification mechanism from your AppDelegate. Agreed, though, that it would probably be nice to just be able to use standard notifications for this. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I noticed that several UIApplication lifecycle notifications are currently unavailable in Skip. These are commonly used in shared code to respond to app lifecycle changes (for example, refreshing state when the app returns to the foreground or cleaning up when backgrounding).
Notifications Requested
UIApplication.willEnterForegroundNotificationUIApplication.didFinishLaunchingNotificationUIApplication.didBecomeActiveNotificationUIApplication.willResignActiveNotificationCurrent Workaround
I have defined a custom extension in my Skip project and I am manually posting from the corresponding
MainActivitylifecycle methods:I imagine the Android lifecycle callbacks map fairly cleanly to these notifications, so it might be possible to expose them in Skip at some point to better align with iOS behavior and simplify shared lifecycle handling.
Of course, I completely understand if this isn’t a current priority — just wanted to share the suggestion in case it’s helpful.
Thanks again!
All reactions