Detailed Release Notes - Android Release 3.9.0 (11/01/2024)

Overview

Version 3.9.0 of the Tickets SDK for Android primarily focuses on top app crashers as viewed in Google console & reported from integration/client feedback. This release includes a variety of bug fixes detailed below. Note: Parity with iOS features will be released in upcoming point builds for these features: * Edit Assign, * Dependant toggles, and * Country Code toggle.

IMPORTANT (Sensetive Dependecies - info)

The dependencies below are used in Tickets SDK and have been shown to cause transitive dependency issues in the past. We cannot guarantee that this list is exhaustive. Our policy is to stay updated on these dependencies to avoid downgrades being required in your codebase. If you use the same dependencies but different versions, you may or may not encounter compile-time or runtime issues. We recommend matching the versions specified below.

io.insert-koin:koin-android:3.5.6
androidx.compose.material3:material3:1.3.0
com.google.android.material:material:1.12.0
androidx.compose.material:material:1.7.4
androidx.compose.ui:ui:1.7.4
androidx.compose.ui:ui-graphics:1.7.4
org.bouncycastle:bcpkix-jdk15on:1.70

High Level Changes:

• Top reported crash items.
• Bugs fixes
• Stability adjustments

Crashes Addressed

1. Crash addressed for console crashes: java.lang.IllegalStateException androidx.fragment.app.Fragment.requireContext
2. Crash addressed for console java.lang.IllegalStateException androidx.fragment.app.Fragment.requireActivity
3. Crash scenario: UK market experience crashes after loading Ticket Details page (aka: back of the ticket).
   1. Pick up if: Your app is in the Canadian market and experiencing this issue.
      1. Reproduction Steps:
         1. Login to the app
         2. Click on the "Sign In" button
         3. Click on any event card
         4. Click on “Ticket Details” from Ticket preview screen
            1. Current result: The My tickets details screen would not display. App sporadically crashes.
            2. Expected result: The user is now able to view Tickets Details screen and continue with flow.
4. Crash scenario: Seat Upgrade Module Crashing App
   1. Android: Seat Upgrade module causing crashing in some apps. Fixed timeout window allowing for upgrades to be dismissed if upstream latency vs. extended timeouts causing crashing.
   2. Pick up if: Your app is in North America, and the Archtics upgrade module is causing crashing.
5. Crash scenario: Future Venue "beta" client - Stage - Seeing a crash when using JumpToOrderorEvent
   1. Android: Fix for SDK function “JumpToOrderEvent” to reduce crashes.
   2. Pick up if: If you have ANY app using the “JumpToOrderEvent” function which drives a fan directly to the Ticket Preview page from another part of your app, and you’re experiencing crashing behavior.
6. Crash scenario: lateinit property psdkBridge has not been initialized
   1. Pick up if: Your app is North America and you're experiancing the crash sequence below
   2. We were able to reproduce the first crash with these steps
      1. Launch App
      2. Open tickets
      3. Click on team in ticket list (my user was already logged into TM)
      4. user is now on TM event view (EventsFragment)
      5. Background app
      6. on command line issue adb shell am kill com.bamnetworks.mobile.android.ballpark
      7. this simulates the os killing the app
      8. Select app in recent apps
      9. Crash with kotlin.UninitializedPropertyAccessException: lateinit property psdkBridge has not been initialized seen

Bug fixes, Issue Resolution

Android: Update to 401 “Session Expired” logic - to ensure when a session is expired a fan should be given the option to back into their account, resetting their token vs. “retry” which won’t fetch a new token.

• Pick up if: Your app is in SE market on Ticketmaster’s MFX (Microflex Platform) for apps experiencing this issue.
  • Reproduction Steps:
    • Login to the app
      • Click on the "Sign In" button
    • Prior result:
      • The app displays an error message "Session Expired" and another message below "Error retrieving Transfer. Try again later."
    • Updated result:
      • The user will not be presented with a 401 error. The user will be presented with a login page to reset the token.

Android: Update to better handle a user who declines “Terms & Conditions” updates by presenting the login page vs. a white screen. Users cannot continue to view tickets without reading and Agreeing to updated T&Cs

• Pick up if: Your app is in the Canadian market and experiencing this issue.
  • Reproduction Steps:
    • Login to the app
      • Click on the "Sign In" button
      • View updated Terms & Conditions
      • Click “Disagree”
    • Prior result:
      • Fan would be presented with a “white screen”
    • Updated result:
      • Fan will now be presented with the Login Page

Android: Update for Mexico market to display Ticket Preview page, as this occasionally is not loading for some users.

• Pick up if: Your app is in the Mexico market and experiencing this issue.
  • Reproduction Steps:
    • Login to the app
    • Click on any event card
      • Current result: The Ticket Preview page will not display, only appear to be loading.
      • Expected result: The user is now able to view Ticket Preview and continue with flow.

Android: Testing adjustment made to lower environments testing.
* Pick up if: You’re a “beta” client using Assign feature and have apps testing on Ticketmaster Stage environment

Android: Fix to ensure dependent ticket status is displayed correctly.
* Pick up if: You’re a “beta” client using Assign feature and are experiencing issues with incorrect status being displayed on dependent tickets.

Android: Fix to ensure assigned status displays correctly on the Ticket Preview.

• Pick up if: You’re a “beta” client using Assign feature and are experiencing issues with no status display on Ticket Preview page.
  

Android: Display adjustment on Assign flow for Pending/Accepted section.

• Pick up if: You’re a “beta” client using the Assign feature and are experiencing issues with tickets not displaying properly on the assign status page.

Android: “Beta” client adjustment to “cancel listing” button when a fan has a ticket listed. Fans will now click on “Manage listing” and be displayed the listed tickets for management.

• Pick up if: You’re a “beta” client using resale platform for resale tickets.

Android: Assignment of tickets based on transaction name, vs. specific assignee.

• Pick up if: If you are a “beta” client using the Assign feature and experiencing the below:
  • Current result: Each seat was transferred to a different person however All seats show as transferred to the same person (First person getting a ticket transferred) see image attached: "Current Issue.png"
  • Expected result: Each seat was transferred to a different person. All seats show the name of the different person waiting for recipient to claim.

Android: Update to “In-App Accept” banner quantity count to ensure ticket quantity is displaying correctly for assigned tickets.

• Pick Up if: You are a “beta” client using the Assign feature. This will ensure ticket count is displayed correctly vs. transaction count.

Android: Fix for “black” background display on assignee tickets to ensure correct readability.

• Pick up if: You are a “beta” client using the Assign feature. This will ensure assignees can properly view tickets text and ticket information