You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that SwiftPM generates the bundle path here (by appending the bundle extension to the build path), then this property conditionally exposes the bundle path, and finally —on the WASI platform— the entire absolute path is retained, leading to the issue described.
Currently use of
Bundle.module
for static resources causes issues, check the URL generated bycarton
with SwiftWasm 5.6 in this code: https://github.com/swiftwasm/carton/blob/b9dab08e869f51415a55b3bb15a3e29cfd1e16e7/Tests/Fixtures/TestApp/Sources/TestApp/main.swift#L48It contains full path to the toolchain, which is obviously invalid.
The text was updated successfully, but these errors were encountered: