# swift\_getOpaqueTypeMetadata crash

**URL:** <https://forums.swift.org/t/swift-getopaquetypemetadata-crash/55811>\
**Category:** Using Swift\
**Created:** [March 9, 2022, 3:10pm UTC](https://forums.swift.org/t/swift-getopaquetypemetadata-crash/55811 "2022-03-09T15:10:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![willft](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/willft/32/412_2.png) [@willft](https://forums.swift.org/u/willft)\
**Post date:** [March 9, 2022, 9:30pm UTC](https://forums.swift.org/t/swift-getopaquetypemetadata-crash/55811/4 "2022-03-09T21:30:34Z")

</div>

@Stan_Smida Try with the Xcode 13.3 beta. There have been a number of weird, iOS 14 + release build only crashes reported on these forums, at least some of which are fixed in Xcode 13.3.

I ran into a very, very similar issue in `__swift_instantiateConcreteTypeFromMangledName` using SwiftUI + `#available`. [This person](https://developer.apple.com/forums/thread/697070) also ran into one in `swift::ResolveAsSymbolicReference::operator` (which also appears to be related to demangling + SwiftUI + `#available`) and then there's [this one](https://forums.swift.org/t/async-await-crash-on-ios14-with-xcode-13-2-1/54541) which had something to do with concurrency.

Until you can actually build a release using Xcode 13.3, you can try [this workaround](https://developer.apple.com/forums/thread/697070?answerId=700301022#700301022) from the above-linked developer forums thread. Something similar worked for me & this way you don't have to set `@_optimize(none)`.

---

_[View the full topic](https://forums.swift.org/t/swift-getopaquetypemetadata-crash/55811)._