Testing and Debugging

Testing

Prerequisites

User accounts:

• A user without TIXNGO ticket

• A user with TIXNGO ticket

iOS

1. Clone demo app from github

2. Setup cocoapods and run "pod install"

3. Run app

4. Login account

   1. by an account with ticket

   2. by an account without ticket

Android

1. Clone demo app from github

2. Setup config same link

3. Run app

4. Login

   1. by an account with ticket

   2. by an account without ticket

Test Scenarios Checklist

Use the following scenarios to validate that your integration with the TIXNGO SDK is functioning correctly. This checklist ensures proper handling of authentication, ticket visibility, transfer flows, session limits, and token expiration recovery.

1. Login Scenarios

1.1 Login with a Ticketed Account

• Precondition: Th

• Steps:

  • Launch the Fan App.

  • Login using valid credentials.

  • Navigate to the TIXNGO SDK screen.

• Expected Result:

  • SDK loads successfully.

  • Ticket list is visible.

  • No errors are returned.

1.2 Login with an Account without Tickets

• Precondition: The test user has never owned a ticket in the TIXNGO system.

• Steps:

  • Launch the Fan App.

  • Login using a valid user account.

  • Attempt to access the TIXNGO SDK screen.

• Expected Result:

  • SDK returns error: 403, NO_TICKET_ELIGIBILITY.

  • Fan App displays a user-friendly message and prevents SDK access.

2. Logout and Re-Login Scenarios

2.1 Logout User

• Steps:

  • From the Fan App, trigger the logout flow.

  • Ensure that TIXNGO SDK logout() is called.

• Expected Result:

  • User is logged out from both Fan App and SDK.

  • SDK local session data is cleared.

2.2 Login Again After Logout

• Steps:

  • Re-authenticate with the same user account.

  • Access the SDK.

• Expected Result:

  • SDK initializes successfully.

  • Previously accessible tickets are still shown (if any).

3. Token Expiration Handling

Refer to Token Lifecycle and IntegrationPreview

3.1 Resume After Token Expiration

• Precondition: User is logged in, token has a short TTL (e.g., 5 mins).

• Steps:

  • Login to the Fan App.

  • Wait until the access token expires (without interacting).

  • Reopen the app and access the SDK.

• Expected Result:

  • SDK triggers token refresh via Fan App.

  • Fan App provides ref

  • SDK resumes operation without user logout.

4. Session & Device Limits

4.1 Exceed Session or Device Limits

Refer to Authentication & SecurityPreview

• Precondition: Backoffice session limit (e.g., 2 sessions) is configured for the user.

• Steps:

  • Login with the same user on two devices (e.g., iPhone + Android) → OK.

  • Attempt login on a third device.

• Expected Result:

  • Login is rejected.

  • SDK returns error:

    • 403, MAX_NUMBER_SECURITY_TOKEN for session limit

    • 403, TOO_MANY_REGISTERED_DEVICES for device limit

  • Fan App displays an appropriate error message.

5. Ticket Transfer Scenarios

5.1 Send a Ticket to Another User

• Precondition: Logged-in user owns at least one transferrable ticket.

• Steps:

  • Access TIXNGO SDK.

  • Initiate a ticket transfer to another valid user.

• Expected Result:

  • Transfer request is sent successfully.

  • Ticket enters “pending transfer” state.

5.2 Accept a Transferred Ticket

• Precondition: Receiving user must be logged in to the Fan App with no ticket yet.

• Steps:

  • Login with the receiving user.

  • Navigate to the TIXNGO SDK screen.

  • Accept the pending transfer.

• Expected Result:

  • Ticket is successfully added to the receiver's wallet.

  • Transfer status is updated accordingly.

6. DeepLink Test

• Tap on a notification with an SDK deeplink (e.g., ticket detail link).

• Expected: SDK opens the correct view.

7. Offline Mode Ticket Viewing

• Login to the Fan App with tickets.

• Go offline.

• Access the SDK.

• Expected: Tickets are still visible (read-only).

8. Notification Test

Validate notification handling across all app states:

• Foreground – the app is open and visible on the screen (actively used).

  Example: You’re logging in or viewing tickets.

• Background – the app is still running but not visible (you switched to another app or pressed the Home button).

  Example: You minimize the app, then later return to it.

• Not running (app has been killed) – the app process has been completely stopped (e.g., you swipe it away from recent apps or force close it).

  Example: You kill the app, reopen it, and check if it still works normally.

For each scenario below, repeat the test in all above states.

8.1 Ticket Injection Notification

• Steps:

  • Inject a ticket to the user account.

  • Wait for the notification to arrive.

  • Open the notification.

• Expected Result: User is redirected to the ticket detail screen.

8.2 Ticket Lifecycle Notifications

• Steps:

  • Perform a ticket action (transfer, accept, reject, cancel, return, or delete).

• Expected Result: User receives a notification for the corresponding action.

8.3 Scheduled Campaign Notification

• Steps:

  • Trigger a scheduled campaign that sends a notification.

  • Open the notification.

• Expected Result: User i

8.4 Account Switch Notification Isolation

• Precondition: Device has been used by two different accounts sequentially.

• Steps:

  • Login with Account A on Device D and receive a notification.

  • Logout Account A, then login with Account B on the same device.

  • Inject or transfer a ticket to Account A.

• Expected Result: Account B does not receive notifications intended for Account A.

8.5 Logout Notification

• Precondition: User is logged in on a device.

• Steps:

  • Logout the user via Backoffice or Mobile.

• Expected Result: User receives a logout notification on their mobile device.

8.6 Validate App Stability Across All States.

• Steps:

  • Perform key actions: login, ticket injection, activation, assignment, transfer/cancel/reject/accept.

  • Send app to background.

  • Kill and relaunch the app.

  • Repeat the above steps 3–5 times.

• Expected Result:

  • The app remains stable in all states.

  • No crash occurs during or after performing the actions above.

  • User can continue using the app normally after reopening.

Debugging

Enable debug mode  'isEnableDebug: true'

We recommend using TIXNGO Backoffice during testing, in