feat: use protected routes

[ManuViola77]

Jira board reference:

• Jira_Card_Name

---

What does this do?

This PR implements the use of Protected Routes to have separate stacks for authenticated/not authenticated.

It has 3 protected stacks:

• The Onboarding with guard isFirstTime
• Authenticated with guard isAuthenticated
• Not authenticated with guard ! isAuthenticated

Also removes the push routes to '/' when success sign in/sign up, since now the protected guards will automatically change stacks when the isAuthenticated changes.

---

Why did you do this?

There was a bug where after sign in/sign up you could go back to a login screen by swiping, while you were actually already logged in.

Also, its good to have separate stacks to avoid accessing screens you shouldn't.

Who/what does this impact?

The App navigation (layout), now it starts in the onboarding if it wasn't shown yet, and then if its authenticated then it shows the authenticated stack (starting in the feed), otherwise it shows the not authenticated stack (starting with sign in screen).

How did you test this?

• Tested on iOS
• Tested on Android
• Tested on a small device
• Tested on a real device
• Tested all flows related with this PR changes
• Tested accessibility
• Added tests

---

Notes:

---

Screenshots / Previews

Before:

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-10-31.at.10.47.59.mp4

After:

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-10-31.at.10.40.52.mp4

🧑‍🎨 Figma Design:

📱 Android:

📱 iOS:

[github-actions]

💯 Test Coverage

Lines	Statements	Branches	Functions
	49.56% (342/690)	44.04% (122/277)	36.28% (86/237)

😎 Tests Results

Tests	Skipped	Failures	Errors	Time
77	0 💤	0 ❌	0 🔥	29.731s ⏱️

👀 Tests Details • (49%)

File	% Stmts	% Branch	% Funcs	% Lines	Uncovered Line #s
All files	49.56	44.04	36.28	49.92
app	0	0	0	0
_layout.tsx	0	0	0	0	23–118
sign-in.tsx	0	100	0	0	9–16
sign-up.tsx	0	100	0	0	10–18

[fernandatoledo]

yay!

[jpirazusta]

👏 👏