Skip to content

Fixed incorrect AppExitReason documentation #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 18, 2025
Merged

Fixed incorrect AppExitReason documentation #46

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions source/_guides/user-interfaces/app-exit-reason.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,7 @@ Introduced in SDK v4.0, the ``AppExitReason`` API allows developers to provide a
reason when terminating their application. The system uses these reasons to
determine where the user should be sent when the current application terminates.

At present there are only 2 ``AppExitReason`` states when exiting an application,
but this may change in future updates.
At present, there are only two ``AppExitReason`` states when exiting an application, but this may change in future updates.

### APP_EXIT_NOT_SPECIFIED

Expand All @@ -39,7 +38,7 @@ this state will be used automatically.
static void prv_deinit() {
// Optional, default behavior
// App will exit to the previous location in the system
app_exit_reason_set(APP_EXIT_NOT_SPECIFIED);
exit_reason_set(APP_EXIT_NOT_SPECIFIED);
}
```

Expand All @@ -52,6 +51,6 @@ to the default watchface.
```c
static void prv_deinit() {
// App will exit to default watchface
app_exit_reason_set(APP_EXIT_ACTION_PERFORMED_SUCCESSFULLY);
exit_reason_set(APP_EXIT_ACTION_PERFORMED_SUCCESSFULLY);
}
```