fix: Ask permission only first open and rationale == true

[baillyjamy]

Ask permission only first open and rationale == true

[Copilot]

Pull request overview

Updates the app’s notification permission flow to only prompt on the first open and to re-prompt only when Android reports that a rationale should be shown.

Changes:

• Adjusted navigation conditions around the notification permission screen.
• Introduced a PermissionPreferences store and exposed it via MainViewModel as a StateFlow.
• Updated MainScreen permission-routing logic to use the new preference + rationale status.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
app/src/main/kotlin/com/infomaniak/auth/ui/screen/permission/NotificationPermissionScreen.kt	Changes when the permission screen auto-navigates away based on permission status.
app/src/main/kotlin/com/infomaniak/auth/ui/screen/main/MainViewModel.kt	Adds preference-backed StateFlow and a setter to mark permission as asked.
app/src/main/kotlin/com/infomaniak/auth/ui/screen/main/MainScreen.kt	Reworks permission-routing logic to use preference state + shouldShowRationale.
app/src/main/kotlin/com/infomaniak/auth/data/preferences/PermissionPreferences.kt	Adds a new Splitties preferences wrapper for notification permission “asked” state.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Updates the notification permission onboarding flow to avoid re-prompting after the first display, while allowing re-display when Android indicates a rationale should be shown again.

Changes:

• Added a persisted hasTriggeredNotificationPermission flag via PermissionPreferences.
• Exposed/updated that flag from MainViewModel as a StateFlow and setter method.
• Reworked navigation decision logic in MainScreen and refactored NotificationPermissionScreen to use the persisted flag.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
app/src/main/kotlin/com/infomaniak/auth/ui/screen/permission/NotificationPermissionScreen.kt	Adds persistence-aware permission screen behavior and refactors UI vs side-effects.
app/src/main/kotlin/com/infomaniak/auth/ui/screen/main/MainViewModel.kt	Introduces flow + setter for persisted “notification permission was triggered” state.
app/src/main/kotlin/com/infomaniak/auth/ui/screen/main/MainScreen.kt	Updates routing logic to decide whether to navigate to the permission screen.
app/src/main/kotlin/com/infomaniak/auth/data/preferences/PermissionPreferences.kt	New Splitties preferences storage for the persisted trigger flag.

Comments suppressed due to low confidence (1)

app/src/main/kotlin/com/infomaniak/auth/ui/screen/permission/NotificationPermissionScreen.kt:116

• Tapping "Later" navigates home but does not call onNotificationPermissionTriggered(), so hasTriggeredNotificationPermission stays false and the permission screen will keep being shown on subsequent launches. Consider marking the permission flow as triggered when the user skips (or when the screen is first shown).

                LargeButton(
                    modifier = Modifier.fillMaxWidth(),
                    title = stringResource(R.string.laterButton),
                    style = ButtonStyle.Tertiary,
                    onClick = navigateToHome
                )

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
24 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud