TIXNGO SDK Release Notes
SDK Version Summary
Version | Release Date | Key Features/Notes |
|---|---|---|
Nov 18, 2025 | Lowered minimum Android Kotlin version to 2.0.0; stability improvements | |
Nov 13, 2025 | Kontakt dependency uses local path; fixed initialization error if | |
Nov 12, 2025 | Fixed Apple ITMS-91065 issue (iOS only). | |
Nov 4, 2025 | Spectator V4, Android 16KB support, mobile UX & performance enhancements, Dutch language, Android font import update, ticket display bug fixes. | |
Aug 13, 2025 | Enhanced ticket fields visibility, bug fixes, update translation key | |
Aug 7, 2025 | SPM checksum fix | |
Aug 7, 2025 | SPM support, SDK renaming, Podfile update | |
Jun 25, 2025 | Ticket V4 ready, new ticket layouts, bug fixes |
Version 4.2541.4
What’s New
Lowered the minimum required Android Kotlin version to 2.0.0, improving compatibility with a wider range of Android projects.
Bug Fixes
General stability improvements and minor bug fixes to enhance overall SDK reliability.
Version 4.2541.3
Bug Fixes
Updated the Kontakt dependency to use a local path instead of a remote URL, preventing potential 404 errors and ensuring reliable initialization.
Fixed an initialization failure that occurred when the
"en"language code was missing fromsupportedLanguage.
Version 4.2541.2 (iOS only)
Bug Fixes
Resolved Apple Review issue ITMS-91065 to improve app submission and compatibility.
Version 4.2541.1
What’s New
Support Spectator V4 Launch:
This SDK version includes support for the Spectator V4 Launch
We have completed a full refactoring of spectator-centric data management
The Spectator data model has been modernized to enhance performance, scalability, GDPR compliance, and maintainability.
We also have new and improved mobile devices and sessions management.
The management of spectator devices and sessions has been rebuilt to improve performance while maintaining a strong focus on security and control.
Important Note
The rollout of this feature is coordinated with the broader TIXNGO product release. For up-to-date availability details, please consult the global release notes 2025 Rimpfischhorn V4
Android 16KB Compatibility
SDK updated to ensure compliance with Google Play's requirement for apps targeting Android 15 and above.
Now supports 16 KB memory page sizes, ensuring optimal functionality on the latest Android versions.
Mobile UX Improvements
Simplified Ticket Return & Transfer: Returning a ticket or transferring it from Backoffice no longer requires acceptance, even if the transfer accept/reject feature is enabled.
Configurable Deleted Ticket Display: The mobile app can now display only specific deleted tickets, based on the deletion reason (configurable in Backoffice).
Seating Details Customization from the Backoffice screen:
Full control over the visibility of each seating detail field on the mobile ticket screen.
Crowdin label keys for seating detail fields can be freely customized per field, allowing for venue-specific terminology (e.g., displaying "Skybox" instead of "Block" for VIP tickets).
Support for Custom Navigation Flow: This SDK version introduces support for the Custom Navigation Flow feature, allowing organizers to define a fully custom navigation experience for the ticket detail screen via the S-360 injection template.
Important Note
The rollout of this feature is coordinated with the broader TIXNGO product release. For up-to-date availability details, please consult the global release notes 2025 Rimpfischhorn V4
Performance Improvements
General performance enhancements have been implemented.
Added Dutch language support
Expanded Dutch (nl) language support in TixngoLanguage:
Android: TixngoLanguage.NLiOS: TixngoLanguage.nl
Syntax Change (Android Only)
To adapt custom fonts, please change the package import for nativefont from:
import com.xuning.native_font.NativeFontPluginto
import io.tixngo.native_font.NativeFontPlugin
Bug Fixes
Addressed small issues related to ticket display.
For more details, see: Fixing small issues on the ticket display
Version 4.2531.1
What’s New
Enhanced Ticket Fields Visibility
You can now define which fields are displayed on the ticket via the design rule, offering greater flexibility and customization.
It is now possible to display custom field values in the first section of the ticket using the main ticket metadata (available in the CLASSIC layout only).
For more details, see the documentation: Added flexibility on ticket fields visibility
Updated the translation key for Ticket V4
Bug fixes
Fix minor issues.
Version 4.2524.3
What’s New
Solved the issue related to checksums on the SPM
Version 4.2524.2
What’s New
Swift Package Manager (SPM) Support for iOS
SDK Renaming and Podfile Update
The SDK has been renamed from
sdktotixngoUpdate your imports:
import Tixngo(instead ofimport sdk)Podfile integration updated:
You must update yourPodfileto use the new pod names:from
pod 'sdk', :git => 'https://github.com/tixngo-mobile-github/tixngo_sdk_ios.git', :tag => '4.2524.2' pod 'sdk-debug', :git => 'https://github.com/tixngo-mobile-github/tixngo_sdk_ios.git', :tag => '4.2524.2', :configurations => ['Debug'] pod 'sdk-release', :git => 'https://github.com/tixngo-mobile-github/tixngo_sdk_ios.git', :tag => '4.2524.2', :configurations => ['Release']to
pod 'Tixngo', :git => 'https://github.com/tixngo-mobile-github/tixngo_sdk_ios.git', :tag => '4.2524.2' pod 'Tixngo-debug', :git => 'https://github.com/tixngo-mobile-github/tixngo_sdk_ios.git', :tag => '4.2524.2', :configurations => ['Debug'] pod 'Tixngo-release', :git => 'https://github.com/tixngo-mobile-github/tixngo_sdk_ios.git', :tag =>
Important Note
SPM (Swift Package Manager) support is introduced in this version. Previous versions do not support SPM. Other integration methods (such as CocoaPods) remain available and supported.
Version 4.2524.1
What’s New
Ticket V4 Ready!
We are thrilled to announce the release of our new SDK, which is filled with powerful enhancements that set the stage for the next generation of mobile ticketing!
Support for Ticket V4 Capability
Ticket V4 is now fully integrated into the SDK, unlocking new opportunities for organizers and significantly improving the platform experience:
Enhanced ticket lifecycle management
Improved scalability and performance
Reduced back-office complexity and onboarding friction
Simplified S-360 interface and faster admin operations
Reinforced platform security
Streamlined settings and legacy features
WYSIWYG configuration options for organizers
Foundation for faster, more relevant feature development
Full details available here: Introduction to TIXNGO V4
New Ticket Layouts
We are excited to unveil two modern ticket layouts that enhance the fan experience:
CURIOSITY Layout – A sleek, premium design tailored for general events. Visually appealing and customizable for a variety of applications.
For full details on the CURIOSITY layout, click here: V4 Ticket Layout > Curiosity
MATCH Layout – Specifically designed for sports clubs and federations. Perfect for events featuring competing teams, with a dynamic team display and a clear, bold design.
For complete details on the MATCH layout, click here: Event semantics - Match
Important Note
The migration from Ticket V3 to Ticket V4 is managed on the backend side. Please reach out to our Support Team for assistance with planning or activating the migration.
Bug Fixes
Resolved issues related to ticket transfer errors in certain edge cases
Transfer Flow Conflict with Past Tickets
Root Cause: The SDK was using the same local storage table for TicketPreview of both Transfers and Past Tickets. In rare cases this caused conflicts when retrieving past tickets and pending transfers and then removing a ticket preview as part of the transfer process.
Solution: Introduced a separate local storage table for Past Tickets to avoid conflicts with TicketPreview used in transfers.
Fixed a bug that caused random user logouts and the need for manual activation in specific scenarios due to duplicate UpdateToken call
Duplicate Token Update Calls
Root Cause: In the previous SDK version, when the app was opened with an expired token, it triggered the
updateTokencall twice—once from a background API call and once via the token expired delegate. This resulted in an error where the service (including activation) stopped and did not resume after obtaining a new token.Solution: Prevent duplicate
generateTokencalls within the SDK.
© TIXNGO 2023 - Login