Repository navigation
Validate T-TAG ranging and prepare the 0.1.0 release - #1
Merged
Merged
Conversation
mhrsntrk
changed the title
mhrsntrk
marked this pull request as ready for review
September 21, 2026 09:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The example rendered black text against a black background in dark mode, hiding live UWB readings and the session log. Use dynamic iOS colors, and configure the built-in T-TAG transport for foreground NI ranging instead of assuming every BLE connection is a paired accessory implementing Apple’s NI GATT service.
Also add the missing nkf build dependency for newer Ruby versions, label the example correctly, and provide opt-in console diagnostics. Record the hardware evidence and remaining validation limitations in docs/validation/2026-09-21.md.
Validation: all 23 JavaScript tests, strict TypeScript, codegen, package checks and four Swift tests passed; fresh React Native and Expo tarball consumers installed and bundled; local simulator and signed iPhone Release builds passed. On an iPhone 16 Pro / iOS 27.0 with a Truesense T-TAG, live distance updates, stop/start, foreground resume and tag power-cycle recovery passed. Dark-mode visibility was reproduced and verified in the simulator and on the phone. The final clean build, without temporary native tracing, also ranged successfully.
Direction/angle remained null. The firmware revision and the remaining hardware acceptance matrix are not validated. Prepare the regular 0.1.0 release on npm latest. Release tests verify stable/prerelease flags and block mismatched channels, private repositories, modified archives and existing versions. Publication and public visibility follow successful CI.