Chimple App || Post-Signup User Redirected to Chimple Home screen instead of Opening Lesson

[poojaustad]

Issue:
When a Chimple lesson is launched via Respect, and Chimple is freshly installed, the user is prompted to sign up via Respect. After signing up, the user is redirected to the Chimple home screen instead of the intended lesson.

Expected Behavior:
After signup, the user should be directly navigated to the selected lesson.

Observed Behavior:
After signup, the app opens the home screen, requiring manual navigation to the lesson.

Screenrecord:

Screencast.from.2025-07-18.10-59-36.webm

[mikedawson]

@kvskandakumar the lesson launching must work independently of whether or not any particular user has signed into Chimple app itself (using Respect or any other mechanism).

The idea that a user would have to install Chimple, open it, sign-in, and then come back to RESPECT, before they could use the Chimple lesson, breaks the idea of launching a lesson from RESPECT.

As per the integration guide section 5

Some or none of the OpenID Standard Claims, e.g. given_name, locale, sub, depending on the privacy settings being used by the RESPECT Launcher.

When a lesson is launched, you need to use the identity information (if any) provided by the launch URL params.

This will also be a major problem if we want to demo on anyone else's device: if we're trying to tell people "hey this makes it easy", and then when installing, we have to go and open Chimple separately to sign-in there, will be a problem.

[kvskandakumar]

@mikedawson I’ve checked this issue. It won’t occur in a real scenario where the Chimple Respect login is used. In the Chimple flow, users are directed to sign in through the launcher app, which causes the original deep link session to expire.

Currently, since Chimple uses a mock user and the deep link is being triggered directly from the launcher app, the Respect login appears to retain the deep link session — but this is specific to the mock setup.

[mikedawson]

@mikedawson I’ve checked this issue. It won’t occur in a real scenario where the Chimple Respect login is used. In the Chimple flow, users are directed to sign in through the launcher app, which causes the original deep link session to expire.

Currently, since Chimple uses a mock user and the deep link is being triggered directly from the launcher app, the Respect login appears to retain the deep link session — but this is specific to the mock setup.

@kvskandakumar this is a real problem and it needs fixed ASAP.

Expected flow (if Chimple app behaved as per spec):

• User installs RESPECT and Chimple
• User signs-in to RESPECT
• User selects Chimple lesson in RESPECT. Chimple app launched
• Lesson starts

When launching a lesson (as per integration guide section 5) the RESPECT Compatible app should get user information from the query parameters provided (if any). Launching a lesson must be independent of signing in with RESPECT or anything else.

Observed flow:

• User installs RESPECT and Chimple
• User signs-in to RESPECT
• User selects Chimple lesson in RESPECT. Chimple app launched
• User has to sign-in again. The exact opposite of what they would expect when using a single sign on solution

The Respect app is not "retaining a deep link session" - it is simply launching an Intent with the Deep Link Uri (including respect parameters):

https://github.com/UstadMobile/Respect/blob/main/respect-lib-shared/src/androidMain/kotlin/world/respect/shared/domain/launchapp/LaunchAppUseCaseAndroid.kt#L38

[kvskandakumar]

@mikedawson @poojaustad We’ve resolved the issue. You can download the latest APK from the link below and please test from your side

🔗 Chimple Respect APK

[poojaustad]

Hi @kvskandakumar ,

I have been able to reproduce the bug, testing the latest APK. Can you please post a screen record on your end?

Screencast.from.2025-07-21.16-34-56.webm

[kvskandakumar]

@poojaustad Please sign in using the RESPECT button. Once the login is complete, the deep link will launch automatically.

[poojaustad]

Hi @kvskandakumar ,

This is the expected flow -

1. User installs RESPECT and Chimple
2. User signs-in to RESPECT
3. User selects Chimple lesson in RESPECT. Chimple app launched
4. Lesson starts

Issue: After step 3, Chimple app unnecessarily asks the user to sign up, which is not as per the expected flow.

Action Required: Chimple app should accept the RESPECT sign-in and directly start the lesson without additional sign-up.

[kvskandakumar]

@poojaustad We’ve followed the same flow as mentioned—please refer to the earlier messages in this task. The user must sign in first; without login, we won’t proceed to launch the lesson.