Overview
SDK 3.19.0 release is not a forced or required update.
Version 3.19.0 includes enhancements across ticket management, mobile tickets, and modules. Ticket management updates include auto-accept for assigned tickets, Deny Mobile list code support for assign recipients, a refreshed Assign experience, one-ticket-per-event transfer restriction support, and dynamic fulfillment instructions for third-party events. On mobile tickets, we've added purchase vs. printed price display. And for modules, new engagement analytics for Ignite Modules.
SDK 3.19.0 uses Android Gradle Plugin 9
Ticket Management
Assign | Auto-Accept
When fans access their Host tickets through the Ticketmaster app, Fans can now skip the manual acceptance step when assigning tickets. When a sender assigns tickets to a recipient with a known Ticketmaster account, the sender can opt in to auto-accept. The tickets are then placed directly into the recipient's account with no acceptance required.
Recipients simply sign in to see their tickets, and email links deep-link them directly to the order. If no Ticketmaster account is found, the assignment follows the existing acceptance flow.
This removes the manual acceptance step for eligible recipients, creating a more direct Assign experience.
Available for: Archtics and Host via Domains events.
Assign | UX Enhancements
The Assign flow has been updated with clearer actions in Steps 2 and 3. The trash-can and edit icons have been replaced with explicit Cancel Access and Edit text buttons, helping distinguish between canceling access and editing an assignment.
The transfer off-ramp banner is also updated with clearer copy: "Need to Transfer Ownership? Transfer a ticket to someone you're not attending with." The banner now uses your app's primary color.
Available for: Archtics and Host via Domains events.
Assign | Deny Mobile List Code Support for Recipients (Archtics)
The Deny Mobile (XTMDENY) list code restriction now applies to assign recipients, not just senders. When a sender's account carries the list code, recipients of assigned tickets are blocked from viewing barcodes on mobile. The fallback screen messaging has also been updated to reflect the restriction.
This closes a policy-enforcement gap and ensures your mobile-entry restrictions apply consistently to every ticket holder.
Transfer | Restrict Recipient to One Ticket (Archtics)
When you enable the "Restrict recipient to one ticket" setting in the CMS, the SDK now enforces and clearly communicates the restriction to recipients.
A fan who already holds a ticket to an event and attempts to accept another sees:
"Looks like you already have a ticket(s). You are eligible for only one ticket to this event."
If a fan receives multiple tickets in a single invite, they'll see guidance to ask the sender to send a single ticket.
This is ideal for the college and student-ticket segment, helping you prevent ticket accumulation and ensure fair access for high-demand events.
Third-Party Events (3PE) | Dynamic Fulfillment Details
Your fans purchasing tickets for events fulfilled by a third-party provider (e.g., AXS, SeatGeek, MLB Ballpark) now see accurate, provider-specific delivery guidance.
The ticket view CTA is labeled per delivery type:
- "Access Your Tickets" — mobile transfer
- "Track Package" — UPS
- "Pick-Up Info" — Will Call
Selecting the CTA opens a webview with the provider's delivery instructions.
This reduces fan confusion and support contacts for third-party events. New providers can also be added through configuration without requiring an SDK update.
Available for: North America events.
Mobile Ticket
Purchase and Printed Price Display
You now have more control over the price fans see on their digital tickets. The SDK mobile ticket honors your Archtics price preference setting, bringing the mobile experience in line with Account Manager.
Based on your Archtics setting:
- "All" — the purchase price is shown
- "Null" — the pricing section is hidden
This update creates a consistent pricing experience across web, iOS, and Android, while giving you control over what fans see.
Available for: Archtics events on the v2 ticket design.
Modules
Ignite Modules Engagement Analytics
The SDK now captures how your fans engage with custom modules:
- Page views
- Module views (triggered when a module is fully in view)
- Button taps
Each interaction includes module ID and event ID metadata and flows into the analytics pipeline, providing visibility into how fans engage with individual modules.
More information on how you can request module reporting will be shared separately.
Bug Fixes
Android
- Fans were able to assign a ticket to themselves using their own phone number
- Crash in OrdersWebViewActivity on launch
- Ballpark app — device binding error
- Error and crash on logout
- Navigation back from SDK login spun indefinitely in the host app
- IllegalArgumentException crash during fragment lifecycle transitions
- Barcode scanning issues when the Android "Screen Zoom" setting was in use (ticket design V2)
- Regular and upsell tickets were not split correctly on transfer (V2)
- Assign text was not visible in Dark Mode (V1/V2)
- Double horizontal bars on location/city tile area (events V2, TM UK)
- Past events incorrectly showed a PAST EVENT tag
- US Open app crashes/errors when opening tickets