René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"analyze: misleading version errors and process crash on AssetBundles without TypeTrees","articleBody":"## Problem\n\nRunning `analyze` on AssetBundles whose SerializedFiles have no TypeTrees produces poor output:\n\n1. **Misleading errors.** The native loader falls back to exact-version type matching when there are no TypeTrees, so it prints `Invalid serialized file version. Expected: ... Actual: ...` straight to stderr. The version mismatch is a symptom; the real cause is the missing TypeTrees.\n\n2. **Process crash.** For at least one such file the native DLL dereferences bad memory and the whole process dies with `Fatal error. 0xC0000005` plus a long, unhelpful managed stack trace. This is a native access violation that cannot be caught in .NET.\n\nExample:\n\n```\nUnityDataTool analyze -o out.db \u003cpath-to-StreamingAssets-with-no-typetree-bundles\u003e\n```\n\nLoose (non-archive) SerializedFiles without TypeTrees (e.g. `TestCommon/Data/PlayerNoTypeTree`) already report a clear hint. The archive case should behave at least as well.\n\n## Desired behaviour\n\nDetect missing TypeTrees before handing the file to the native loader and skip it cleanly, printing the existing \"does not have TypeTrees\" hint. No misleading version errors, no crash. Report these files in their own summary category so they can be distinguished from genuine failures in a large run.","author":{"url":"https://github.com/SkowronskiAndrew","@type":"Person","name":"SkowronskiAndrew"},"datePublished":"2026-06-15T22:15:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/77/UnityDataTools/issues/77"}