upgrade to 3 latest - #3
Merged
Merged
Conversation
Completes the move to dd-sdk-ios 3.14.0 begun in 5192d23: * Release notes for 3.14.0.1 covering the module restructure (DatadogObjc and CrashReporter gone, Flags and Profiling new), the namespace moves, and every 3.x API change, plus the generator bugs found and fixed. * README rewritten for the twelve-package set, per-module namespaces, the unified URLSession instrumentation, and a 2.x migration table. * Sample and device tests moved to the product-module namespaces and the 3.x API (RUMView(name:), view attributes, KSCrash, W3C header writer). 17 on-simulator checks pass on both net9 and net10. * CI package lists updated across pr.yml, release.yml and the e2e script; the release table lists the new set and marks Objc as a meta-package. * merge-packages.py merges dependency groups independently of lib assets, so the dependency-only Objc meta-package advertises net10 correctly. * GenerateBindings.sh framework list updated for the 3.x set. * generate_3x.py removed - it is scratch tooling, committed by accident. Verified: solution builds warning-free, 127 package tests, and the sample launches clean against the packed 3.14.0.1 packages. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Both mapper checks failed in CI while passing locally. They assert on an asynchronous side effect - mappers run on the SDK's own write queue - and gave it a fixed five-second deadline over whatever events happened to be queued already. Locally the queue drains in 0.1s; the CI runner was slow enough that its simulator took 46 seconds just to boot, and five seconds was not enough. The binding is fine: the same packages pass on net9 and net10 locally, and the other 15 checks passed in that CI run. Rather than just raising the number, the wait now re-drives the work it is waiting on - starting and stopping a view, or writing a log - once a second until the mapper fires, and reports how long it took so future slowness is visible rather than silent. The ceiling is 30 seconds, but a healthy run still returns in milliseconds because the condition is polled every 100ms. Kept as a hard failure: a mapper that never fires is a real block-marshalling defect, which is exactly what these checks exist to catch. Verified: 17/17 on both net9.0-ios18.0 and net10.0-ios26.0, mappers firing in 0.1s. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This branch was previously deployed
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
1 participant
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.
No description provided.